Will Newton wrote:
> On Tue, 20 Mar 2001, Jeff Garzik wrote:
> > 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 seems pretty unequivocal to me, I'm not sure how easy it is to
> explain to a user that irq=none doesn't do what it says.
For this specific case, Via motherboards, we know exactly whether or not
an interrupt was assigned to the parallel port, and whether or not the
parallel port is in an interrupt-driven mode. Attempting to pretend
that the parallel port is not in an interrupt driven mode by passing
irq=none is folly.
If irq=none is passed to tell the Via code to -force- the parallel port
into a non-irq-driven mode is one thing. If irq=none is passed to hide
a problem with spurious interrupts, we need to fix that problem, not
hide it.
So as I see it, I should fix the Via code to read (only!) the parallel
port configuration from BIOS, and set up the parallel port that way. I
still am not convinced that irq=<anything> should affect the Via code at
all. Maybe I can print out a message "irq=foo ignored".
Optionally, I could handle irq=none by force-disabling the parallel
port's interrupt driven modes, if they are active. I don't want to do
this, but may be forced to by circumstance...
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full mooon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
