devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Andres Salomon <dilinger-pFFUokh25LWsTnJN9+BGXg@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: board identification in /sys
Date: Fri, 19 Aug 2011 12:23:06 +1000	[thread overview]
Message-ID: <20110819022306.GD30097@yookeroo.fritz.box> (raw)
In-Reply-To: <20110818121530.08946a6e-pFFUokh25LWsTnJN9+BGXg@public.gmane.org>

On Thu, Aug 18, 2011 at 12:15:30PM -0700, Andres Salomon wrote:
> I've been paying partial attention to the following thread:
> http://marc.info/?l=linux-hotplug&m=131352330625733&w=2
> 
> It's an interesting discussion.  I realize that
> moving /proc/device-tree to /sys would probably violate
> sysrq-rules.txt, but it would be nice to have a common way to
> represent things like cpu type, board id, etc in /sys that is populated
> from the DT.  I haven't seen that discussed here yet, has anyone
> considered it?

Seems like a specious argument to me.  Despite all the problems of
/proc, the contents of /proc/device-tree are perfectly well-defined.
Or at least, its problems are entirely its own and not related to the
general problems of /proc.  The only argument here seems to be that
it's in /proc, and that's dealt with if that helper script just thinks
of /proc/device-tree as one possible place for the device tree path.
In the future it could be under /sys.  Indeed on sparc I think their
device tree representation is a separate filesystem and could be
anywhere.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  parent reply	other threads:[~2011-08-19  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 19:15 board identification in /sys Andres Salomon
     [not found] ` <20110818121530.08946a6e-pFFUokh25LWsTnJN9+BGXg@public.gmane.org>
2011-08-19  2:23   ` David Gibson [this message]
     [not found]     ` <20110819022306.GD30097-787xzQ0H9iQXU02nzanrWNbf9cGiqdzd@public.gmane.org>
2011-08-19  3:14       ` Andres Salomon

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=20110819022306.GD30097@yookeroo.fritz.box \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=dilinger-pFFUokh25LWsTnJN9+BGXg@public.gmane.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).