On Tue, Mar 20, 2001 at 11:21:10PM -0500, Jeff Garzik wrote:
> The current Via-specific parport_pc.c code forces on the best possible
> parallel port modes the chip can handle. In retrospect, what it should
> be doing is reading the configuration BIOS has set up, and not touching
> it.
Yes, I think you are right.
> I am not sure that I agree, however, that an "irq=none" on the kernel
> cmd line should affect the operation of the Via code. I would much
> rather fix the Via code as I suggest above.
irq=none should definitely be honoured, or else the user has to reboot
in order to debug problems with printing. The user's io=, irq= and
dma= settings should always be honoured. IMHO.
When irq=auto, the BIOS settings should be used.
Case in point: until very recently there was a bad problem in the
irq-driven printing path. But only people with Via chipsets were
reporting it, and it didn't go away with 'irq=none' (which parport.txt
says to do in order to trouble-shoot). It makes Via chipsets the
exception, and it's confusing IMHO (it confused me, anyhow).
Tim.
*/
--UJhykcm+BCcdfd3/
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6uHymONXnILZ4yVIRApohAJ4ka7ZnTSjHMZkaG6Hs+rHCtMviSQCdE1NP
WWfbgAXhem32s9SaGMQfIjk=
=ojRc
-----END PGP SIGNATURE-----
--UJhykcm+BCcdfd3/--
-
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/