Workarounds in generic EHCI code
raj at semihalf.com
Fri Mar 7 15:03:15 UTC 2008
I'd like to hear comments on the proper way of handling non-standard behaviour
of a host controller when a workaround needs to be aplied at the shared code
level. In the following I followed an example of existing VIA/ATI chip workaround:
The respective flags are potentially set in platform-specific attachment
driver code, which knows if they apply etc.
Does anybody see a better way to handle such cases?
More information about the freebsd-usb