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 a=
re=20
> really multi-I/O ones, and only load parport_serial when it will be able =
to=20
> 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.
*/
--YyxSosoRaUW6PdRh
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7OOedONXnILZ4yVIRAlERAKCpgANy9pD4NL1VByhyik8GcAobtACfXM89
gqsFdV8dBm7FWH5bBSeR4LQ=
=uNjP
-----END PGP SIGNATURE-----
--YyxSosoRaUW6PdRh--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/