* David Brownell <[EMAIL PROTECTED]> [2004-09-03]: > > Great to know! But I don't think that'll explain Richard's > problem, unless his new arch was SMP or his early port > work didn't quite handle the IRQ/timer interaction right.
At the time we were seeing this, it was quite early into our porting to 2.6. There's a chance that at that stage we still had some bug under arch/sh64 still that was causing random memory corruption (we fixed quite a few in the early days). Since around the time the arch/sh64 stuff became basically stable, we've not seen any more USB2-related problems, though I forget the exact timeline of what was tried when versus when particular bugs were tracked down and fixed. sh64 is UP only, at least with any existing silicon, though we have been running successfully with CONFIG_PREEMPT for some time. We'll keep a note to watch out for any future USB2 misbehaviour and report back if we encounter any. But for now you might as well consider the sh64 issue closed I think. Cheers Richard -- Richard \\\ SH-4/SH-5 Core & Debug Architect Curnow \\\ SuperH (UK) Ltd, Bristol ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
