On Wed, 2 Jun 2010 14:56:30 +0200
Koen Kooi k...@dominion.thruhere.net wrote:
How about add-on cards for e.g. BeagleBoard? It would be nice feature
if a kernel module for that particular add-on card can do the muxing
without needing to specify them on cmdline. I.e. if you are switching
* Jarkko Nikula jhnik...@gmail.com [100602 16:06]:
On Wed, 2 Jun 2010 14:56:30 +0200
Koen Kooi k...@dominion.thruhere.net wrote:
How about add-on cards for e.g. BeagleBoard? It would be nice feature
if a kernel module for that particular add-on card can do the muxing
without needing
Op 2 jun 2010, om 15:57 heeft Tony Lindgren het volgende geschreven:
* Jarkko Nikula jhnik...@gmail.com [100602 16:06]:
On Wed, 2 Jun 2010 14:56:30 +0200
Koen Kooi k...@dominion.thruhere.net wrote:
How about add-on cards for e.g. BeagleBoard? It would be nice feature
if a kernel module
On Wed, 2 Jun 2010 16:57:10 +0300
Tony Lindgren t...@atomide.com wrote:
Problem is that amount of expansion boards is practically unlimited so
patching bootloader and board file could come quite maintenance effort.
Of course there are some lets say generic boards but bunch of in-house,
* Jarkko Nikula jhnik...@gmail.com [100602 17:06]:
On Wed, 2 Jun 2010 16:57:10 +0300
Tony Lindgren t...@atomide.com wrote:
Problem is that amount of expansion boards is practically unlimited so
patching bootloader and board file could come quite maintenance effort.
Of course there
On Wed, Jun 02, 2010 at 04:45:48PM +0200, ext Tony Lindgren wrote:
Yeah having the modules do the platform device init and registration will
lead into nasty conflicts. The platform device registration really needs
to happen in the board-*.c files, not in the drivers.
yeah, unless you had a way
* Felipe Balbi felipe.ba...@nokia.com [100602 17:50]:
I have to agree modules are not supposed to change platform stuff.
On the other hand, that could be used by EHCI/OHCI to implement port
handoff on runtime:
mux all usb ports to ehci, if enumeration fails, remux ports to
ohci and try
Felipe Balbi wrote:
On Wed, Jun 02, 2010 at 04:45:48PM +0200, ext Tony Lindgren wrote:
Yeah having the modules do the platform device init and registration will
lead into nasty conflicts. The platform device registration really needs
to happen in the board-*.c files, not in the drivers.
