From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Ethernet port
Date: Wed, 19 Sep 2007 00:11:48 +0200 [thread overview]
Message-ID: <20070918221148.591AD247FE@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 18 Sep 2007 22:57:43 +0200." <1190149063.4516.9.camel@aeglos.sweden.atmel.com>
In message <1190149063.4516.9.camel@aeglos.sweden.atmel.com> you wrote:
>
> > It is a terrible bad idea to set the IP address and especially the MAC
> > address of your board in the config file, as then all your boards will
> > share the same address, which will cause only trouble.
> >
> > DO NOT DO THIS!!!
>
> Unless you use this functionality to simplify factory programming of the
> device.
It's still a very stupid thing to do, as you buy your own convenience
at the cost of your customers - it's they who will have the problems,
not you, obviously. And it's trivial to set up a production
envrionment where each and every board has it's own specific serial
number, MAC address atf. in the U-Boot environment.
Don't tell me it could not be done, or would be too complicated. It's
all there, just use it.
> By having a compile time setup of ethaddr/ipaddr/serverip, you can
> easily connect to a production PC using a twisted cable.
It is NOT necessary to do this at compile time.
> If this "feature" is used, it must be possible to reconfigure
> the ethaddr/ipaddr combination to something unique.
> You do not want to ship this to end customers.
Then you have to make ethaddr and serial# unprotected, which IMHO is
a bad idea either. I don't want to have users messing around with the
serial number. If you intend for such a setup, you should at least
use the CONFIG_OVERWRITE_ETHADDR_ONCE feature.
> An autoscript at the production PC can do this as part of the production
> programming.
There are much easier ways which don't require console access or
booting the system. See "board/tqm8xx/load_sernum_ethaddr.c" for one
example wher ethis information can be written by the same programming
sequence that programs the U-Boot image - it just programs some small
data block in a second step.
> it is probably advisable to disallow booting the linux kernel if
> the ethaddr/ipaddr has not changed.
Too complicated, and not necessary.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A committee is a group that keeps the minutes and loses hours.
-- Milton Berle
next prev parent reply other threads:[~2007-09-18 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 11:41 [U-Boot-Users] Ethernet port Yasothabalan
2007-09-18 21:19 ` urwithsughosh at gmail.com
2007-09-18 12:19 ` Yasothabalan
2007-09-18 22:48 ` urwithsughosh at gmail.com
2007-09-18 13:55 ` Yasothabalan
[not found] ` <CE54F2377C0FB8439A290BF5A88BF13D066727E0@CHN-HCLT-EVS01.HCLT.CORP.HCL .IN>
2007-09-18 14:17 ` Ramasamy C
2007-09-18 19:13 ` Wolfgang Denk
2007-09-18 19:09 ` Wolfgang Denk
2007-09-18 20:57 ` Ulf Samuelsson
2007-09-18 22:11 ` Wolfgang Denk [this message]
2007-09-18 22:52 ` Ulf Samuelsson
2007-09-19 7:07 ` [U-Boot-Users] Ethernet ports Yasothabalan
2007-09-19 13:45 ` Detlev Zundel
2007-09-19 18:07 ` Wolfgang Denk
2007-09-21 0:02 ` [U-Boot-Users] At91rm9200 buildroot Leonid
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=20070918221148.591AD247FE@gemini.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