> I don't think so, I'm thinking more specific entries in the
> EEPROM. We would need a debug version that dumps the EEPROM before
> we load the firmware. We will have to find data at some offset,
> which reliably would tell us, whether we deal with a ZD1211B
> instead of a ZD1211. Just classical r
Hi Sebastian,
Yes, we are talking about 2.6.18. But looks like our ditributor gave
us the rootfs which is minimal as we are working on embedded system.
I'll try to build the complete RFS
specially w.r.t. udev and then try it out.
thanks
Nazim
On 8/16/07, Sebastian Siewior <[EMAIL PROTECTED]> wro
Hi Sebastian,
Thanks for your response and providing some pointers. I see that in my
RFS, the entire "udev" stuff is missing. Both from /etc and lib folder.
(this is the embedded distribution I got from our hardware platform vendor).
Any specific step to set it up (any doc anywhere other than man
* Nazim Khan | 2007-08-16 13:29:20 [+0530]:
>I tried placing the firmware
>/libs/firmware/zd1211/
>/zd1211/
mine is in /lib/firmware/zd1211/ (note the s in your path, maybe a
typo).
>but it did not work? Where exactly this firmware is supposed to be.
Check your udev config, you should have a lin
Hi,
I am trying to bring up Zydas1211 chipset based AirLink card on my ARM
based system
with 2.6.18 kernel. While loading the zd1211rw.ko module it gives the
following error.
usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2
zd1211rw 1-1:1.0: couldn't load firmware. Error n