From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: Mike Galbraith <mikeg@wen-online.de>,
linux-kernel@vger.kernel.org,
Will Newton <will@misconception.org.uk>
Subject: Re: VIA audio and parport in 2.4.2
Date: Tue, 20 Mar 2001 23:21:10 -0500 [thread overview]
Message-ID: <3AB82C36.C807B787@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103171951340.440-100000@mikeg.weiden.de> <Pine.LNX.4.33.0103190015080.8534-100000@dogfox.localdomain> <20010318192221.A27150@redhat.com>
Tim Waugh wrote:
>
> On Mon, Mar 19, 2001 at 12:16:26AM +0000, Will Newton wrote:
>
> > In /etc/modules.conf I have:
> >
> > options parport_pc irq=none
> >
> > but dmesg says:
> >
> > parport0: PC-style at 0x378 (0x778), irq 7, dma 3
> > [PCSPP,TRISTATE,COMPAT,ECP,DMA]
>
> Jeff, this is a bug with the Via code in parport_pc.c. Basically, the
> problem is that the code that detects the Via doesn't know what
> parameters you passed. I know about the problem, but I don't know the
> fix yet.
Will,
What are your parallel port settings in BIOS?
Do you have Plug-n-Play OS enabled in BIOS?
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.
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.
Time to look for and drag out the old Via laptop... Oh well, I needed
to debug the Via audio code some more anyway. :)
Jeff
--
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.
next prev parent reply other threads:[~2001-03-21 4:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 18:45 VIA audio and parport in 2.4.2 Will Newton
2001-03-16 10:53 ` Tim Waugh
2001-03-16 14:53 ` Will Newton
2001-03-17 7:09 ` Mike Galbraith
2001-03-17 17:46 ` Will Newton
2001-03-17 19:13 ` Mike Galbraith
2001-03-19 0:16 ` Will Newton
2001-03-19 0:22 ` Tim Waugh
2001-03-21 4:21 ` Jeff Garzik [this message]
2001-03-21 10:04 ` Tim Waugh
2001-03-21 13:37 ` Will Newton
2001-03-21 14:19 ` Jeff Garzik
2001-03-21 14:49 ` Tim Waugh
2001-03-22 2:41 ` TimO
2001-03-27 18:21 ` Tim Waugh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AB82C36.C807B787@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--cc=twaugh@redhat.com \
--cc=will@misconception.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox