I conceed. The opl3 pnp patch still stands.
I will have to look again at why the sb driver wasn't finding the mpu.
Sigh
Mark
Mark Hindley
Director of the Music Centre
University of St Andrews
01334 462226/7
http://www.st-andrews.ac.uk/services/music
-
To unsubscribe from this list: send
> So why does the kernel command-line uart401=1 make a builtin uart401
> driver look for the mpu at 0x1 rather than persuade the sb driver to to do
> a pnp lookup for it?
Because the __setup string for it is uart401, the sb is sb=...
>
-
To unsubscribe from this list: send the line "unsubscri
>It changes the command line properties people already use. It also cannot be
>neccessary since 'uart401' is static.
So why does the kernel command-line uart401=1 make a builtin uart401
driver look for the mpu at 0x1 rather than persuade the sb driver to to do
a pnp lookup for it?
Mark Hindley
> 2) The other relates to the uart401 detection. If you build the sb driver
> into the kernel and then pass the commandline uart401=1 this is interpreted
> as the io parameter for the uart401 module not a command for the sb driver.
Of course. Module parameters are _not_ relevant for builtin driv
> 2) The other relates to the uart401 detection. If you build the sb driver
> into the kernel and then pass the commandline uart401=1 this is interpreted
> as the io parameter for the uart401 module not a command for the sb driver.
> I have renamed the uart401 detection command to uart401probe. Ob
5 matches
Mail list logo
