From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: keymap rule selection for non-DMI platforms
Date: Tue, 16 Aug 2011 21:47:32 +0000 [thread overview]
Message-ID: <20110816214732.GA32484@kroah.com> (raw)
In-Reply-To: <3483.1313087020@foxharp.boston.ma.us>
On Tue, Aug 16, 2011 at 09:39:37PM +0100, Daniel Drake wrote:
> On Tue, Aug 16, 2011 at 9:30 PM, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > Sure, if there is something we all can use, we will switch over to it.
> > Until that happens, hacks have to be maintained by the people relying
> > on them, not by udev upstream.
>
> You can use it. Just like many platforms (of varying architectures)
> already do in other contexts, all using unmodified Linus kernels.
>
> Device tree is a well-documented cross-platform way of providing
> hardware identification information (and in great detail) to the
> kernel. I think it is the system you are asking for. Am I right in
> saying that its location in /proc is the main downfall that you are
> criticising it for? (i.e. would your viewpoint change if it appeared
> in /sys tomorrow?)
What about all of the existing device tree work that has been going on
in the kernel for the past year? It should be in sysfs already, so why
not just use those files instead?
As for DMI being "desktop" specific, others agree, and tried to write
patches to rename everything. I think they were rightly shot down as it
would have broken lots of userspace code, so there's no problem with
putting this type of information into the dmi "namespace" as it is.
greg k-h
next prev parent reply other threads:[~2011-08-16 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 18:23 keymap rule selection for non-DMI platforms Paul Fox
2011-08-16 18:54 ` Paul Fox
2011-08-16 19:34 ` Kay Sievers
2011-08-16 20:09 ` Daniel Drake
2011-08-16 20:30 ` Kay Sievers
2011-08-16 20:39 ` Daniel Drake
2011-08-16 20:49 ` Paul Fox
2011-08-16 21:47 ` Greg KH [this message]
2011-08-16 22:27 ` Kay Sievers
2011-08-16 22:34 ` Kay Sievers
2011-08-16 22:37 ` Kay Sievers
2011-08-16 22:54 ` Daniel Drake
2011-08-16 23:35 ` Prarit Bhargava
2011-08-17 2:09 ` Karl O. Pinc
2011-08-17 3:32 ` Paul Fox
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=20110816214732.GA32484@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.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 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).