>> >
>> >> > insmod usbdfu.o -----------missing
>> >> > insmod at76c503.o ---------have
>> >> > insmod at76c503-rfmd.o -----have
>> >>
>> >
>> >> Otherwise you need to download the debianimage file
>> >
>> > Anyone have a usbdfu.o file they could email me? If not, what
>> > is the link to the debianimage file?
>>
>> I think the mailing list will eat the attachment,
>
> yes - large BURP!!
>
>> but I have attached
>> usbfu.o... The link to the debian tarball is
>> here(http://www.embeddedx86.com/downloads/Linux/ARM/debian256-5-6-2005.tar.bz2).
>> <http://www.embeddedx86.com/downloads/Linux/ARM/debian256-5-6-2005.tar.bz2%29.>
>> I double checked and the module is in the tarball...
>>
>> //Eddie
>>
> I'm not confused - I'm just being myself......
>
> Ok, the threads I read said "usbdfu.o". The debian tar file has
> at76_usbdfu.o.
> So... are usbdfu and at76_usbdfu the same ?
>
> I did insmod usbcore - ok
> insmod at76 usbdfu - ok
> ins at76c503 - ok
> ins at76c505-rfmd
> Using
> /lib/modules/2.4.26-vrs1-cirrus-1-2-1-ts6/kernel/drivers/net/wireless/at76c503/at76c505-rfmd.o
> insmod: unresolved symbol request_firmware
> insmod: unresolved symbol release_firmware
The USB hotplug scripts need to handle this because they need to load the
firmware during a small time frame. By default Debian (on a CF card or USB
flash drive) should handle all of this by default. If you are booting to
the onboard flash you would need to edit your hotplug scripts and move the
firmware(/usr/lib/hotplug/firmware) over to the onboard flash...
//Eddie
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|