tong changda wrote:
Hello,
The problem is figured out!My two lubbock are both pxa250 based.(But all
people think it is pxa26x).I am very very sorry to waste your precious
time on solving such meaningless question.:-( . Yes pxa250 has bugs as
driver's comments says,So the problem is hardware-related.Thank you
You misunderstood me. The problem I referred to isn't normally severe,
even though Intel had to fix it by adding a new register in the PXA 255.
(In some cases it can be severe ... but there's no evidence that's what
you were seeing.) You were just causinging that problem by turning up the
debug message volume too high for that chip, so that it affected timings;
Since you said at first that your hardware was pxa26x based, I assumed
that wouldn't be an issue.
We know that the RNDIS code can work on the pxa250; I think most of the
original work was done on a B1 chiprev. The reason it doesn't seem do
so right now has more to do with nobody having had time to fully debug
and test the 2.6 version than anything else. All the pieces work, it's
just integrating them on PXA 25x/26x/21x that's an issue.
again for your board knowledge to save me lots of times to locate
problem. Now I will continue to test rndis based on Intel
Mainstone(pxa27x). Best regards,
Well, good luck in that. Someone needs to write a pxa27x_udc driver.
That looks to fix some of the worst issues with PXA 25x/26x/21x UDC,
but I don't think the same driver would work.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
