linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christian Krafft <krafft@de.ibm.com>,
	Olaf Hering <olaf@aepfle.de>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] generic check_legacy_ioport
Date: Wed, 25 Apr 2007 15:33:05 +0200	[thread overview]
Message-ID: <3f8a4cde6b06ee98203d62dc33c1630f@kernel.crashing.org> (raw)
In-Reply-To: <200704250949.17795.arnd@arndb.de>

>> SLOF/JS21 (at least some versions of it) have an "ipmi"
>> node on the "isa" bus. =A0And the kernel ipmi driver actually
>> works on it, too (no idea about the currently proposed
>> scanning though -- but the principle is correct at least).
>
> 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.

Drat.  Why not?

> If the ipmi node on the ISA bus is located at the standardized
> legacy I/O port range, it should get found by the later probing,
> if check_legacy_ioport allows it.

"Standardised" hahaha.  No, it is at some other
address.

> 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.

That sounds like the only option then.  Does
this have to be done per platform though?  It
sounds perfectly safe to do it in more generic
code.


Segher

  reply	other threads:[~2007-04-25 13:33 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 [this message]
2007-04-25 22:02                 ` Arnd Bergmann
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=3f8a4cde6b06ee98203d62dc33c1630f@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=krafft@de.ibm.com \
    --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).