From: John Crispin <blogic-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: RFC of_boardconfig
Date: Tue, 29 Nov 2011 17:22:15 +0100 [thread overview]
Message-ID: <4ED506B7.5050001@openwrt.org> (raw)
In-Reply-To: <4ED4EF4D.4080806-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> How is label used?
>
this would be used as a name when exporting the data, however you are
right and the property name lanmac could be used here
>> data = <0x100 0x6>;
>> };
>>
>> wanmac {
>> label = "WAN";
>> data = <0x106 0x6>;
>> };
>>
>> ath9keeprom {
>> label = "eeprom";
>> partition = <0x200 0x200>;
>> magic = <0x0 0x55 0xaa 0xaa 0x55>;
>> no-export;
>> };
>> };
>>
>> you can are then able to reference these properties from other nodes:
>> ethernet {
>> compatible = "ethernet";
>> phy-mode = "mii";
>> //mac-address = [ 00 11 22 33 44 55 ];
> Why throw out the defined way to set a MAC addr and invent something
> new. If it's separating out some of the properties you want, you can
> have multiple "ethernet" nodes with some properties in each node and it
> all gets combined together at dtb compile time. I think the Tegra and
> other ARM dts files have examples of this.
>
> Rob
>
in my usecase there will be only 1 ethernet device. the mac is stored
inside the devices flash and will not be passed as a parameter by the
bootloader. We need to have some means to load things like mac addresses
from memory mapped flash devices. This is the reasoning behind this wrapper
prev parent reply other threads:[~2011-11-29 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 13:52 RFC of_boardconfig John Crispin
[not found] ` <4ECF9DA8.8000504-p3rKhJxN3npAfugRpC6u6w@public.gmane.org>
2011-11-29 14:42 ` Rob Herring
[not found] ` <4ED4EF4D.4080806-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-29 16:22 ` John Crispin [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=4ED506B7.5050001@openwrt.org \
--to=blogic-p3rkhjxn3npafugrpc6u6w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@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 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.