From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
linuxppc-dev@ozlabs.org,
Konstantinos Margaritis <markos@codex.gr>,
linux-ide@vger.kernel.org, rmk@arm.linux.org.uk,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [PATCH] fix sata_sil compilation on non-DMI platforms
Date: Tue, 12 May 2009 08:31:44 +1000 [thread overview]
Message-ID: <1242081104.304.12.camel@pasglop> (raw)
In-Reply-To: <20090511194410.46641214@lxorguk.ukuu.org.uk>
On Mon, 2009-05-11 at 19:44 +0100, Alan Cox wrote:
> > Ideally the DMI subsystem should be provided wrappers for platforms
> > without DMI, rendering patches like this unnecessary.
>
> Interesting question - is the PPC OpenFirmware machine information
> mappable onto the DMI space ? or the various static bits of name
> information in the various ARM and the like machine descriptions.
>
> If not which bits are similar enough we could replace dmi at the high
> level with an abstract interface for system/vendor/... that was ?
The one thing we could try to map would be the device-tree "compatible"
property which would contain vendor,system tuples from more specific to
more generic with which the machine is compatible with.
Of course I would argue the other way around and create a device-tree
from the DMI data :-)
Cheers,
Ben.
next prev parent reply other threads:[~2009-05-11 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 17:09 [PATCH] fix sata_sil compilation on non-DMI platforms Konstantinos Margaritis
2009-05-11 18:12 ` Jeff Garzik
2009-05-11 18:23 ` Lennert Buytenhek
2009-05-11 18:44 ` Alan Cox
2009-05-11 18:44 ` Alan Cox
2009-05-11 22:31 ` Benjamin Herrenschmidt [this message]
2009-05-11 19:30 ` Lennart Sorensen
2009-05-12 9:09 ` Mikael Pettersson
2009-05-12 9:26 ` Jeff Garzik
2009-05-15 11:11 ` Mikael Pettersson
2009-05-15 17:49 ` Jeff Garzik
2009-05-15 22:46 ` Mikael Pettersson
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=1242081104.304.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=buytenh@wantstofly.org \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=markos@codex.gr \
--cc=rmk@arm.linux.org.uk \
/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.