From: Tim Waugh <twaugh@redhat.com>
To: TimO <hairballmt@mcn.net>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Will Newton <will@misconception.org.uk>,
Mike Galbraith <mikeg@wen-online.de>,
linux-kernel@vger.kernel.org
Subject: Re: VIA audio and parport in 2.4.2
Date: Tue, 27 Mar 2001 19:21:23 +0100 [thread overview]
Message-ID: <20010327192123.L21068@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103211333440.1541-100000@dogfox.localdomain> <3AB8B877.D36E8719@mandrakesoft.com> <20010321144907.D1323@redhat.com> <3AB9664B.10451E6D@mcn.net>
In-Reply-To: <3AB9664B.10451E6D@mcn.net>; from hairballmt@mcn.net on Wed, Mar 21, 2001 at 07:41:15PM -0700
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
On Wed, Mar 21, 2001 at 07:41:15PM -0700, TimO wrote:
> 0x378: possible IRQ conflict! [Don't know why it always reports
> this]
I've been sending Linus a patch to remove this bogus warning for the
last few pre-patches.
> 0x378: ECP settings irq=<none or set by other means> dma=<none or set by
> other means>
[...]
> With no options in modules.conf, lp0 uses polling; with irq=auto
> dma=auto
> it uses interrupt-driven but no dma?.
It does its best to figure out the IRQ, even though the chipset won't
tell us. For the DMA channel, it doesn't even try to guess.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-03-27 18: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
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 [this message]
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=20010327192123.L21068@redhat.com \
--to=twaugh@redhat.com \
--cc=hairballmt@mcn.net \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--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