Hello,
> Here is a passage from around line 236 of zd_mac.c:

1) At which tree are you  you looking ?
I have the wireless-next-2.6 .git tree (updated as true for today).
There is no such comment in this file

2)
> I am going to make myself very unpopular
This is indeed so. Why should I not use the new driver ?
this firmware question  should be solved; it has nothing to do with
the new AD-HOC feature, which was added recently.

(Namely, the addition of the AD-HOC feadture has nothing to do with
this firmware question.)



Regards,
Mark R.


On Fri, Jul 11, 2008 at 9:34 PM, Hin-Tak Leung <[EMAIL PROTECTED]> wrote:
> I am going to make myself very unpopular to suggest this: use the vendor
> driver.
> Here is a passage from around line 236 of zd_mac.c:
>
>        /* At this point, the vendor driver downloads the whole firmware
>         * image, hacks around with version IDs, and uploads it again,
>         * completely overwriting the boot code. We do not do this here as
>         * it is not required on any tested devices, and it is suspected to
>         * cause problems. */
>
> So the zd1211rw code doesn't cope with your situation, and it is a known
> problem. I don't think you will get better answers at linux-wireless mailing
> list. The manufacturer is being a bit funny in mislabelling the devices.
> (And, really, you should have approached your distro's bug tracking system
> first).
>
> Mark Ryden wrote:
>>
>> Thanks!
>>
>>  I am looking for a more accurate answer. What should I do with this
>> firmware problem ? I do not want to delve into the zd1211rw code trying to
>> solve it.
>> Didn't other people encounter this problem ?  Maybe the zd1211rw
>> developers can
>> try to hint as to what the problem is ?
>>
>> Or maybe should I forward this message to the linux wireless mailing list
>> ?
>>
>> I am quite stuck with this problem,as you can see.
>>
>> Regards,
>> Mark Ryden
>>
>> On Fri, Jul 11, 2008 at 12:31 PM, Hin-Tak Leung
>> <[EMAIL PROTECTED]> wrote:
>>>
>>> Hmm, a quick look around the net says your message possibly comes from
>>> a 1211 lying about being a 1211b or vice versa.
>>>
>>> --- On Fri, 11/7/08, Mark Ryden <[EMAIL PROTECTED]> wrote:
>>>
>>>> From: Mark Ryden <[EMAIL PROTECTED]>
>>>> Subject: Re: [zd1211-devs] Problem when trying ad-hoc patch for zd1211rw
>>>> To: "Hin-Tak Leung" <[EMAIL PROTECTED]>
>>>> Cc: zd1211-devs@lists.sourceforge.net, [EMAIL PROTECTED],
>>>> [EMAIL PROTECTED]
>>>> Date: Friday, 11 July, 2008, 6:48 AM
>>>> Hello,
>>>> Thanks!
>>>>
>>>> Could it be a probelem of firmware version ?
>>>> How can I know what is the zd1211 firmware version I have ?
>>>>
>>>> I have these files under /lib/firmware/zd1211/:
>>>>
>>>> ls -al /lib/firmware/zd1211/
>>>> total 72
>>>> drwxr-xr-x 2 root root 4096 2008-05-14 19:48 .
>>>> drwxr-xr-x 3 root root 4096 2008-05-06 13:35 ..
>>>> -rw-r--r-- 1 root root 4018 2007-10-12 14:44 zd1211b_ub
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uph
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uphm
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211b_uphr
>>>> -rw-r--r-- 1 root root 3584 2007-10-12 14:44 zd1211b_ur
>>>> -rw-r--r-- 1 root root 4018 2007-10-12 14:44 zd1211_ub
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uph
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uphm
>>>> -rw-r--r-- 1 root root 5120 2007-10-12 14:44 zd1211_uphr
>>>> -rw-r--r-- 1 root root 3584 2007-10-12 14:44 zd1211_ur
>>>>
>>>> Regards,
>>>> Mark
>>>>
>>>> On Thu, Jul 10, 2008 at 6:41 PM, Hin-Tak Leung
>>>> <[EMAIL PROTECTED]> wrote:
>>>>>
>>>>> It is as it says, can't load firmware. If you had
>>>>
>>>> not used this USB nic
>>>>>
>>>>> on a machine before, it is likely you did not have
>>>>
>>>> them installed.
>>>>>
>>>>> They should be under /lib/firmware/zd1211 . In
>>>>
>>>> whatever mode,
>>>>>
>>>>> the driver still needs the firmware.
>>>>>
>>>>> Mark Ryden wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I have build and booted the last linux
>>>>
>>>> wireless-netx-2.6 tree:
>>>>>>
>>>>>> (
>>>>>>
>>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next-2.6.git)
>>>>>>
>>>>>> This tree includes the ad-hoc patch for zd1211rw.
>>>>>>
>>>>>> See:
>>>>>>
>>>> http://marc.info/?l=linux-wireless&m=121514338914960&w=2
>>>>>>
>>>>>> I tried to run these two actions:
>>>>>> (I must say that I did not tried this USB nic with
>>>>
>>>> other modes before on
>>>>>>
>>>>>> this
>>>>>> machine):
>>>>>>
>>>>>> iwconfig wlan0 mode ad-hoc
>>>>>> ifconfig wlan0 up
>>>>>>
>>>>>> I get:
>>>>>> SIOCSIFFLAGS: Connection timed out
>>>>>>
>>>>>> in in the kernel log I get:
>>>>>> Jul 10 15:40:53 kernel: usb 1-4: firmware version
>>>>
>>>> 0x4330 and device
>>>>>>
>>>>>> bootcode version 0x4810 differ
>>>>>> Jul 10 15:40:54 kernel: usb 1-4: USB control
>>>>
>>>> request for firmware
>>>>>>
>>>>>> upload failed. Error number -110
>>>>>> Jul 10 15:40:54 kernel: zd1211rw 1-4:1.0:
>>>>
>>>> couldn't load firmware.
>>>>>>
>>>>>> Error number -110
>>>>>>
>>>>>> What should I do ? is it has to do with some
>>>>
>>>> firmware mismatch ?
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> lsusb -v shows:
>>>>>> Bus 001 Device 003: ID 0ace:1211 ZyDAS 802.11b/g
>>>>
>>>> USB2 WiFi
>>>>>>
>>>>>> Device Descriptor:
>>>>>>  bLength                18
>>>>>>  bDescriptorType         1
>>>>>>  bcdUSB               2.00
>>>>>>  bDeviceClass          255 Vendor Specific Class
>>>>>>  bDeviceSubClass       255 Vendor Specific
>>>>
>>>> Subclass
>>>>>>
>>>>>>  bDeviceProtocol       255 Vendor Specific
>>>>
>>>> Protocol
>>>>>>
>>>>>>  bMaxPacketSize0        64
>>>>>>  idVendor           0x0ace ZyDAS
>>>>>>  idProduct          0x1211 802.11b/g USB2 WiFi
>>>>>>  bcdDevice           48.10
>>>>>>  iManufacturer          16
>>>>>>  iProduct               32
>>>>>>  iSerial                 0
>>>>>>  bNumConfigurations      1
>>>>>>  Configuration Descriptor:
>>>>>>   bLength                 9
>>>>>>   bDescriptorType         2
>>>>>>   wTotalLength           46
>>>>>>   bNumInterfaces          1
>>>>>>   bConfigurationValue     1
>>>>>>   iConfiguration          0
>>>>>>   bmAttributes         0x80
>>>>>>     (Bus Powered)
>>>>>>   MaxPower              500mA
>>>>>>   Interface Descriptor:
>>>>>>     bLength                 9
>>>>>> ...
>>>>>>
>>>>>> Regards,
>>>>>> Mark Ryden
>>>>>>
>>>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>>>>
>>>>>> Sponsored by: SourceForge.net Community Choice
>>>>
>>>> Awards: VOTE NOW!
>>>>>>
>>>>>> Studies have shown that voting for your favorite
>>>>
>>>> open source project,
>>>>>>
>>>>>> along with a healthy diet, reduces your potential
>>>>
>>>> for chronic lameness
>>>>>>
>>>>>> and boredom. Vote Now at
>>>>
>>>> http://www.sourceforge.net/community/cca08
>>>>>>
>>>>>> _______________________________________________
>>>>>> Zd1211-devs mailing list -
>>>>
>>>> http://zd1211.wiki.sourceforge.net/
>>>>>>
>>>>>> Unsubscribe:
>>>>
>>>> https://lists.sourceforge.net/lists/listinfo/zd1211-devs
>>>>>
>>>
>>>     __________________________________________________________
>>> Not happy with your email address?.
>>> Get the one you really want - millions of new email addresses available
>>> now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html
>>>
>>>
>>
>
>

-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Zd1211-devs mailing list - http://zd1211.wiki.sourceforge.net/
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs

Reply via email to