On Mon, 3 Oct 2005, Yedidyah Bar-David wrote: > Fine, but why does it work with 2.6.8-rc1? > Maybe, for example, it is indeed a hardware bug, which didn't manifest > itself in 2.6.8-rc1 because there was somewhere a larger delay that let > the bad hardware manage to do its job, and rc2 shortened that delay. > Wouldn't it make sense to make the delay larger back?
Yes. If you can find the delay in question, it can be lengthened. > As I said in the first message, BTW, I do know for sure that the > hardware is bad. But because it always worked for me well, and still > does on some versions, I thought the only problem with it is in a > specific part of the memory, not in other parts like the firmware. If > you are right, and this indeed should never happen with good hardware, > then > 1. I am much releaved, and might put the machine to production even > without solving this, as I do not particularly care about the specific > pen - only used it for testing, > 2. It's still a question whether we want linux to support bad hardware > if possible. If there's a reasonably non-invasive way of doing it, we will try to support the hardware. > > Also keep in mind that sometimes failures occur at random. You might get > > fooled into thinking a particular kernel release is at fault, simply > > because by pure chance the previous release ran okay in your test. > > I do not understand how that can be. I tried several times to plug it > in and out in both versions, and it always worked with rc1 and never > with rc2. Okay. Maybe there was a simple change that you'll be able to find. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
