From: Bernhard Walle <bwalle@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add base_hi BAR for oxsemi_840
Date: Wed, 2 Jul 2008 00:24:21 +0200 [thread overview]
Message-ID: <20080702002421.084d4f1c@kopernikus.site> (raw)
In-Reply-To: <20080701150026.d0ee3457.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [2008-07-01 15:00]:
> >
> > --- a/drivers/parport/parport_pc.c
> > +++ b/drivers/parport/parport_pc.c
> > @@ -2877,7 +2877,7 @@ static struct parport_pc_pci {
> > * and 840 locks up if you write 1 to bit 2! */
> > /* oxsemi_952 */ { 1, { { 0, 1 }, } },
> > /* oxsemi_954 */ { 1, { { 0, -1 }, } },
> > - /* oxsemi_840 */ { 1, { { 0, -1 }, } },
> > + /* oxsemi_840 */ { 1, { { 0, 1 }, } },
> > /* aks_0100 */ { 1, { { 0, -1 }, } },
> > /* mobility_pp */ { 1, { { 0, 1 }, } },
> > /* netmos_9705 */ { 1, { { 0, -1 }, } }, /* untested */
>
> My parport knowledge doesn't permit me to understand how serious the
> just-fixed bug was. Non-functional parport?
>
> If so, this looks like a 2.6.26 and 2.6.25.x fix?
No, for good old printers, everything works. It's just that ECR
register was not available (the base_hi stuff). Because of that,
the TRISTATE detection did not work, which meant that for me my
self-built logic analyzer which uses the parallel port did not work.
Just merge in 2.6.27 is enough. :)
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
prev parent reply other threads:[~2008-07-01 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 21:45 Bernhard Walle
2008-07-01 22:00 ` Andrew Morton
2008-07-01 22:24 ` Bernhard Walle [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=20080702002421.084d4f1c@kopernikus.site \
--to=bwalle@suse.de \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®