linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
	linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>,
	cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] [PATCH] Implement check_legacy_ioport() on PS3
Date: Fri, 30 Mar 2007 15:44:02 +0200	[thread overview]
Message-ID: <d345e54b618b4b853cccf014b3b25589@kernel.crashing.org> (raw)
In-Reply-To: <1175219137.28116.2.camel@localhost.localdomain>

> I was thinking that we could have one single helper shared by most
> platforms who allow that legacy ISA crap which checks the device-tree
> for known ISA devices. That would cover PREP, CHRP and pSeries at
> least...

Make the helper check every device node under the ISA
node and translate the "reg" in there.  If the requested
legacy I/O region is a subset of the union of all those,
allow the access, otherwise not.  This should cover all
cases (well at least those with a valid device tree, heh).


Segher

  reply	other threads:[~2007-03-30 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30  0:02 [PATCH] Implement check_legacy_ioport() on PS3 David Woodhouse
2007-03-30  1:45 ` Olof Johansson
2007-03-30  1:43   ` David Woodhouse
2007-03-30  1:43   ` [Cbe-oss-dev] " Michael Ellerman
2007-03-30  1:47     ` Benjamin Herrenschmidt
2007-03-30  1:49     ` David Woodhouse
2007-03-30  1:45   ` Benjamin Herrenschmidt
2007-03-30 13:44     ` Segher Boessenkool [this message]
2007-04-06 21:32 ` Geoff Levand

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=d345e54b618b4b853cccf014b3b25589@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=benh@kernel.crashing.org \
    --cc=cbe-oss-dev@ozlabs.org \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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).