public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] MAC address question...
Date: Thu, 26 Aug 2004 21:22:24 +0200	[thread overview]
Message-ID: <20040826192230.05DEDC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 26 Aug 2004 19:10:27 +0200." <20040826171027.GA2759@umax645sx>

In message <20040826171027.GA2759@umax645sx> you wrote:
>
> > No. For U-Boot the reference is always the  value  of  the  "ethaddr"
> > envrionment variable.
> 
> Ah, I probably didn't explain it too well :( "ethaddr" envrionment
> variable still exist, but it's not stored together with other variables,
> but in smc's eeprom itself (so it's not stored in two different places)

This is not acceptable.  The  environment  is  defined  as  a  single
contiguous  area  in memory (RAM while U-Boot is running). I will not
accept exceptions from that rule.

> That feature is configurable (eeprom is optional and smc can be told not
> to use it). Are you interested in patch?

No, see above.

Again: there is no need for such a behaviour. If there is a valid MAC
address somewhere else, you can simply  omit  the  "ethaddr"  in  the
initialization  of  the  environment,  and  you  may even add code to
automatically bootstrap the definition from  this  external  storage.
But that's all.

> My point is exactly the same. After board is manufactured, it is put
> into automatic tester which writes mac address (basicaly it is computer
> hooked to serial line and some other signals for diagnostic) by issuing
> setenv ethaddr command. This command stores mac address directly into
> eeprom, not into the same space as other variables are stored (NOR
> flash)

No. Make your teste write it directly to the EEPROM if you like  (but
not  though  the "setenv" command, as this will always write to _one_
device only).

> Once set, overwriting mac address is allowed, but it is password protected.
> That way unexperienced user is not able to change it, but service
> technician is.

Such password protection  is  overkill.  Shall  I  show  you  how  an
unexperienced user is able to overwrite the whole environment even if
you  password protect it? You just need to read the documentation and
add 2 and 2 together.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
In any group of employed individuals the only naturally  early  riser
is  _always_  the office manager, who will _always_ leave reproachful
little notes ... on the desks of their subordinates.
                                - Terry Pratchett, _Lords and Ladies_

  reply	other threads:[~2004-08-26 19:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26  8:30 [U-Boot-Users] MAC address question Getz, Robin
2004-08-26  9:17 ` Ladislav Michl
2004-08-26 15:05   ` Wolfgang Denk
2004-08-26 16:02     ` Ladislav Michl
2004-08-26  9:47 ` R: " Paolo Broggini
2004-08-26 15:06   ` Wolfgang Denk
2004-08-26 15:03 ` Wolfgang Denk
2004-08-26 16:13   ` Ladislav Michl
2004-08-26 16:44     ` Wolfgang Denk
2004-08-26 17:10       ` Ladislav Michl
2004-08-26 19:22         ` Wolfgang Denk [this message]
2004-08-26 20:54           ` Ladislav Michl
2004-08-26 21:58             ` Wolfgang Denk
2004-08-26 22:40               ` Ladislav Michl
  -- strict thread matches above, loose matches on Subject: below --
2004-08-26 17:25 Robin Getz
2004-08-26 19:17 ` Ladislav Michl
2004-08-26 19:38 ` Wolfgang Denk
2004-08-26 20:26 Robin Getz
2004-08-26 21:42 ` Wolfgang Denk

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=20040826192230.05DEDC109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=u-boot@lists.denx.de \
    /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