Hi Torsten,
Now , I'm not sure about this header file. I know that we need it for the ptd-struct defined in ohci-isp1362.h, but why do we need stuff like that? And does anybody has an idea, why it's hardware-specific?
You are talking here about the bitfield.h, right? No, you don't need the methods currently used in the driver and you can implement the access differently so that you can eliminate the need for bitfield.h.
OK, I think changes on bitfield.h aren't so important now to get the driver working. But when I have time for it I will eliminate it.
Good to know :) I took a closer look at the manual of the chip and I assumed that, but it was good to be discussed.(4) We have a WLAN-Stick (Prism2-Chipset) and we are using the linux-wlan-ng project. We have no problem detecting the device. But when we try to load the wlan-modules (p80211, prism2_usb) and start the wlan-driver (wlanctl) we have a problem. The chip wants to read a td with lenght 3000 (bb8h) Bytes in bulk-mode. Is this value possible? I mean the buffer is 4096 (1000h) Byte, but ...
This length is OK, but you cannot cover all this payload with a single ptd (10 bits length limit in ptd, you know). Furthermore, it is not possible to transfer 3000 bytes of fullspeed data within one frame. You have to chop the large TD up.
I wonder if a ptd (philips transfer descriptor) is philips version of a transfer descriptor as described in the ohci-specs?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
