- The first is about the get_frame_number. I see that the 'glue' driver can provide a function to read this value and that's good news for me because there is an errata for this chips that specify the red value should be corrected. However, there are two places in the code where the OHCI_FRAME_NO(ohci->hcca) macro is called instead of hcd->driver->get_frame_number(hcd), on line 248 & 626 of ohci-hcd.
- The other problems is that this chip is Big Endian ( power pc ) and that all it's internal registers including the OHCI ones are big endian ... And that's a bigger problem. The 2.4 port for this processor just uses #ifdef #define ... to override any call to cpu_to_le16 or such function when needed. However I don't want that solution because I have another OHCI controler on the PCI bus that requires those ... So what should I do ?
Sylvain Munaut
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
