From: Bill G. <bg...@bi...> - 2008-11-25 22:32:55
|
Guys: Does the Linux kernel that ships with Overo Earth include support for usb ethernet gadget? I'm trying to decide if I have a kernel config problem, or a cable problem... b.g. -- Bill Gatliff bg...@bi... |
From: Steve S. <sa...@gm...> - 2008-11-25 22:44:35
|
On Tue, Nov 25, 2008 at 2:32 PM, Bill Gatliff <bg...@bi...> wrote: > Does the Linux kernel that ships with Overo Earth include support for > usb ethernet gadget? I'm trying to decide if I have a kernel config > problem, or a cable problem... As shipped, the musb (OTG) port is configured for host only. If you want the ethernet gadget you will need to modify the kernel config for either device or OTG mode and rebuild. Steve |
From: Bill G. <bg...@bi...> - 2008-11-25 23:05:37
|
Steve Sakoman wrote: > On Tue, Nov 25, 2008 at 2:32 PM, Bill Gatliff <bg...@bi...> wrote: > > >> Does the Linux kernel that ships with Overo Earth include support for >> usb ethernet gadget? I'm trying to decide if I have a kernel config >> problem, or a cable problem... > > As shipped, the musb (OTG) port is configured for host only. If you > want the ethernet gadget you will need to modify the kernel config for > either device or OTG mode and rebuild. So, what's with the connector labeled "Host", then? I'm confused... b.g. -- Bill Gatliff bg...@bi... |
From: Frank A. <ft...@ya...> - 2008-11-25 23:03:40
|
Bill Gatliff wrote: > Guys: > > > Does the Linux kernel that ships with Overo Earth include support for > usb ethernet gadget? I'm trying to decide if I have a kernel config > problem, or a cable problem... > > > b.g. Bill, The kernel that came with my Overo does include support for usb ethernet gadget. Here's the message from the kernel on my board: pegasus 1-1.3.4:1.0: eth0, ADMtek ADM8511 "Pegasus II" USB Ethernet, 00:14:d1:12 I'm connecting the USB ethernet dongle (a Trendnet TU-ET100C) to a hub, then from the hub to the USB OTG connector on the Overo. The USB cable that connects from the hub to the Overo has pin 4 (id) shorted to pin 5 (gnd). Here's the list of USB network adapters that are enabled in the kernel that is shipped with Overo: CONFIG_USB_CATC=m CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_RTL8150=m CONFIG_USB_USBNET=y CONFIG_USB_NET_AX8817X=y CONFIG_USB_NET_CDCETHER=y CONFIG_USB_NET_DM9601=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_PLUSB=m CONFIG_USB_NET_MCS7830=m CONFIG_USB_NET_RNDIS_HOST=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_KC2190=y CONFIG_USB_NET_ZAURUS=m frank agius |
From: Dave H. <dhy...@gm...> - 2008-11-25 23:40:11
|
Hi Frank, > > Does the Linux kernel that ships with Overo Earth include support for > > usb ethernet gadget? I'm trying to decide if I have a kernel config > > problem, or a cable problem... > > The kernel that came with my Overo does include support for usb ethernet > gadget. Here's the message from the kernel on my board: > > pegasus 1-1.3.4:1.0: eth0, ADMtek ADM8511 "Pegasus II" USB Ethernet, > 00:14:d1:12 > > I'm connecting the USB ethernet dongle (a Trendnet TU-ET100C) to a hub, > then from the hub to the USB OTG connector on the Overo. The USB cable > that connects from the hub to the Overo has pin 4 (id) shorted to pin 5 > (gnd). So this is using the Overo as a USB host. When used as a USB gadget, the Overo would be plugged into a PC and would look like an ethernet adapter. This is different from using an ethernet adapter. USB gadgets are used to make the linux machine look like a USB device, as opposed to the USB host which uses USB devices. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: jwoycheese <jwo...@ya...> - 2009-09-07 05:45:11
|
I am very confused. I am using the default v0.92 palmtop build for an Earth on a Palo43. I have the same configuration as Frank (TRENDnet TU-ET100C dongle plugged into a 4-port, powered hub, plugged into the OTG port). When I fire up the Earth, the hub and usb dongle are discovered, the latter as an ADMtek ADM8511 "Pegasus II" USB Ethernet, with a MAC address of 00:00:00:00:00:00. dhcp sends a discover 3 times and then throws up its little hands. I can't set the HW address (see below). Connecting the same dongle to my winbox gives an appropriate MAC (00:14: etc). Anyone know what gives? Thanks, John Some data: ---- root@overo:~# rebootusb 1-1: USB disconnect, address 2 usb 1-1: new full speed USB device using musb_hdrc and address 3 usb 1-1: New USB device found, idVendor=050f, idProduct=0003 usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 usb 1-1: configuration #1 chosen from 1 choice hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.3: new full speed USB device using musb_hdrc and address 4 usb 1-1.3: New USB device found, idVendor=07a6, idProduct=8511 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.3: Product: USB To LAN Converter usb 1-1.3: Manufacturer: ADMtek usb 1-1.3: SerialNumber: 0001 usb 1-1.3: configuration #1 chosen from 1 choice pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver pegasus 1-1.3:1.0: setup Pegasus II specific registers pegasus 1-1.3:1.0: eth0, ADMtek ADM8511 "Pegasus II" USB Ethernet, 00:00:00:00:0 0:00 usbcore: registered new interface driver pegasus ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready root@overo:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:896 (896.0 b) TX bytes:2238 (2.1 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2352 (2.2 KiB) TX bytes:2352 (2.2 KiB) ---- ifconfig eth0 hw ether 12:34:56:43:21 SIOCSIFHWADDR: Operation not supported ---- root@overo:~# ifdown -a cat: /var/run/udhcpc.eth0.pid: No such file or directory root@overo:~# ifup -a eth0 no wireless extensions. udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing ---- Frank Agius wrote: > > Bill Gatliff wrote: >> Guys: >> >> >> Does the Linux kernel that ships with Overo Earth include support for >> usb ethernet gadget? I'm trying to decide if I have a kernel config >> problem, or a cable problem... >> >> >> b.g. > > Bill, > > The kernel that came with my Overo does include support for usb ethernet > gadget. Here's the message from the kernel on my board: > > pegasus 1-1.3.4:1.0: eth0, ADMtek ADM8511 "Pegasus II" USB Ethernet, > 00:14:d1:12 > > I'm connecting the USB ethernet dongle (a Trendnet TU-ET100C) to a hub, > then from the hub to the USB OTG connector on the Overo. The USB cable > that connects from the hub to the Overo has pin 4 (id) shorted to pin 5 > (gnd). > ... > -- View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p25325285.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Andy M. <ja...@sm...> - 2009-09-07 10:18:00
|
I have a 4 port hub that I have been using plugged into the USB OTG port. Everything has been working fine and I have full access to all devices that I plug in. I finally got a mini-a to mini-b cable and when I connect it to the USB host port nothing enumerates. Is there something that I need to enable to get this to function? I am using the console bb, only adding additional audio options. cheers a |
From: <chi...@gm...> - 2009-09-19 00:08:47
|
I've noticed a strange behavior on the Gstix I've worked with where if at any point there is a hub plugged in that doesn't have anything plugged in to it, the gstix will disable that hub. This includes the root hub and could be the cause of the behavior you're seeing. Sent from my iPhone On Sep 7, 2009, at 3:17 AM, "Andy Maginnis" <ja...@sm...> wrote: > I have a 4 port hub that I have been using plugged into the USB OTG > port. Everything has been working fine and I have full access to all > devices that I plug in. > > I finally got a mini-a to mini-b cable and when I connect it to the > USB host port nothing enumerates. Is there something that I need to > enable > to get this to function? > > I am using the console bb, only adding additional audio options. > > cheers > a > > --- > --- > --- > --------------------------------------------------------------------- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2008-11-25 23:48:13
|
On Tue, Nov 25, 2008 at 3:05 PM, Bill Gatliff <bg...@bi...> wrote: > Steve Sakoman wrote: >> On Tue, Nov 25, 2008 at 2:32 PM, Bill Gatliff <bg...@bi...> wrote: >> >> >>> Does the Linux kernel that ships with Overo Earth include support for >>> usb ethernet gadget? I'm trying to decide if I have a kernel config >>> problem, or a cable problem... >> >> As shipped, the musb (OTG) port is configured for host only. If you >> want the ethernet gadget you will need to modify the kernel config for >> either device or OTG mode and rebuild. > > So, what's with the connector labeled "Host", then? I'm confused... The OMAP3 processors have 2 USB ports: 1. musb: will operate in device, OTG, or host mode via kernel config 2. ehci: host mode only. this interface isn't currently functional with the linux-omap kernel top of tree. As delivered the musb driver is configured for host only. You would need to run menuconfig and select either device or OTG if you want to use the ethernet gadget (and rebuild the kernel of course). Steve Steve |
From: David W. <dw...@da...> - 2008-11-25 23:55:38
|
Hi all, I keep seeing comments such as "you need to run menuconfig". But nobody ever gives the exact command line or which directory is supposed to be current when it is issued. I believe (no real basis, just other build systems) the line is 'make menuconfig' but that requires a Makefile and issuing it on the Makefiles I have found so far does not work - 'No Target of that name' or similar errors. Searching on the Wiki yields no hits. So, precisely, how does one reconfigure the kernel and rootfs? Thanks, David Warman Computer Systems Architect dw...@da... http://www.davidwarman.net http://www.linkedin.com/in/davidjwarman P: 206-780-9963 M: 206-407-7050 F: 206-842-4958 Skype: david.warman On Nov 25, 2008, at 3:48 PM, Steve Sakoman wrote: > On Tue, Nov 25, 2008 at 3:05 PM, Bill Gatliff > <bg...@bi...> wrote: >> Steve Sakoman wrote: >>> On Tue, Nov 25, 2008 at 2:32 PM, Bill Gatliff >>> <bg...@bi...> wrote: >>> >>> >>>> Does the Linux kernel that ships with Overo Earth include >>>> support for >>>> usb ethernet gadget? I'm trying to decide if I have a kernel >>>> config >>>> problem, or a cable problem... >>> >>> As shipped, the musb (OTG) port is configured for host only. If you >>> want the ethernet gadget you will need to modify the kernel >>> config for >>> either device or OTG mode and rebuild. >> >> So, what's with the connector labeled "Host", then? I'm confused... > > The OMAP3 processors have 2 USB ports: > > 1. musb: will operate in device, OTG, or host mode via kernel config > 2. ehci: host mode only. this interface isn't currently functional > with the linux-omap kernel top of tree. > > As delivered the musb driver is configured for host only. You would > need to run menuconfig and select either device or OTG if you want to > use the ethernet gadget (and rebuild the kernel of course). > > Steve > > Steve > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Bill G. <bg...@bi...> - 2008-11-26 03:50:08
|
Steve Sakoman wrote: > The OMAP3 processors have 2 USB ports: > > 1. musb: will operate in device, OTG, or host mode via kernel config > 2. ehci: host mode only. this interface isn't currently functional > with the linux-omap kernel top of tree. > D'oh! I guess I'm still stuck in "beagleboard mode". Thanks for clarifying. :) b.g. -- Bill Gatliff bg...@bi... |
From: Bill G. <bg...@bi...> - 2008-11-26 03:51:04
|
David Warman wrote: > Hi all, > > I keep seeing comments such as "you need to run menuconfig". But nobody > ever gives the exact command line or which directory is supposed to be > current when it is issued. I believe (no real basis, just other build > systems) the line is 'make menuconfig' but that requires a Makefile and > issuing it on the Makefiles I have found so far does not work - 'No > Target of that name' or similar errors. Searching on the Wiki yields no > hits. Try: $ make ARCH=arm menuconfig b.g. -- Bill Gatliff bg...@bi... |
From: schemish <sch...@ri...> - 2009-03-20 04:38:07
|
sakoman wrote: > > As delivered the musb driver is configured for host only. You would > need to run menuconfig and select either device or OTG if you want to > use the ethernet gadget (and rebuild the kernel of course). > Well, I have tried to enable device or OTG in 2.6.28 kernel, without success. In both cases I am getting the same error: In file included from drivers/usb/musb/musb_core.c:108: drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... select CONFIG_USB_GADGET_MUSB_HDRC I have tried also the current 2.6.29 kernel (bitbake -c rebuild linux-omap3), with the same result. In case you need more details, I have attached corresponding fragments of v2.6.28 "defconfig" file and build log below. --- 1. Case of USB Peripheral (gadget stack) defconfig fragment: # # OMAP 343x high speed USB support # # CONFIG_USB_MUSB_HOST is not set CONFIG_USB_MUSB_PERIPHERAL=y # CONFIG_USB_MUSB_OTG is not set # CONFIG_USB_GADGET_MUSB_HDRC is not set CONFIG_MUSB_PIO_ONLY=y # CONFIG_USB_MUSB_DEBUG is not set Build error: | make[2]: Entering directory `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' | CC drivers/usb/musb/musb_core.o | In file included from drivers/usb/musb/musb_core.c:108: | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... select CONFIG_USB_GADGET_MUSB_HDRC | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 | make[2]: Leaving directory `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' 2 Case of USB OTG (On The Go) Device defconfig looks like: # # OMAP 343x high speed USB support # # CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_PERIPHERAL is not set CONFIG_USB_MUSB_OTG=y # CONFIG_USB_GADGET_MUSB_HDRC is not set CONFIG_USB_MUSB_HDRC_HCD=y CONFIG_MUSB_PIO_ONLY=y # CONFIG_USB_MUSB_DEBUG is not set Build error: make[2]: Entering directory `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' | CC drivers/usb/musb/musb_core.o | In file included from drivers/usb/musb/musb_core.c:108: | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... select CONFIG_USB_GADGET_MUSB_HDRC | drivers/usb/musb/musb_core.c: In function 'musb_free': | drivers/usb/musb/musb_core.c:1819: error: 'dev_attr_srp' undeclared (first use in this function) | drivers/usb/musb/musb_core.c:1819: error: (Each undeclared identifier is reported only once | drivers/usb/musb/musb_core.c:1819: error: for each function it appears in.) | drivers/usb/musb/musb_core.c: In function 'musb_init_controller': | drivers/usb/musb/musb_core.c:2066: error: 'dev_attr_srp' undeclared (first use in this function) | drivers/usb/musb/musb_core.c:1891: error: label 'bad_config' used but not defined | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 | make[2]: Leaving directory `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' -- View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p22614221.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2008-11-25 23:52:51
|
On Tue, Nov 25, 2008 at 3:48 PM, Steve Sakoman <sa...@gm...> wrote: > On Tue, Nov 25, 2008 at 3:05 PM, Bill Gatliff <bg...@bi...> wrote: >> Steve Sakoman wrote: >>> On Tue, Nov 25, 2008 at 2:32 PM, Bill Gatliff <bg...@bi...> wrote: >>> >>> >>>> Does the Linux kernel that ships with Overo Earth include support for >>>> usb ethernet gadget? I'm trying to decide if I have a kernel config >>>> problem, or a cable problem... >>> >>> As shipped, the musb (OTG) port is configured for host only. If you >>> want the ethernet gadget you will need to modify the kernel config for >>> either device or OTG mode and rebuild. >> >> So, what's with the connector labeled "Host", then? I'm confused... > > The OMAP3 processors have 2 USB ports: > > 1. musb: will operate in device, OTG, or host mode via kernel config > 2. ehci: host mode only. this interface isn't currently functional > with the linux-omap kernel top of tree. > > As delivered the musb driver is configured for host only. You would > need to run menuconfig and select either device or OTG if you want to > use the ethernet gadget (and rebuild the kernel of course). BTW, the musb port is labeled OTG and the ehci port is labled HOST To use the OTG port in either OTG or host mode you'll need to use the white mini-A to mini-B cable that Gumstix sells (or a commercial OTG cable available elsewhere). For device mode, the standard mini-B cables that you likely have in a drawer somewhere are just fine. Steve |
From: Don A. <do...@gu...> - 2008-12-04 23:38:07
|
Gumstix has just added the USB cable (mini-A to mini-B) to our web store: http://gumstix.com/store/catalog/product_info.php?cPath=31&products_id=219 This USB cable is the white mini-A to mini-B cable that Steve mentions below. Don @Gumstix =================== On Tue, Nov 25, 2008 at 3:52 PM, Steve Sakoman <sa...@gm...> wrote: > On Tue, Nov 25, 2008 at 3:48 PM, Steve Sakoman <sa...@gm...> wrote: > > On Tue, Nov 25, 2008 at 3:05 PM, Bill Gatliff <bg...@bi...> > wrote: > >> Steve Sakoman wrote: > ..... > > To use the OTG port in either OTG or host mode, you'll need to use the > white mini-A to mini-B cable that Gumstix sells (or a commercial OTG > cable available elsewhere). > > For device mode, the standard mini-B cables that you likely have in a > drawer somewhere are just fine. > > Steve > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: David W. <dw...@da...> - 2008-11-26 04:07:25
|
OK, thanks, but in what directory? Where is the Makefile that make is looking for with that target in it? When Makefile is not specified make looks in the current directory only IIRC. David Warman Computer Systems Architect dw...@da... http://www.davidwarman.net http://www.linkedin.com/in/davidjwarman P: 206-780-9963 M: 206-407-7050 F: 206-842-4958 Skype: david.warman On Nov 25, 2008, at 7:51 PM, Bill Gatliff wrote: > David Warman wrote: >> Hi all, >> >> I keep seeing comments such as "you need to run menuconfig". But >> nobody >> ever gives the exact command line or which directory is supposed >> to be >> current when it is issued. I believe (no real basis, just other build >> systems) the line is 'make menuconfig' but that requires a >> Makefile and >> issuing it on the Makefiles I have found so far does not work - 'No >> Target of that name' or similar errors. Searching on the Wiki >> yields no >> hits. > > Try: > > $ make ARCH=arm menuconfig > > > b.g. > -- > Bill Gatliff > bg...@bi... > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2008-11-26 04:48:59
|
On Tue, Nov 25, 2008 at 8:07 PM, David Warman <dw...@da...> wrote: > OK, thanks, but in what directory? Where is the Makefile that make is > looking for with that target in it? When Makefile is not specified make > looks in the current directory only IIRC. The top level of the linux source directory. We could be more specific if you tell us whether you've set a build environment yet, whether you are using the Gumstix OE environment, or using some other alternative. Steve |
From: David W. <dw...@da...> - 2008-11-26 05:48:58
|
Thanks. That's interesting. I have checked out the OE tree, and it bitbakes just fine. But there is no Makefile at the top of the tree. I did follow the suggestion and copied the environment settings file onto the end of my .bashrc. I also found that to make bitbake work I had to issue 'newgrp oe'. This is into a downloaded install of Debian Etch set up specifically for Gumstix purposes inside a new VmWare Fusion bubble, so I only have whatever tools the Gumstix Wiki calls for installed, and no other projects in there to confuse the issue. I followed the instructions on http://www.gumstix.net/Software/view/ Getting-started/Setting-up-a-build-environment/111.html . David Warman Computer Systems Architect dw...@da... http://www.davidwarman.net http://www.linkedin.com/in/davidjwarman P: 206-780-9963 M: 206-407-7050 F: 206-842-4958 Skype: david.warman On Nov 25, 2008, at 8:48 PM, Steve Sakoman wrote: > On Tue, Nov 25, 2008 at 8:07 PM, David Warman > <dw...@da...> wrote: >> OK, thanks, but in what directory? Where is the Makefile that make is >> looking for with that target in it? When Makefile is not specified >> make >> looks in the current directory only IIRC. > > The top level of the linux source directory. > > We could be more specific if you tell us whether you've set a build > environment yet, whether you are using the Gumstix OE environment, or > using some other alternative. > > Steve > > ---------------------------------------------------------------------- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2008-11-26 16:13:50
|
On Tue, Nov 25, 2008 at 9:48 PM, David Warman <dw...@da...> wrote: > Thanks. That's interesting. I have checked out the OE tree, and it bitbakes > just fine. But there is no Makefile at the top of the tree. I did follow the > suggestion and copied the environment settings file onto the end of my > .bashrc. I also found that to make bitbake work I had to issue 'newgrp oe'. > This is into a downloaded install of Debian Etch set up specifically for > Gumstix purposes inside a new VmWare Fusion bubble, so I only have whatever > tools the Gumstix Wiki calls for installed, and no other projects in there > to confuse the issue. I followed the instructions > on http://www.gumstix.net/Software/view/Getting-started/Setting-up-a-build-environment/111.html OK, then you are set up to do OE builds for connex and verdex. I'm away from the office so I can't cut & paste specific paths for you, but I'll try to give you general pointers. If you are going to do anything beyond building the standard images and packages I recommend you spend some time reading the OE documentation to get familiar with how OpenEmbedded works and where it places things in the directory structure. There's an extremely brief overview at: http://www.gumstix.net/Software/view/Build-system-overview/Directory-layout/111.html In general though, you will find the source tree for any package in the tmp/work directory of your oe settup. Packages are grouped there under subdirectories for general arm executables and machine specific executables (which is where linux/gumstix-kernel would be). Once you find the linux source tree, cd there and you will see the linux makefile. This is where you would run 'make ARCH=arm menuconfig' You'll want to save the resulting new config in the gumstix kernel recipe so that future builds will use it instead of the default one. Look for it under org.openembedded.dev/packages/linux. You'll want to replace the existing defconfig file you find there with the .config file you generated above. Hopefully this is enough guidance to get you to the right spots in the build tree. The OE build settup is extremely powerful, but it requires quite an investment of time to get familiar with how it works in order to exploit its full potential. Steve |
From: schemish <sch...@ri...> - 2009-05-07 20:29:03
|
Hi Jon, As of yesterday, I am able to build the kernel. But I have not tested any USB gadgets yet, this is on TODO list for tonight. So, there was a conflicting entry in .config file: CONFIG_USB_GADGET_OMAP=y CONFIG_USB_OMAP=y According to Steve Sakoman, the first one, i.e. CONFIG_USB_GADGET_OMAP is an old OMAP1 setting, it should not be set. So, in your defconfig file you shold have: # CONFIG_USB_GADGET_OMAP is not set CONFIG_USB_OMAP=y and later also: CONFIG_USB_GADGET_MUSB_HDRC=y In my case CONFIG_USB_GADGET_OMAP=y was not initially in my defconfig file, which was derived in turn from the generic Overo defconfig file, i.e. from org.openembedded.com/recipes/linux/linux-omap3-2.6.29/overo/defconfig. But it got automagically added to .config file after I built the kernel, or run make menuconfig (I usually use .config file as my new defconfig after running 'make arch=ARM menuconfig' in the kernel git directory). So,if you use .config file as your new defconfig after running 'make arch=ARM menuconfig', make sure to set CONFIG_USB_GADGET_OMAP back to "is not set". Thanks, Sergey jonmccune wrote: > > Hello, > > Has anyone gotten past this issue? I'm getting the same > drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... > select CONFIG_USB_GADGET_MUSB_HDRC > > error, regardless of whether CONFIG_USB_GADGET_MUSB_HDRC is disable or set > =y. > > Thanks, > -Jon > > > > schemish wrote: >> >> >> sakoman wrote: >>> >>> As delivered the musb driver is configured for host only. You would >>> need to run menuconfig and select either device or OTG if you want to >>> use the ethernet gadget (and rebuild the kernel of course). >>> >> >> Well, I have tried to enable device or OTG in 2.6.28 kernel, without >> success. In both cases I am getting the same error: >> In file included from drivers/usb/musb/musb_core.c:108: >> drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... >> select CONFIG_USB_GADGET_MUSB_HDRC >> >> I have tried also the current 2.6.29 kernel (bitbake -c rebuild >> linux-omap3), with the same result. In case you need more details, I >> have attached corresponding fragments of v2.6.28 "defconfig" file and >> build log below. >> --- >> >> 1. Case of USB Peripheral (gadget stack) >> >> defconfig fragment: >> >> # >> # OMAP 343x high speed USB support >> # >> # CONFIG_USB_MUSB_HOST is not set >> CONFIG_USB_MUSB_PERIPHERAL=y >> # CONFIG_USB_MUSB_OTG is not set >> # CONFIG_USB_GADGET_MUSB_HDRC is not set >> CONFIG_MUSB_PIO_ONLY=y >> # CONFIG_USB_MUSB_DEBUG is not set >> >> Build error: >> | make[2]: Entering directory >> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >> | CC drivers/usb/musb/musb_core.o >> | In file included from drivers/usb/musb/musb_core.c:108: >> | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output >> ... select CONFIG_USB_GADGET_MUSB_HDRC >> | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 >> | make[2]: Leaving directory >> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >> >> >> >> >> 2 Case of USB OTG (On The Go) Device >> >> >> defconfig looks like: >> # >> # OMAP 343x high speed USB support >> # >> # CONFIG_USB_MUSB_HOST is not set >> # CONFIG_USB_MUSB_PERIPHERAL is not set >> CONFIG_USB_MUSB_OTG=y >> # CONFIG_USB_GADGET_MUSB_HDRC is not set >> CONFIG_USB_MUSB_HDRC_HCD=y >> CONFIG_MUSB_PIO_ONLY=y >> # CONFIG_USB_MUSB_DEBUG is not set >> >> Build error: >> >> make[2]: Entering directory >> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >> | CC drivers/usb/musb/musb_core.o >> | In file included from drivers/usb/musb/musb_core.c:108: >> | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output >> ... select CONFIG_USB_GADGET_MUSB_HDRC >> | drivers/usb/musb/musb_core.c: In function 'musb_free': >> | drivers/usb/musb/musb_core.c:1819: error: 'dev_attr_srp' undeclared >> (first use in this function) >> | drivers/usb/musb/musb_core.c:1819: error: (Each undeclared identifier >> is reported only once >> | drivers/usb/musb/musb_core.c:1819: error: for each function it appears >> in.) >> | drivers/usb/musb/musb_core.c: In function 'musb_init_controller': >> | drivers/usb/musb/musb_core.c:2066: error: 'dev_attr_srp' undeclared >> (first use in this function) >> | drivers/usb/musb/musb_core.c:1891: error: label 'bad_config' used but >> not defined >> | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 >> | make[2]: Leaving directory >> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >> >> >> > > -- View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p23434465.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2009-05-07 21:00:24
|
On Thu, May 7, 2009 at 1:28 PM, schemish <sch...@ri...> wrote: > > Hi Jon, > > As of yesterday, I am able to build the kernel. But I have not tested any > USB gadgets yet, this is on TODO list for tonight. > > So, there was a conflicting entry in .config file: > > CONFIG_USB_GADGET_OMAP=y > CONFIG_USB_OMAP=y > > According to Steve Sakoman, the first one, i.e. CONFIG_USB_GADGET_OMAP is an > old OMAP1 setting, it should not be set. So, in your defconfig file you > shold have: > # CONFIG_USB_GADGET_OMAP is not set > CONFIG_USB_OMAP=y Not quite! There was indeed an error (kind of) in the overo defconfig, in that the two lines in question were as you stated: CONFIG_USB_GADGET_OMAP=y CONFIG_USB_OMAP=y If you are hand editing, then these two lines should collapse to one line: # CONFIG_USB_GADGET_OMAP is not set The CONFIG_USB_OMAP setting need not be present in the config at all! CONFIG_USB_GADGET_OMAP is indeed a setting for an earlier version of OMAP, and CONFIG_USB_OMAP is automatically set whenever CONFIG_USB_GADGET_OMAP is enabled. If it the former isn't set, then the latter shouldn't be set. All this will happen automatically if you use "make ARCH=arm menuconfig" to generate your defconfig. To understand what is going on just review the Kconfig in drivers/usb/gadget: config USB_GADGET_OMAP boolean "OMAP USB Device Controller" depends on ARCH_OMAP select ISP1301_OMAP if MACH_OMAP_H2 || MACH_OMAP_H3 || MACH_OMAP_H4_OTG select USB_OTG_UTILS if ARCH_OMAP help Many Texas Instruments OMAP processors have flexible full speed USB device controllers, with support for up to 30 endpoints (plus endpoint zero). This driver supports the controller in the OMAP 1611, and should work with controllers in other OMAP processors too, given minor tweaks. Say "y" to link the driver statically, or "m" to build a dynamically linked module called "omap_udc" and force all gadget drivers to also be dynamically linked. config USB_OMAP tristate depends on USB_GADGET_OMAP default USB_GADGET select USB_GADGET_SELECTED and a little later on: config USB_GADGET_MUSB_HDRC boolean "Inventra HDRC USB Peripheral (TI, ADI, ...)" depends on USB_MUSB_HDRC && (USB_MUSB_PERIPHERAL || USB_MUSB_OTG) select USB_GADGET_DUALSPEED select USB_GADGET_SELECTED help This OTG-capable silicon IP is used in dual designs including the TI DaVinci, OMAP 243x, OMAP 343x, TUSB 6010, and ADI Blackfin Probably more than you wanted to know . . . Steve > > and later also: > > CONFIG_USB_GADGET_MUSB_HDRC=y > > In my case CONFIG_USB_GADGET_OMAP=y was not initially in my defconfig file, > which was derived in turn from the generic Overo defconfig file, i.e. from > org.openembedded.com/recipes/linux/linux-omap3-2.6.29/overo/defconfig. But > it got automagically added to .config file after I built the kernel, or run > make menuconfig (I usually use .config file as my new defconfig after > running 'make arch=ARM menuconfig' in the kernel git directory). So,if you > use .config file as your new defconfig after running 'make arch=ARM > menuconfig', make sure to set CONFIG_USB_GADGET_OMAP back to "is not set". > > Thanks, > Sergey > > > > jonmccune wrote: >> >> Hello, >> >> Has anyone gotten past this issue? I'm getting the same >> drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... >> select CONFIG_USB_GADGET_MUSB_HDRC >> >> error, regardless of whether CONFIG_USB_GADGET_MUSB_HDRC is disable or set >> =y. >> >> Thanks, >> -Jon >> >> >> >> schemish wrote: >>> >>> >>> sakoman wrote: >>>> >>>> As delivered the musb driver is configured for host only. You would >>>> need to run menuconfig and select either device or OTG if you want to >>>> use the ethernet gadget (and rebuild the kernel of course). >>>> >>> >>> Well, I have tried to enable device or OTG in 2.6.28 kernel, without >>> success. In both cases I am getting the same error: >>> In file included from drivers/usb/musb/musb_core.c:108: >>> drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... >>> select CONFIG_USB_GADGET_MUSB_HDRC >>> >>> I have tried also the current 2.6.29 kernel (bitbake -c rebuild >>> linux-omap3), with the same result. In case you need more details, I >>> have attached corresponding fragments of v2.6.28 "defconfig" file and >>> build log below. >>> --- >>> >>> 1. Case of USB Peripheral (gadget stack) >>> >>> defconfig fragment: >>> >>> # >>> # OMAP 343x high speed USB support >>> # >>> # CONFIG_USB_MUSB_HOST is not set >>> CONFIG_USB_MUSB_PERIPHERAL=y >>> # CONFIG_USB_MUSB_OTG is not set >>> # CONFIG_USB_GADGET_MUSB_HDRC is not set >>> CONFIG_MUSB_PIO_ONLY=y >>> # CONFIG_USB_MUSB_DEBUG is not set >>> >>> Build error: >>> | make[2]: Entering directory >>> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >>> | CC drivers/usb/musb/musb_core.o >>> | In file included from drivers/usb/musb/musb_core.c:108: >>> | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output >>> ... select CONFIG_USB_GADGET_MUSB_HDRC >>> | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 >>> | make[2]: Leaving directory >>> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >>> >>> >>> >>> >>> 2 Case of USB OTG (On The Go) Device >>> >>> >>> defconfig looks like: >>> # >>> # OMAP 343x high speed USB support >>> # >>> # CONFIG_USB_MUSB_HOST is not set >>> # CONFIG_USB_MUSB_PERIPHERAL is not set >>> CONFIG_USB_MUSB_OTG=y >>> # CONFIG_USB_GADGET_MUSB_HDRC is not set >>> CONFIG_USB_MUSB_HDRC_HCD=y >>> CONFIG_MUSB_PIO_ONLY=y >>> # CONFIG_USB_MUSB_DEBUG is not set >>> >>> Build error: >>> >>> make[2]: Entering directory >>> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >>> | CC drivers/usb/musb/musb_core.o >>> | In file included from drivers/usb/musb/musb_core.c:108: >>> | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output >>> ... select CONFIG_USB_GADGET_MUSB_HDRC >>> | drivers/usb/musb/musb_core.c: In function 'musb_free': >>> | drivers/usb/musb/musb_core.c:1819: error: 'dev_attr_srp' undeclared >>> (first use in this function) >>> | drivers/usb/musb/musb_core.c:1819: error: (Each undeclared identifier >>> is reported only once >>> | drivers/usb/musb/musb_core.c:1819: error: for each function it appears >>> in.) >>> | drivers/usb/musb/musb_core.c: In function 'musb_init_controller': >>> | drivers/usb/musb/musb_core.c:2066: error: 'dev_attr_srp' undeclared >>> (first use in this function) >>> | drivers/usb/musb/musb_core.c:1891: error: label 'bad_config' used but >>> not defined >>> | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 >>> | make[2]: Leaving directory >>> `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' >>> >>> >>> >> >> > > -- > View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p23434465.html > Sent from the Gumstix mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: jonmccune <jon...@cm...> - 2009-05-08 14:09:43
|
Hello, Has anyone gotten past this issue? I'm getting the same drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... select CONFIG_USB_GADGET_MUSB_HDRC error, regardless of whether CONFIG_USB_GADGET_MUSB_HDRC is disable or set =y. Thanks, -Jon schemish wrote: > > > sakoman wrote: >> >> As delivered the musb driver is configured for host only. You would >> need to run menuconfig and select either device or OTG if you want to >> use the ethernet gadget (and rebuild the kernel of course). >> > > Well, I have tried to enable device or OTG in 2.6.28 kernel, without > success. In both cases I am getting the same error: > In file included from drivers/usb/musb/musb_core.c:108: > drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... > select CONFIG_USB_GADGET_MUSB_HDRC > > I have tried also the current 2.6.29 kernel (bitbake -c rebuild > linux-omap3), with the same result. In case you need more details, I have > attached corresponding fragments of v2.6.28 "defconfig" file and build log > below. > --- > > 1. Case of USB Peripheral (gadget stack) > > defconfig fragment: > > # > # OMAP 343x high speed USB support > # > # CONFIG_USB_MUSB_HOST is not set > CONFIG_USB_MUSB_PERIPHERAL=y > # CONFIG_USB_MUSB_OTG is not set > # CONFIG_USB_GADGET_MUSB_HDRC is not set > CONFIG_MUSB_PIO_ONLY=y > # CONFIG_USB_MUSB_DEBUG is not set > > Build error: > | make[2]: Entering directory > `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' > | CC drivers/usb/musb/musb_core.o > | In file included from drivers/usb/musb/musb_core.c:108: > | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output > ... select CONFIG_USB_GADGET_MUSB_HDRC > | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 > | make[2]: Leaving directory > `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' > > > > > 2 Case of USB OTG (On The Go) Device > > > defconfig looks like: > # > # OMAP 343x high speed USB support > # > # CONFIG_USB_MUSB_HOST is not set > # CONFIG_USB_MUSB_PERIPHERAL is not set > CONFIG_USB_MUSB_OTG=y > # CONFIG_USB_GADGET_MUSB_HDRC is not set > CONFIG_USB_MUSB_HDRC_HCD=y > CONFIG_MUSB_PIO_ONLY=y > # CONFIG_USB_MUSB_DEBUG is not set > > Build error: > > make[2]: Entering directory > `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' > | CC drivers/usb/musb/musb_core.o > | In file included from drivers/usb/musb/musb_core.c:108: > | drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output > ... select CONFIG_USB_GADGET_MUSB_HDRC > | drivers/usb/musb/musb_core.c: In function 'musb_free': > | drivers/usb/musb/musb_core.c:1819: error: 'dev_attr_srp' undeclared > (first use in this function) > | drivers/usb/musb/musb_core.c:1819: error: (Each undeclared identifier is > reported only once > | drivers/usb/musb/musb_core.c:1819: error: for each function it appears > in.) > | drivers/usb/musb/musb_core.c: In function 'musb_init_controller': > | drivers/usb/musb/musb_core.c:2066: error: 'dev_attr_srp' undeclared > (first use in this function) > | drivers/usb/musb/musb_core.c:1891: error: label 'bad_config' used but > not defined > | make[2]: *** [drivers/usb/musb/musb_core.o] Error 1 > | make[2]: Leaving directory > `/home/schemish/gumstix/overo/overo-oe.2009/tmp/work/overo-angstrom-linux-gnueabi/linux-omap3-2.6.28-r0/git' > > > -- View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p23434035.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Steve S. <sa...@gm...> - 2009-05-08 16:05:35
|
On Fri, May 8, 2009 at 7:09 AM, jonmccune <jon...@cm...> wrote: > > Hello, > > Has anyone gotten past this issue? I'm getting the same > > drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... > select CONFIG_USB_GADGET_MUSB_HDRC > > error, regardless of whether CONFIG_USB_GADGET_MUSB_HDRC is disable or set > =y. I just did a quick build test to see if I could reproduce your issue. This is from the current top of tree (do a git pull to get there). I modified the defconfig: diff --git a/recipes/linux/linux-omap3-2.6.29/overo/defconfig b/recipes/linux/linux-omap3-2.6.29/overo/defconfig index c9b38a7..d2c138b 100644 --- a/recipes/linux/linux-omap3-2.6.29/overo/defconfig +++ b/recipes/linux/linux-omap3-2.6.29/overo/defconfig @@ -1584,10 +1584,10 @@ CONFIG_USB_MUSB_SOC=y # # OMAP 343x high speed USB support # -CONFIG_USB_MUSB_HOST=y +# CONFIG_USB_MUSB_HOST is not set # CONFIG_USB_MUSB_PERIPHERAL is not set -# CONFIG_USB_MUSB_OTG is not set -# CONFIG_USB_GADGET_MUSB_HDRC is not set +CONFIG_USB_MUSB_OTG=y +CONFIG_USB_GADGET_MUSB_HDRC=y CONFIG_USB_MUSB_HDRC_HCD=y # CONFIG_MUSB_PIO_ONLY is not set CONFIG_USB_INVENTRA_DMA=y Then I did a 'bitbake -c clean linux-omap3' and 'bitbake linux-omap3' The result was a successful build (I did not run it to test gadget functionality though): NOTE: Running task 545 of 545 (ID: 0, /home/sakoman/source/omap3-oe/org.openembedded.dev/recipes/linux/linux-omap3_2.6.29.bb, do_build) NOTE: package linux-omap3-2.6.29-r0: task do_build: started NOTE: package linux-omap3-2.6.29-r0: task do_build: completed NOTE: Tasks Summary: Attempted 545 tasks of which 525 didn't need to be rerun and 0 failed. NOTE: build 200905080746: completed Steve |
From: jonmccune <jon...@cm...> - 2009-05-08 19:32:03
|
Hi Sergey, Steve, Thanks for your replies. That fixed the build issue for me. Now I need figure out how to actually write some "gadget" code and get the Overo to show up as a peripheral. I was expecting more to happen when I plugged in a USB cable (typical A-to-mini-B) between my Debian Lenny workstation and the Gumstix board (nothing in syslog / dmesg on either system). I haven't done due diligence on Google yet though... Thanks again, -Jon -- View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p23451988.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: steve_carren <ste...@gm...> - 2009-07-30 16:51:25
|
Hello, Does anyone have _any_ USB gadget working with the Overo? I have followed the recommendations on this thread and have had a successful build with the 2.6.30 kernel. I load the driver manually on the Overo and it seems happy (here's the output): modprobe g_ether g_ether gadget: using random self ethernet address g_ether gadget: using random host ethernet address usb0: MAC aa:61:98:52:3a:5c usb0: HOST MAC 5a:2a:d7:97:ef:9d g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 g_ether gadget: g_ether ready ADDRCONF(NETDEV_UP): usb0: link is not ready ... but plugging in the cable from the OTG port to a PC (running Ubuntu) does nothing (no dmesg output, etc). I have tried two different cables, two host machines and the g_backed_storage driver as well. I was hoping that I may missed a step, before I started hacking the drivers... BTW, Steve Sakoman, I loved BeOS, You Rock! -SC sakoman wrote: > > On Fri, May 8, 2009 at 7:09 AM, jonmccune <jon...@cm...> wrote: >> >> Hello, >> >> Has anyone gotten past this issue? I'm getting the same >> >> drivers/usb/musb/musb_core.h:94:2: error: #error bogus Kconfig output ... >> select CONFIG_USB_GADGET_MUSB_HDRC >> >> error, regardless of whether CONFIG_USB_GADGET_MUSB_HDRC is disable or >> set >> =y. > > I just did a quick build test to see if I could reproduce your issue. > > This is from the current top of tree (do a git pull to get there). I > modified the defconfig: > > diff --git a/recipes/linux/linux-omap3-2.6.29/overo/defconfig > b/recipes/linux/linux-omap3-2.6.29/overo/defconfig > index c9b38a7..d2c138b 100644 > --- a/recipes/linux/linux-omap3-2.6.29/overo/defconfig > +++ b/recipes/linux/linux-omap3-2.6.29/overo/defconfig > @@ -1584,10 +1584,10 @@ CONFIG_USB_MUSB_SOC=y > # > # OMAP 343x high speed USB support > # > -CONFIG_USB_MUSB_HOST=y > +# CONFIG_USB_MUSB_HOST is not set > # CONFIG_USB_MUSB_PERIPHERAL is not set > -# CONFIG_USB_MUSB_OTG is not set > -# CONFIG_USB_GADGET_MUSB_HDRC is not set > +CONFIG_USB_MUSB_OTG=y > +CONFIG_USB_GADGET_MUSB_HDRC=y > CONFIG_USB_MUSB_HDRC_HCD=y > # CONFIG_MUSB_PIO_ONLY is not set > CONFIG_USB_INVENTRA_DMA=y > > Then I did a 'bitbake -c clean linux-omap3' and 'bitbake linux-omap3' > > The result was a successful build (I did not run it to test gadget > functionality though): > > NOTE: Running task 545 of 545 (ID: 0, > /home/sakoman/source/omap3-oe/org.openembedded.dev/recipes/linux/linux-omap3_2.6.29.bb, > do_build) > NOTE: package linux-omap3-2.6.29-r0: task do_build: started > NOTE: package linux-omap3-2.6.29-r0: task do_build: completed > NOTE: Tasks Summary: Attempted 545 tasks of which 525 didn't need to > be rerun and 0 failed. > NOTE: build 200905080746: completed > > Steve > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://www.nabble.com/Ethernet-gadget-on-Overo-Earth--tp20691020p24741931.html Sent from the Gumstix mailing list archive at Nabble.com. |