On Tue, Jun 26, 2001 at 06:59:11PM +0100, Philip Blundell wrote:

> This would be a bit bad, because it would require people to guess
> whether they might have a card that parport_serial can drive and/or
> try loading the module to see what happens.

Not necessarily.  The module has a PCI device table, so a user-space
utility can figure it out and adjust /etc/modules.conf accordingly.

> I guess one option would be for parport_pc to somehow "know" what cards are 
> really multi-I/O ones, and only load parport_serial when it will be able to 
> find something to do.  Doesn't seem all that appealing though.

Replace parport_pc's "knowledge" with parport_serial's PCI device
table and a user-space utility, and that's kind of what I had in
mind.

> If you do that then the code will effectively be there all the time,
> even when it's not needed.  You might as well just compile it in to
> parport_pc.  To be honest, there isn't all that much of it so maybe
> this wouldn't be such a bad idea.

Perhaps.

Tim.
*/