From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Loading drivers based on board identification
Date: Tue, 17 Jun 2008 23:17:55 +0100 [thread overview]
Message-ID: <20080617221754.GA17165@sirena.org.uk> (raw)
In-Reply-To: <20080617213105.4F96911D8063@mail23-dub.bigfish.com>
On Tue, Jun 17, 2008 at 02:31:03PM -0700, Stephen Neuendorffer wrote:
> I'm very interested in trying to factor out board data from the device
> tree, but for slightly different reasons, I think. (Although I don't
> exactly understand what you're proposing...)
Sorry, I should have gone into a *little* more detail about what DMI
information actually is. DMI provides device management data - you can
see the things that Linux supports in include/linux/dmi.h. Of most
relevance to what I'm talking about here is information like the board,
chassis and system manufactuer, product name and version though there is
other, more device tree style, information in there.
This information can be queried by drivers to allow them to override
default behaviour based on knowledge about the system in a similar way
to how OpenFirmware but of more relevance here is that it is also
possible for drivers to use the module autoloading infrastructure to
automatically load modules which provide dmi: module aliases (for
example, this is used by the dcdbas driver which interfaces to Dell
system management controllers to automatically load on Dell systems).
> I don't yet have a proposal, but I'd be curious to hear your thoughts.
My proposal would be to essentially clone at least the system
information bit of the DMI API to provide equivalent information.
prev parent reply other threads:[~2008-06-17 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 20:26 Loading drivers based on board identification Mark Brown
2008-06-17 21:31 ` Stephen Neuendorffer
2008-06-17 22:17 ` Mark Brown [this message]
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=20080617221754.GA17165@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=stephen.neuendorffer@xilinx.com \
/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).