hCO[Gf`?lHK2@d]^CT1A^BL@[^6iTbKebAoFY`   
      
   Hallo Doug,   
      
   "Doug Bissett"  schrieb    
   im Newsbeitrag news:SKfw30zmCGmZ-pn2-2Ud63S5H4rLS@blah.blah.com...   
   > On Sat, 24 Dec 2011 08:56:28 UTC, "Lars Erdmann"   
   >  wrote:   
   >   
   >> Then you are a lucky man and there is nothing for you to do !   
   >   
   > There is lots that I can do  :-)   
   >   
   >> It's all so damn complicated to correctly INITIALIZE the HC HW: there is    
   >> a   
   >> relationship between an EHCI host controller and   
   >> its associcated UHCI/OHCI "companion" host controllers. I am not sure but   
   >> they even might partially share the very same HW !   
   >> On some systems it's important that the EHCI host controllers claims   
   >> ownership of the HC BEFORE the companion controller has a chance to do    
   >> the   
   >> same. On other systems this does not seem to matter.   
   >> The USB specs for UHCI/OHCI/EHCI don't really go into this level of    
   >> detail   
   >> to be of any help. It's all trial and error.   
   >   
   > I just tried it on a fifth machine. No problems with the order of   
   > statements in CONFIG.SYS. All of these systems are quite different.   
   > Some are using ACPI (3.18, or 3.19), and a couple of them are using   
   > the old APM support. Of course, some of them do have problems caused   
   > by ACPI, but they do work, once I found the right combination of   
   > parameters. I doubt if your USB drivers will fix problems in ACPI.   
      
   You need to wait until the new version of ACPI is released.   
   No more parameters. And it works right out of the box for most systems.   
   I am also testing my HC drivers in conjunction with the new ACPI driver.   
   I am in contact with the ACPI developer if I think there is some problem in   
   conjunction with ACPI.   
   Unfortunately, as always in PC industry, systems are so different that   
   there is always a chance that some BIOS/ACPI code is broken.   
   But this is something Linux also struggles with.   
      
   > I have one more old ThinkPad 390x to try it on, but it has only a UHCI   
   > adapter (or perhaps an OHCI adapter). There is no EHCI adapter. Works   
   > fine...   
      
   This is the easier case to handle. Since in this case there is no "handover    
   hassle".   
      
   >> For USBD.SYS: I recently added some stuff that brings it closer to the    
   >> IBM   
   >> driver (while also having introduced a fix that is NOT in the IBM driver    
   >> +   
   >> some other optimizations + "to be on the safe side" changes).   
   >> Now, the driver might even be in the same shape as the 10.162 driver. But   
   >> again, for some people, this modified driver does not properly work    
   >> compared   
   >> to the IBM driver. It needs more feedback. It's in its early stages.   
   >   
   > All that I can say, is that it has given me no trouble, yet.   
      
   If there is, just raise a bug (see readme.txt). But do not expect an    
   immediate response.   
   USBD.SYS is currently a side-track. I just have too little time to tackle it    
   all ....   
      
      
   Lars    
      
      
   --- Internet Rex 2.31   
    * Origin: Arcor (1:261/20.999)