linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Garry <daveg@firsdown.demon.co.uk>
To: Tim Waugh <twaugh@redhat.com>
Cc: junio@siamese.dhis.twinsun.com, bill davidsen <davidsen@tmr.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] Re: linux-2.4.12 / linux-2.4.13 parallel port problem
Date: Fri, 26 Oct 2001 14:26:18 +0100	[thread overview]
Message-ID: <3BD9647A.B6244D05@firsdown.demon.co.uk> (raw)
In-Reply-To: <20011024230917.H7544@redhat.com> <ioWB7.5038$rR5.921319585@newssvr17.news.prodigy.com> <20011025165226.T7544@redhat.com> <7vofmuu9d7.fsf@siamese.dhis.twinsun.com> <20011026104125.Z7544@redhat.com>

Tim Waugh wrote:
> 
> On Fri, Oct 26, 2001 at 12:51:48AM -0700, junio@siamese.dhis.twinsun.com wrote:
> 
> > >From the original poster's description, 2.4.10 claimed to have
> > detected both address and irq for parport0, while 2.4.12,
> > according to the your response, could not tell that IRQ=7.  Do
> > you mean that the logic which made 2.4.10 to claime to have
> > detected IRQ=7 was faulty and the logic in 2.4.12 is being
> > careful not to misdetect?
> 
> Oh, I see.  No, this is a regression.  Please try this patch:

Firstly, I was unable to apply this patch on 2.4.13...

I'm now running 2.4.14-pre2, still had difficulty applying
the patch, and ended up patching parport_pc.c by hand. (?)

However, loading the parport_pc module, with NO arguments,
like I was doing up till 2.4.10, and it still does not
recognise the port as being in ECP mode:

[root@p450 /root]# modprobe parport_pc
[root@p450 /root]# dmesg -c
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
parport0: cpp_daisy: aa5500ff(98)
parport0: assign_addrs: aa5500ff(98)
parport0: faking semi-colon
parport0: Printer, Hewlett-Packard HP LaserJet 1100

If I load the module WITH arguments, something I've never
had to do in the past, it works:

[root@p450 /root]# modprobe parport_pc io=0x378 irq=7
[root@p450 /root]# dmesg -c
parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,ECP]
parport0: cpp_daisy: aa5500ff(98)
parport0: assign_addrs: aa5500ff(98)
parport0: faking semi-colon
parport0: Printer, Hewlett-Packard HP LaserJet 1100

I'm still unsure why I NEED to supply arguments
to this module.

Regards.

-- 
Dave Garry,
Daemon Solutions Ltd

  reply	other threads:[~2001-10-26 13:26 UTC|newest]

Thread overview: 15+ 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
2001-10-26  7:51               ` junio
2001-10-26  9:41                 ` [patch] " Tim Waugh
2001-10-26 13:26                   ` Dave Garry [this message]
2001-10-26 18:00                     ` Tim Waugh
2001-10-28  4:14                   ` junio

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=3BD9647A.B6244D05@firsdown.demon.co.uk \
    --to=daveg@firsdown.demon.co.uk \
    --cc=davidsen@tmr.com \
    --cc=junio@siamese.dhis.twinsun.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).