> However, I've not looked at how (for example) the lp code interacts
> with the parport, this maybe a problem. If it *knows* which port it
> wants, it should be able to request the appropriate char-dev-xxx (or
> perhaps an alias) to get the right stuff loaded.
The way it works is that when lp loads it tells the generic parport layer
about itself, so that it gets notified about new ports as they are
registered (by the port drivers).
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/