Defining new section for bus driver init
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 3 lines
I like it. Are you going to want to move the other busses to this (sbus, mca, ecard, zorro, etc.)?
Yes, though I don't have a way to test them...
Quoted 3 lines
Don't add USB to the list of busses that should be
moved to this scheme, it works just fine today in the initcall section (after pci starts up.)
Ok, fine. My main concern was to remedy the root buses of the system. I don't believe that USB is such a thing, except maybe on some ARM systems?
-pat
Quoted 3 lines · Patrick Mochel
Quoted 2 lines
I like it. Are you going to want to move the other busses to this (sbus, mca, ecard, zorro, etc.)?
Yes, though I don't have a way to test them...
Not a problem, I'm sure you'll find an army of testers on l-k.
Signature · 2 lines
| Dave Jones. http://www.codemonkey.org.uk | SuSE Labs
Quoted 6 lines · Dave Jones
Quoted 3 lines · Patrick Mochel
Quoted 2 lines
I like it. Are you going to want to move the other busses to this (sbus, mca, ecard, zorro, etc.)?
Yes, though I don't have a way to test them...
Not a problem, I'm sure you'll find an army of testers on l-k.
Ok, as I'm converting the drivers, I find that some have the option of modular compilation, like isapnp and irda. In theory, it seems that each of the bus drivers could be compiled modular. But, how do you define it in the section?
I was thinking something like this:
#ifdef MODULE
#define __devsubsys_init(fn) \ module_init(fn); #else #define __devsubsys_init(fn) \ static initcall_t __devsubsys_##fn __devsubsys_call = fn;
#endif
Thoughts?
-pat