From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Matthew Wilcox <willy@debian.org>
Cc: LaMont Jones <lamont@b180.mmjgroup.com>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] airo.c patch for hppa
Date: Wed, 4 Dec 2002 10:12:47 -0700 [thread overview]
Message-ID: <20021204171247.GA11629@dsl2.external.hp.com> (raw)
In-Reply-To: <20021204144454.P27991@parcelfarce.linux.theplanet.co.uk>
On Wed, Dec 04, 2002 at 02:44:54PM +0000, Matthew Wilcox wrote:
> Grant, I think this is a long-standing bug (Jan 2000!) in
> Dino's port IO macros.
It sounds like there is...
...
> That '& ~3' clears the bottom two bits of the address, so we always read
> from a 32-bit aligned address, even if we actually wanted to read the
> other 16-bit word or one of the other bytes.
The Dino ERS clearly says the AD[0:1] are used for IO Port space.
I gather IO_DATA behaves differently than MEM_DATA.
MEM_DATA definitely uses byte enables to manage subword bytes
and ignores the lower two bits of the address. The GSC byte enables
are forwarded to the PCI bus when doing subword MMIO reads.
Because MEM_DATA was added much later, it seems to have been implemented
with more insight into how GSC/PCI can interact.
> The PORT_OUT define doesn't mask that way:
Right.
...
> LaMont's doing a rebuild now to check it works, but this seems fairly
> obvious to me. Thoughts? (Can _anyone_ remember what they were thinking
> when they wrote code nearly three years ago? ;-)
You are on the right track. And no, I don't remember.
thanks,
grant
prev parent reply other threads:[~2002-12-04 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 5:06 [parisc-linux] airo.c patch for hppa LaMont Jones
2002-12-04 14:44 ` Matthew Wilcox
2002-12-04 17:12 ` Grant Grundler [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=20021204171247.GA11629@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=lamont@b180.mmjgroup.com \
--cc=parisc-linux@parisc-linux.org \
--cc=willy@debian.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.