From: Tim Waugh <twaugh@redhat.com>
To: junio@siamese.dhis.twinsun.com
Cc: bill davidsen <davidsen@tmr.com>, linux-kernel@vger.kernel.org
Subject: [patch] Re: linux-2.4.12 / linux-2.4.13 parallel port problem
Date: Fri, 26 Oct 2001 10:41:25 +0100 [thread overview]
Message-ID: <20011026104125.Z7544@redhat.com> (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>
In-Reply-To: <7vofmuu9d7.fsf@siamese.dhis.twinsun.com>; from junio@siamese.dhis.twinsun.com on Fri, Oct 26, 2001 at 12:51:48AM -0700
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:
--- linux/drivers/parport/ChangeLog.irq Fri Oct 26 10:11:02 2001
+++ linux/drivers/parport/ChangeLog Fri Oct 26 10:37:36 2001
@@ -0,0 +1,8 @@
+2001-10-26 Tim Waugh <twaugh@redhat.com>
+
+ * parport_pc.c (parport_irq_probe): When ECR programmable IRQ
+ support fails, generate interrupts using the FIFO even if we don't
+ want to use the FIFO for real data transfers.
+ (parport_pc_probe_port): Display the ECR address if we have an
+ ECR, not just if we will use the FIFO.
+
--- linux/drivers/parport/parport_pc.c.irq Fri Oct 26 10:11:06 2001
+++ linux/drivers/parport/parport_pc.c Fri Oct 26 10:35:49 2001
@@ -2119,10 +2119,9 @@
if (priv->ecr) {
pb->irq = programmable_irq_support(pb);
- }
- if (pb->modes & PARPORT_MODE_ECP) {
- pb->irq = irq_probe_ECP(pb);
+ if (pb->irq == PARPORT_IRQ_NONE)
+ pb->irq = irq_probe_ECP(pb);
}
if ((pb->irq == PARPORT_IRQ_NONE) && priv->ecr &&
@@ -2255,7 +2254,7 @@
p->private_data = priv;
printk(KERN_INFO "%s: PC-style at 0x%lx", p->name, p->base);
- if (p->base_hi && (p->modes & PARPORT_MODE_ECP))
+ if (p->base_hi && priv->ecr)
printk(" (0x%lx)", p->base_hi);
p->irq = irq;
p->dma = dma;
Tim.
*/
next prev parent reply other threads:[~2001-10-26 9:41 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 ` Tim Waugh [this message]
2001-10-26 13:26 ` [patch] " Dave Garry
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=20011026104125.Z7544@redhat.com \
--to=twaugh@redhat.com \
--cc=davidsen@tmr.com \
--cc=junio@siamese.dhis.twinsun.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.