[Prism54-devel] [prism54-usb] DWL-G122 and FW 2.4.6.0 differences

[Ian Kent]

On Fri, 3 Dec 2004, Feyd wrote:

To save possible confusion and frustration I must say that I'm not 
familiar with any of the subsystems here (yet).

Also I've not yet familiar with the code yet either.

Time is also in short supply for me as I'm pretty much fully commited to
other things. But you get that.

Hopefully, this will not be to much of a hastle and I'll be able to 
contribute to the project in some small way.

> On Fri, 3 Dec 2004 15:52:36 +0800 (WST)
> Ian Kent <raven at themaw.net> wrote:
> 
> > 
> > Given that the DWL-G122 using firmware 2.4.6.0 appears to have different 
> > offsets for (at least) the MAC address and the frequencies in the 
> > management frame, how should we handle this?
> 
> I doubt that the API differs among the SotfMAC firmwares (it is possible
> though). More likely the frame start doesn't have to match an offset after
> the USB transfer start, rather it is marked somehow. If that is the case
> we can find how by comparing the frames. Can you post your frame and the
> different one? Mine folows.

Yep. Looking at your frames below the difficulty with what I'm seeing is 
possible way earlier. I'll have to investigate further before we can have 
a meaningfull discussion.

All that I've done is extract the firmware, grab the arch project, add my 
device id, compile and plug in the device. What I got from that is at 
http://themaw.net/mess-2.bz2 in case you want to have a look.

> 
> the received frame starts at 0x4a, then is received I don't know what,
> then two frames transmitted, both start at 0x24
> 
> [OUT >18342 <18343 +1     ]     01 -> 00000000: 6c 07 02 00 ba 00 00 00 00 00 00 00 00 00 00 00
       ^^^^^^^^^^^^^^^^
This is nothing like what I get. So this is likely my first problem.

I get stuff like:

[OUT >0     <0     +152899]     0d -> 00000000: 1f 00 2c 00 00 00 00 00 00 01
[OUT >0     <0     +152900]     0e -> 00000000: 0f 08 18 00 00 40 04 40 00 00
[IN  >0     <0     +153050]     82 <- 00000000: 0c 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                                   -> 00000010: 00 80 00 04 00 00 00 00 0c 00 00 00 00 00 fc 03
                                   -> 00000020: 47 4d 55 aa 00 00 00 00 ff ff ff ff 09 00 01 00
                                   -> 00000030: 58 58 58 58 58 58 00 00 00 00 00 00 00 00 00 00
                                   -> 00000040: 04 00 01 01 00 0f 3d fa 5e bc 0b 00 01 10 00 00
                                   -> 00000050: 0f 00 8b 03 01 00 ff 03 00 00 09 00 03 00 01 00

down to 0x41b.

The above is the frame I get after, what appears to be interupt service 
routine setup. You'll probably need to look at the log above to make sense 
of what I'm saying.

Ian