From: Grant Likely <grant.likely@secretlab.ca>
To: Theodore Ts'o <tytso@mit.edu>,
Rob Herring <robherring2@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tim Bird <tbird20d@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [GIT PULL] Device tree updates for v3.12
Date: Wed, 11 Sep 2013 22:49:03 +0100 [thread overview]
Message-ID: <CACxGe6tWN2d_MpncDXz8rb1u4bEWCip1isACC-hWGPX9wzYvZQ@mail.gmail.com> (raw)
In-Reply-To: <20130910221939.GC11063@thunk.org>
On Tue, Sep 10, 2013 at 11:19 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> On Tue, Sep 10, 2013 at 05:06:39PM -0500, Rob Herring wrote:
>> > If I recall correctly, somebody said that things like ethernet MAC
>> > addresses etc sometimes come from DT. Is my memory going, or is that
>> > true but very rare?
>>
>> It is true and fairly common. You can also have serial numbers in the
>> DT, but that is more rare. The bootloader will also add the kernel
>> command line, initrd start and end addresses.
>
> Stuff which is common across a large number of devices is rather less
> useful to merge in. Is there some fixed way that things like serial
> numbers and MAC addresses are tagged as such in the device tree?
Unfortunately not. There is no indication about which are the dynamic
properties.
g.
next prev parent reply other threads:[~2013-09-11 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 18:00 [GIT PULL] Device tree updates for v3.12 Grant Likely
2013-09-10 18:40 ` Tim Bird
2013-09-10 20:50 ` Linus Torvalds
2013-09-10 21:39 ` Tim Bird
2013-09-10 21:44 ` Linus Torvalds
2013-09-10 22:06 ` Rob Herring
2013-09-10 22:19 ` Theodore Ts'o
2013-09-11 21:49 ` Grant Likely [this message]
2013-09-11 17:02 ` Tony Luck
2013-09-11 20:21 ` Tim Bird
2013-09-11 20:52 ` Olof Johansson
2013-09-11 21:49 ` Grant Likely
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=CACxGe6tWN2d_MpncDXz8rb1u4bEWCip1isACC-hWGPX9wzYvZQ@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=anton@samba.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=tbird20d@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).