--- Quote Start ---
originally posted by hippo@Feb 7 2007, 10:08 AM
please check if it is endian issue.
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=21328)
--- quote end ---
--- Quote End ---
Well, no one else came to my rescue with anything more profound than "an endian issue".
After some days of bug-hunting there were several issues related to "endianess" although a couple of them not at all obvious (to me!;o) but related to target CPU being in BE and USB2.0 & ISP1761 working in LE.
The biggest headache was composition of PIDs which are in QTD "token" to PTD 'token'. This ends up in DW2 of the QHA. In the posts above this second dword is zero using the Philips example code and shouldn't be, it was not converted to target CPU BE representation.
There were a couple of other similar issues with QTD representation. Once these were changed in the example driver it all sprung to life on PPC platform.
Hope this is of some help to others on non-LE CPUs.
Mike.