From: Tim Waugh <twaugh@redhat.com>
To: bill davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.12 / linux-2.4.13 parallel port problem
Date: Thu, 25 Oct 2001 16:52:26 +0100 [thread overview]
Message-ID: <20011025165226.T7544@redhat.com> (raw)
In-Reply-To: <20011024230917.H7544@redhat.com> <ioWB7.5038$rR5.921319585@newssvr17.news.prodigy.com>
In-Reply-To: <ioWB7.5038$rR5.921319585@newssvr17.news.prodigy.com>; from davidsen@tmr.com on Thu, Oct 25, 2001 at 03:41:02PM +0000
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
On Thu, Oct 25, 2001 at 03:41:02PM +0000, bill davidsen wrote:
> Thank you... that sure doesn't jump out at someone, it generates no
> error message, etc.
See
<ftp://people.redhat.com/twaugh/patches/linux24/linux-ignore.patch>.
> Question: is this intended behaviour? I would think that you would
> normally want to just say irq=auto and let the driver find the io
> address just as it does normally.
It is intended behaviour. 'irq=auto' in this case didn't help because
the ECP chipset would not tell us what IRQ it was assigned (it just
said "it's set by jumpers, or alternatively I'm not telling you".
The problem with just specifying 'irq=7' on its own is that in the
case of there being more than one port it isn't clear what it should
mean.
When there is only one port to consider, it would make sense to use
that IRQ, but by the time we know how many ports there are we've
already decided not to use the supplied parameter. Patches
welcome. :-)
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-25 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 13:16 linux-2.4.12 / linux-2.4.13 parallel port problem Dave Garry
2001-10-24 13:36 ` Tim Waugh
2001-10-24 15:02 ` Dave Garry
2001-10-24 15:05 ` Tim Waugh
2001-10-24 15:53 ` Dave Garry
2001-10-24 21:54 ` bill davidsen
2001-10-24 22:09 ` Tim Waugh
2001-10-24 22:09 ` Tim Waugh
2001-10-25 15:41 ` bill davidsen
2001-10-25 15:52 ` Tim Waugh [this message]
2001-10-26 7:51 ` junio
2001-10-26 9:41 ` [patch] " Tim Waugh
2001-10-26 13:26 ` Dave Garry
2001-10-26 18:00 ` Tim Waugh
2001-10-28 4:14 ` junio
-- strict thread matches above, loose matches on Subject: below --
2001-10-24 14:46 f5ibh
2001-10-24 14:40 ` 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=20011025165226.T7544@redhat.com \
--to=twaugh@redhat.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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