From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl
Date: Tue, 27 Mar 2012 23:13:38 +0200 [thread overview]
Message-ID: <20120327211338.4806B2002FF@gemini.denx.de> (raw)
In-Reply-To: <201203272255.59259.michael@walle.cc>
Dear Michael,
In message <201203272255.59259.michael@walle.cc> you wrote:
>
> Wolfgang, what do you think about relaxing this policy a bit and allowing this
> class of devices (no service port/serial port available, no storage for the
> MAC address besides the environment) to use hardcoded values (maybe defined in
> a place common to all boards). Again, i don't think my device is the only one
> with this problem.
Probably it is not the only device, but eventually all the others
found other working solutions?
I still fail to understand why you would need fixed network settings.
Evenin emergency cases, the only parameter you really need is a MAC
address, all others can be fetched for example from a DHCP server.
As for the MAC address, it is in such emergencies OK to use a random
locally administered Ethernet address. Note the "random" - hard-
coding the same address for all devices is definitely a No-Go.
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
Disc space - the final frontier!
next prev parent reply other threads:[~2012-03-27 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 10:51 [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl Michael Walle
2012-03-27 11:05 ` Prafulla Wadaskar
2012-03-27 20:55 ` Michael Walle
2012-03-27 21:13 ` Wolfgang Denk [this message]
2012-03-29 11:30 ` Michael Walle
-- strict thread matches above, loose matches on Subject: below --
2012-03-02 15:02 Michael Walle
2012-03-26 10:15 ` Michael Walle
2012-03-27 7:27 ` Prafulla Wadaskar
2012-03-27 20:38 ` Michael Walle
2012-03-29 12:38 ` Michael Walle
2012-03-29 14:24 ` Prafulla Wadaskar
2012-03-29 14:39 ` Michael Walle
2012-03-30 11:18 ` Prafulla Wadaskar
2012-03-30 13:57 ` Michael Walle
2012-04-02 6:37 ` Prafulla Wadaskar
2012-03-27 7:28 ` Prafulla Wadaskar
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=20120327211338.4806B2002FF@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