Hi Brian,

partly. See [1] for more information. I'm currently stuck with a bug that 
hangs the bb when initiating the driver.

Felix

[1] https://groups.google.com/forum/#!topic/beagleboard/pdCUJ2HdkRE

On Tuesday, December 24, 2013 7:02:10 PM UTC+1, Brian Park wrote:
>
> Hi Felix,
> Have you had any success in getting GadgetFS working with BB?
>
> Brian
>
> On Thursday, October 3, 2013 1:54:15 PM UTC-7, [email protected]:
>>
>> Hi Chris,
>>
>> I'm trying to do something similar but so far without any luck. Did you 
>> succeed?
>>
>> Regards
>>  Felix
>>
>> On Thursday, January 28, 2010 7:31:55 PM UTC+1, Chris Veigl wrote:
>>>
>>> Hi all,
>>>
>>> I currently try to get USB device functionality (USB-gadget) working
>>> with  beagleboard and a recent kernel (2.6.31). My plan is to emulate
>>> a HID (mouse / keyboard) via gadgetfs.
>>>
>>> I use OpenEmbedded / bitbake as build environment and modified the
>>> kernel config
>>> as described here: http://wh1t3s.com/2009/05/11/oe-bitake-kernel-mods/
>>>
>>> I enabled all gadget-related stuff (e.g. the omap_udc, gadgetfs and
>>> other modules)
>>> and have them in my rootfs under  /lib/modules....
>>>
>>> however, when i try to get it running like described here:
>>> http://svcs.cs.pdx.edu/pipermail/usb-hacking/2007-March/000098.html ,
>>> I fail at the first steps (omap_udc.ko simply does not exist - using
>>> menuconfig i can only
>>> have this as a permanent module,  modprobe omap_udc fails.)
>>>
>>> the modules gadgetfs or g_ether cannot bind to the omap_udc driver.
>>>
>>> furthermore,    mount -t gadgetfs /dev/gadget   does not succeed
>>> (filesystem gadgetfs not known)
>>>
>>> I tried a lot with the kernel-config, but obviously I'm missing
>>> something.
>>>
>>> could you please help out ?
>>>
>>> regards,
>>> chris.
>>>
>>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to