On Sat, 30 Mar 2013, Arnd Bergmann wrote:
I guess this means the onus is now on me to split up ohci-hcd into a
central library and separate bus drivers, like ehci-hcd...
The original plan in my teams was that Manjunath would do that after
he was done with the simple conversion of the
On Friday 29 March 2013, Alan Stern wrote:
I have not checked the details of all the changes; however, the basic
idea is okay as a stop-gap measure.
Ok, thanks.
I guess this means the onus is now on me to split up ohci-hcd into a
central library and separate bus drivers, like ehci-hcd...
Like the EHCI driver, OHCI supports a large number of different platform
glue drivers by directly including them, which causes problems with
conflicting macro definitions in some cases. As more ARM architecture
specific back-ends are required to coexist in a single build, we should
split those out
