My configuration requires me to use a USB Keyboard and Mouse on the system I use for BeOS/Zeta/Haiku. The system BIOS supports legacy device emulation and I’m able to run everything from BeOS R5.0.3 to Zeta 1.5 without trouble. Somehow (probably because Haiku is missing one of the USB flavors - EHCI?)
Has anyone found a workaround for this issue? I’d really like to be more active in my Haiku testing.
The missing “flavor” is OHCI currently.
Even if EHCI is there, I suspect devices like mice/keyboards still use “slow” USB modes: UHCI/OHCI.
If your chipset only supports OHCI, I’m afraid you’ll be stuck waiting for completion of that spec.
Reading from Wikipedia
VIA, Intel chips uses UHCI/(USB 2.0 EHCI)
Other chips uses OHCI/(USB 2.0 EHCI)
From Wikipedia.
"In the version 1.x age, there were two competing HCD implementations, Open Host Controller Interface (OHCI) and Universal Host Controller Interface (UHCI). OHCI was developed by Compaq, Microsoft and National Semiconductor; UHCI was by Intel.
VIA Technologies licensed the UHCI standard from Intel; all other chipset implementers use OHCI. UHCI is more software-driven, making UHCI slightly more processor-intensive than OHCI but cheaper to implement. The dueling implementations forced operating system vendors and hardware vendors to develop and test on both implementations which increased cost.
During the design phase of USB 2.0 the USB-IF insisted on only one implementation. The USB 2.0 HCD implementation is called the Enhanced Host Controller Interface (EHCI). Only EHCI can support hi-speed transfers. Most of PCI-based EHCI controllers contain other HCD implementations called ‘companion host controller’ to support Full Speed and Low Speed devices. The virtual HCD on Intel and VIA EHCI controllers are UHCI. All other vendors use virtual OHCI controllers.
I have the same problem with wireless USB Keyb+Mouse. However, Dell Vostro 410 BIOS doesn’t have too many USB options (only High/Full Speed), so I’m stuck. Besides that, I can’t plug an IDE drive, so even with the ata drive it won’t boot. I’ll have to wait for ticket #5.