**** BEGIN LOGGING AT Sat Jan 11 02:59:58 2014 Jan 11 03:00:17 96328dg2x2 is the ID of the board, and I had to add this section in order to have the kernel boot in this device Jan 11 03:03:00 <[florian]> ok, sounds good then Jan 11 03:03:43 but, when I added the section, I just copied another board's spec, becouse, to be honest, I don't know very much what I'm doing. Jan 11 03:07:22 <[florian]> what this does it that when the kernel reads the board id from flash, it needs to know about the on-board peripherals Jan 11 03:07:25 So, if it is a gpio thing, perhaps there is a way to poke them from the running kernel and find out? Jan 11 03:07:27 <[florian]> and that structure describes exactly that Jan 11 03:07:56 <[florian]> you could export all gpios using echo > /sys/class/gpio/export Jan 11 03:08:09 <[florian]> and then control the gpio line using /sys/class/gpio/gpio/direction Jan 11 03:08:18 <[florian]> and /sys/class/gpio/gpio/value Jan 11 03:09:32 and if I hit the right gpio I would see it with dmesg? Jan 11 03:09:59 the ports being recognized, I mean... Jan 11 03:10:24 <[florian]> it might yes, not sure how well hotplugged that would be though Jan 11 03:11:15 root@OpenWrt:~# echo > /sys/class/gpio/export Jan 11 03:11:18 -ash: syntax error: unexpected redirection Jan 11 03:12:10 <[florian]> hey, this needs to be a number :( Jan 11 03:12:12 <[florian]> :) Jan 11 03:12:25 ? Jan 11 03:12:36 <[florian]> yeah, this was just to illustrate Jan 11 03:12:52 <[florian]> 0 to 31 are valid numbers for 6328 Jan 11 03:13:03 ok, here we go Jan 11 03:14:25 some of them shows: ash: write error: Device or resource busy Jan 11 03:14:42 when doing echo Jan 11 03:14:55 <[florian]> ah ok, that means the kernel is already using it Jan 11 03:15:02 <[florian]> or that you already requested it previously Jan 11 03:15:19 <[florian]> cat /sys/kernel/debug/gpio will show what's exported and by what (sysfs or something else) Jan 11 03:16:47 Your last command is great. The problem is that shows what I copied from another device :| so... unreliable, I guess... Jan 11 03:17:28 what should I set for direction and/or value on the gpios? Jan 11 03:19:40 almost all of them which aren't already used are in direction in and value 1, Jan 11 03:19:40 <[florian]> "in" for input and "out" for output in */direction Jan 11 03:19:44 <[florian]> then 0 and 1 for value Jan 11 03:19:49 except gpio16 which has value 0 Jan 11 03:23:11 I set all of them to 0, one led ligths up. Jan 11 03:23:43 dmesg shows no change Jan 11 03:24:08 but the led is the USB one Jan 11 03:24:40 <[florian]> ok Jan 11 03:24:57 <[florian]> can you paste your log on pastebin.com so I can check if things look good? Jan 11 03:25:11 its gpio10 Jan 11 03:25:33 of course, what log? dmesg? Jan 11 03:27:38 build #479 of cobalt is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/479 Jan 11 03:29:42 <[florian]> dmesg yes Jan 11 03:31:13 http://pastebin.com/a2JTqL4w Jan 11 03:32:54 <[florian]> is usb support enabled with kmod- in make menuconfig? Jan 11 03:33:16 <[florian]> "[ 0.000000] board_bcm963xx: board name: 963281TAN" Jan 11 03:33:26 that's the board I copied from. Jan 11 03:33:33 <[florian]> ok, you should change the name Jan 11 03:33:34 I don't know where to change that. Jan 11 03:34:16 -*- kmod-usb-core............................................ Support for USB Jan 11 03:34:39 I will paste the section I am adding. Jan 11 03:34:45 <[florian]> ok, that sounds good Jan 11 03:35:43 http://pastebin.com/KgPdgDEv Jan 11 03:41:06 [florian]: it's working! Jan 11 03:41:23 yow were a key part, of course. Jan 11 03:42:26 I don't understand, though, why. The CFE says: Jan 11 03:42:33 Board Id (0-4) : 96328dg2x2 Jan 11 03:42:59 <[florian]> that's the board id that CFE is using and configured for Jan 11 03:43:05 and before I added the section copied, the kernel panicked. After that, it loaded all right. Jan 11 03:43:06 <[florian]> and so the kernel should match against the same name Jan 11 03:43:18 <[florian]> if the kernel does not know the board, it will panic Jan 11 03:43:43 <[florian]> this is such that people know that they have to add board support for their specific platform Jan 11 03:43:48 But now that you pointed me the TAN board, I added .has_*hci to that section, and recompiled, reflashed, and now it works. Jan 11 03:44:11 I mean, it is not using the section I added. Jan 11 03:44:21 <[florian]> humm that does not sound right then Jan 11 03:44:36 I will connect serial and check again. Jan 11 03:44:38 <[florian]> can you show the kernel log of when it works Jan 11 03:45:41 sure Jan 11 03:45:55 [ 6.220000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Jan 11 03:45:55 [ 6.340000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 Jan 11 03:45:55 [ 6.368000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00, overcurrent ignored Jan 11 03:45:55 [ 6.376000] hub 1-0:1.0: USB hub found Jan 11 03:45:55 [ 6.392000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Jan 11 03:45:56 [ 6.404000] ohci-platform ohci-platform: new USB bus registered, assigned bus number 2 Jan 11 03:45:59 [ 6.480000] hub 2-0:1.0: USB hub found Jan 11 03:46:01 [ 6.496000] uhci_hcd: USB Universal Host Controller Interface driver Jan 11 03:46:03 [ 19.560000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Jan 11 03:46:05 [ 19.660000] usbhid: USB HID core driver Jan 11 03:46:07 [ 72.364000] usb 2-1: new full-speed USB device number 2 using ohci-platform Jan 11 03:46:10 <[florian]> ahhh stop that :) Jan 11 03:46:18 <[florian]> use a pastebin instead ;) Jan 11 03:46:21 sorry Jan 11 03:46:25 <[florian]> no problem Jan 11 03:46:27 not used to the rules Jan 11 03:46:35 <[florian]> I mean can you show me the part where it says which board it detected? Jan 11 03:46:42 lsusb also works. Jan 11 03:46:56 [ 0.000000] board_bcm963xx: board name: 963281TAN Jan 11 03:47:06 it is what you pointed out earlier Jan 11 03:48:13 <[florian]> ok, so you need to figure out why this is the board which is picked up instead of your definition for 96328dg2x2 Jan 11 03:49:48 Now in CFE it says Jan 11 03:49:52 Board Id (0-4) : 963281TAN Jan 11 03:50:29 I don't know what happened. I am sure it was the other ID because I don't have another device. Jan 11 03:51:20 all other parameters are the same. Jan 11 03:51:47 <[florian]> ah sounds like you have a flash problem Jan 11 03:51:54 <[florian]> or did you change the board id yourself? Jan 11 03:52:15 no, I don't know how Jan 11 03:52:31 maybe openwrt did it for me? Jan 11 03:54:13 <[florian]> if that's the case something is seriously broken with the flash driver Jan 11 03:54:33 I can get another identical device... will try. Jan 11 03:58:15 well... it is not working anyways... I connected a pen drive, a usb to serial adapter, and nothing. Jan 11 03:58:55 the devices are powered on, but not being detected. Jan 11 03:59:17 I have the kernel modules for usb_storage and usb-acm Jan 11 03:59:41 maybe I have to do something with gpio10? Jan 11 04:01:14 <[florian]> maybe Jan 11 04:01:52 do you know how would I have to configure it in the description file? Jan 11 04:03:04 <[florian]> we don't have a good infrastructure for that Jan 11 04:03:14 <[florian]> so registering it as a LEd would be the simplest way to do it Jan 11 04:08:53 ok, reflashing Jan 11 04:15:11 build #491 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/491 Jan 11 04:16:44 there is progress, the pen drive is detected. Jan 11 04:16:51 <[florian]> good Jan 11 04:16:56 <[florian]> did playing with the gpio helped? Jan 11 04:21:54 yes, like you said, I added it as a led. Jan 11 04:23:24 <[florian]> ah great Jan 11 04:25:32 however, it doesn't reboot now. Jan 11 04:25:39 since I reflashed Jan 11 04:25:54 I have to power cicle Jan 11 04:32:22 usb storage works fine. Jan 11 04:32:58 now when I plug a USB ACM device, no show Jan 11 04:33:07 I have the kmod-usb-acm module Jan 11 04:33:26 it just says Jan 11 04:33:29 [ 151.644000] usb 2-1: new full-speed USB device number 2 using ohci-platform Jan 11 04:33:42 will try disabling ohci Jan 11 04:38:03 bad idea, now I get nothing. also tried with pl-2303 usb to serial Jan 11 04:38:19 however, it reboots now... Jan 11 04:38:47 this is some kind of dark art for me. Jan 11 04:44:52 build #434 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/434 Jan 11 04:45:24 seems to be something wrong with ohci. Jan 11 04:46:23 <[florian]> ohci is required for usb to work afair Jan 11 04:46:45 .has_ohci0 = 1, Jan 11 04:46:54 <[florian]> the module must be loaded too Jan 11 04:46:56 the one means presence? Jan 11 04:47:11 if I put a 0, it disables it? Jan 11 04:47:40 the module kmod-usb-ohci is compiled in kernel. Jan 11 04:48:11 but when I connect the device, dmesg shows: Jan 11 04:48:17 [ 151.644000] usb 2-1: new full-speed USB device number 2 using ohci-platfor Jan 11 04:49:01 and nothing more. I have the drivers for pl2303 in the kernel also. Jan 11 04:54:34 ernesto_> the one means presence?: never mind, it does Jan 11 05:00:50 I have a kernel panic, that's why it doesn't reboots. Jan 11 05:06:04 I'll deal with it tomorrow. Jan 11 05:06:19 [florian]: thanks very much for your assistance. Jan 11 05:15:41 build #54 of mxs is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/54 Jan 11 05:20:14 build #480 of ramips is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/480 Jan 11 08:50:06 build #466 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/466 Jan 11 09:57:58 build #55 of imx6 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/55 Jan 11 10:00:43 build #371 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/371 Jan 11 11:18:10 juhosg r39219 trunk/target/linux/ar71xx/files/drivers/net/ethernet/atheros/ag71xx/ag71xx_main.c * ar71xx: ag71xx: increase calculated max frame length value Jan 11 11:24:43 build #53 of mvebu is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/53 Jan 11 12:11:06 build #422 of xburst is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/422 Jan 11 12:28:03 build #418 of ixp4xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/418 Jan 11 16:09:16 juhosg r39220 trunk/ (54 files in 36 dirs) * kernel: update 3.10 to 3.10.26 Jan 11 16:22:55 build #400 of au1000 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/400 Jan 11 17:19:56 wigyori r39221 trunk/package/ boot/uboot-sunxi/Makefile boot/uboot-sunxi/patches/001-a10_olinuxino_lime_support.patch boot/uboot-sunxi/patches * [packages] uboot-sunxi: add support for Olinuxino A10 LIME Jan 11 17:21:43 wigyori r39222 trunk/target/linux/ sunxi/profiles/a10-olinuxino.mk sunxi/files/arch/arm/boot/dts/sun4i-a10-olinuxino-lime.dts sunxi/image/Makefile sunxi/patches-3.12/231-add-a10-olinuxino-lime.patch * sunxi: add support for Olinuxino A10 LIME Jan 11 19:48:43 blogic: which commit actually fixes bug 14633 (ltq-atm.c compilation failure)? Jan 11 20:28:11 build #371 of ep93xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/371 Jan 11 20:31:55 build #360 of mcs814x is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/360 Jan 11 20:53:20 sungami: not pushed yet Jan 11 21:01:06 is the wifi eeprom patch "not pushed yet" too? Jan 11 21:23:04 DonkeyHotei: would that patch be for the rt2800 by any chance? I'd be interested in giving it a try if it is Jan 11 21:23:41 build #325 of octeon is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/325 Jan 11 21:25:39 build #482 of ramips is complete: Failure [failed compile_3] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/482 Jan 11 21:40:36 vampo: for ath9k Jan 11 21:52:05 ah, ok, thanks Jan 11 22:00:29 blogic: that's what I thought. I just wanted to make sure that the patch in the bug report is still needed for now, and not superseded by some other solution. Jan 11 22:01:08 wigyori r39223 trunk/target/linux/ (6 files in 2 dirs) Jan 11 22:01:08 sunxi: various changes Jan 11 22:01:08 - let LBDAF be set by generic config Jan 11 22:01:08 - add high-speed timer support Jan 11 22:01:08 - refresh sun5i USB patch Jan 11 22:01:10 Signed-off-by: Zoltan HERPAI Jan 12 01:02:20 build #455 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/455 Jan 12 01:05:14 build #455 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/455 Jan 12 01:32:00 build #481 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/481 **** ENDING LOGGING AT Sun Jan 12 02:59:59 2014