From: matthew@wil.cx (Matthew Wilcox)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH,RFC] PCI: deal with device incorrectly reporting I/O decoding being enabled
Date: Sun, 8 Nov 2009 08:23:10 -0700 [thread overview]
Message-ID: <20091108152310.GA16033@parisc-linux.org> (raw)
In-Reply-To: <20091108090451.GA20529@n2100.arm.linux.org.uk>
On Sun, Nov 08, 2009 at 09:04:51AM +0000, Russell King - ARM Linux wrote:
> On Sat, Nov 07, 2009 at 08:03:05AM -0700, Matthew Wilcox wrote:
> > I'm OK with this ... it might provoke bugs in some _other_ piece of hardware,
> > but that seems pretty unlikely.
>
> Please remember that some ARM hardware only has the capability to read
> and write full 32-bit quantities of configuration space, which means
> writing the control register can result in the status register being
> written as well.
>
> That shouldn't be a problem, but is merely something else to consider
> which isn't obvious.
Wow, that's horrid. You must have to special case each config register
that's accessed in a 16-bit way, since some bits are 'preserve' and others
are 'write 1 to clear'. What a nightmare.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-11-08 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 13:56 [PATCH, RFC] PCI: deal with device incorrectly reporting I/O decoding being enabled Lennert Buytenhek
2009-11-07 15:03 ` [PATCH,RFC] " Matthew Wilcox
2009-11-08 9:04 ` Russell King - ARM Linux
2009-11-08 15:23 ` Matthew Wilcox [this message]
2009-11-08 15:41 ` Russell King - ARM Linux
2009-11-08 16:15 ` Matthew Wilcox
2009-11-10 0:35 ` Dan Williams
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=20091108152310.GA16033@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).