All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mitch Bradley <wmb-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
To: Renaud Barbier <renaud.barbier-JJi787mZWgc@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: Re: specifying MAC address location in device tree
Date: Mon, 09 Feb 2009 08:44:37 -1000	[thread overview]
Message-ID: <49907995.3050508@firmworks.com> (raw)
In-Reply-To: <499042EC.6050103-JJi787mZWgc@public.gmane.org>

> Assuming that a MAC address ( or list of MAC addresses or any board 
> data)  is located in an I2C (or flash),
> how would you specify the data location in the device tree?
>
> For an I2C, should I specify the specific device containing the data 
> under the I2C node?
>

The standard way to communicate MAC address information to the OS is via 
properties in the node for the network interface.  "local-mac-address" 
is the MAC address that was factory-assigned to the interface and 
"mac-address" is the actual address that is being used for the device 
(in case the factory-assigned address was overridden by some policy 
choice).  The value is the mac address itself (6 bytes), not the 
"address" of the mac address.

The reason I put "address" in quotes is because the devices that are 
used to store MAC addresses are often not "addressable" in any 
convenient sense.  You often have to run some device-specific driver 
code to extract the information.  It's the firmware's responsibility to 
do that, extracting the information and creating the properties 
described above.

Strictly speaking, a MAC address is an attribute of a network interface; 
the association of a MAC address with a mainboard is meaningless, or at 
least there is no standard that I know of that assigns a specific 
interpretation.  That said, it's fairly common to store a MAC address on 
a mainboard EEPROM as a surrogate for a nonexistent EEPROM that is 
supposed to be attached to the network interface hardware.  In that 
case, the mainboard firmware is supposed to know that and do whatever is 
necessary to move the data into the device node for the corresponding.

      parent reply	other threads:[~2009-02-09 18:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 14:51 specifying MAC address location in device tree Renaud Barbier
     [not found] ` <499042EC.6050103-JJi787mZWgc@public.gmane.org>
2009-02-09 18:44   ` Mitch Bradley [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=49907995.3050508@firmworks.com \
    --to=wmb-d5eqfidgl7eakbo8gow8eq@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=renaud.barbier-JJi787mZWgc@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.