From: Tim Waugh <twaugh@redhat.com>
To: Dave Garry <daveg@firsdown.demon.co.uk>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.4.12 / linux-2.4.13 parallel port problem
Date: Wed, 24 Oct 2001 14:36:01 +0100 [thread overview]
Message-ID: <20011024143601.M7544@redhat.com> (raw)
In-Reply-To: <3BD6BF43.D347719B@firsdown.demon.co.uk>
In-Reply-To: <3BD6BF43.D347719B@firsdown.demon.co.uk>; from daveg@firsdown.demon.co.uk on Wed, Oct 24, 2001 at 02:16:51PM +0100
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On Wed, Oct 24, 2001 at 02:16:51PM +0100, Dave Garry wrote:
> With kernel 2.4.12 and 2.4.13 the parallel port on
> my machine looks like this according to dmesg:
>
> parport0: PC-style at 0x378 [PCSPP,TRISTATE]
Yes. It's showing you what modes it is prepared to use.
> Under 2.4.10 is looks like this:
[...]
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,ECP]
A bug; it was showing you what modes the hardware was capable of,
_despite_ knowing that it wasn't going to use it.
The parport driver will only use ECP and parallel port FIFO modes if
it has an IRQ to use. Try 'irq=auto'.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-10-24 13:35 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 [this message]
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
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=20011024143601.M7544@redhat.com \
--to=twaugh@redhat.com \
--cc=daveg@firsdown.demon.co.uk \
--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