All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Christian Krafft <krafft@de.ibm.com>,
	Olaf Hering <olaf@aepfle.de>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] generic check_legacy_ioport
Date: Thu, 26 Apr 2007 00:02:54 +0200	[thread overview]
Message-ID: <200704260002.54627.arnd@arndb.de> (raw)
In-Reply-To: <3f8a4cde6b06ee98203d62dc33c1630f@kernel.crashing.org>

On Wednesday 25 April 2007, Segher Boessenkool wrote:

> > It won'd be found by the of_platform_driver part of ipmi,
> > since devices on the ISA bus do not get added to the linux
> > device tree.
>=20
> Drat. =A0Why not?

We have a number of buses on which devices get automatically added
as of_devices into the Linux driver infrastructures. Which buses
are probed depends on the platform, it may include e.g. "soc",
"plb5" and "siliconbackplane", but no platform currently scans
the ISA bus.

> > We might still want to have the driver use a proper of_device,
> > which would require the maple platform code to add this device
> > during probing.
>=20
> That sounds like the only option then. =A0Does
> this have to be done per platform though? =A0It
> sounds perfectly safe to do it in more generic
> code.

I think the right solution would be to add automatic probing
of all ISA devices into the platform independent code. Besides
making IPMI work on JS21, it would result in the legacy serial
ports to show up in the right place in sysfs.

I am however worried about what other side-effects this change
could have on platforms that have a broken ISA device in their
device trees.

	Arnd <><

  reply	other threads:[~2007-04-25 22:03 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 [this message]
2007-04-25  0:09         ` Benjamin Herrenschmidt
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=200704260002.54627.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=krafft@de.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olaf@aepfle.de \
    --cc=segher@kernel.crashing.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.