From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] generic check_legacy_ioport
Date: Wed, 25 Apr 2007 10:09:03 +1000 [thread overview]
Message-ID: <1177459743.14873.167.camel@localhost.localdomain> (raw)
In-Reply-To: <20070424185402.GA16077@aepfle.de>
On Tue, 2007-04-24 at 20:54 +0200, Olaf Hering wrote:
> On Tue, Apr 24, Olaf Hering wrote:
>
> > > And also check now if the parent is "isa". Just to be sure. If a
> > > platform won't match that, then it will need it's own
> > > check_legacy_ioport which is fine with me.
> >
> > Do you think a device_type fdc, i8042 or ipmi will appear outside an isa
> > node?
>
> Does anyone know where those ipmi devices appear in the device-tree?
Somebody with an up-to-date qs21 device-tree at hand ?
Ben.
next prev parent reply other threads:[~2007-04-25 0:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 21:07 [PATCH] generic check_legacy_ioport Olaf Hering
2007-04-17 21:22 ` Arnd Bergmann
2007-04-17 23:28 ` Segher Boessenkool
2007-04-20 18:51 ` Olaf Hering
2007-04-22 5:15 ` Milton Miller
2007-04-22 6:46 ` Olaf Hering
2007-04-23 8:15 ` [PATCH] " Olaf Hering
2007-04-24 0:53 ` Benjamin Herrenschmidt
2007-04-24 11:25 ` Olaf Hering
2007-04-24 15:45 ` Milton Miller
2007-04-24 18:54 ` Olaf Hering
2007-04-24 22:01 ` Arnd Bergmann
2007-04-25 0:12 ` Benjamin Herrenschmidt
2007-04-25 1:54 ` Segher Boessenkool
2007-04-25 7:49 ` Arnd Bergmann
2007-04-25 13:33 ` Segher Boessenkool
2007-04-25 22:02 ` Arnd Bergmann
2007-04-25 0:09 ` Benjamin Herrenschmidt [this message]
2007-04-24 22:34 ` Benjamin Herrenschmidt
2007-04-25 20:36 ` Olaf Hering
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=1177459743.14873.167.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
/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).