On 08/30/12 14:49, Alejandro Martinez Ruiz wrote: > Some xHC drivers (most notably on Windows and BSD systems) read > the first capability registers using 1 and 2 bytes accesses, since > this is how they are defined in section 5.3 of the xHCI specs. > > Enabling these kind of read accesses allows Windows and FreeBSD > guests to properly recognize the host controller. > > As this is an exception to the general 4-byte aligned accesses rule, > we special-case the code path for capability reading and implement > checks to guard against wrong size/alignment combinations.
No need to do that by hand, the memory api can handle it. Can you check whenever usb-next (http://www.kraxel.org/cgit/qemu/log/?h=rebase/usb-next) works for you? thanks, Gerd
