From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl
Date: Thu, 29 Mar 2012 13:30:40 +0200 [thread overview]
Message-ID: <201203291330.40131.michael@walle.cc> (raw)
In-Reply-To: <20120327211338.4806B2002FF@gemini.denx.de>
Hi Wolfgang,
> 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.
bootp/dhcp should work for getting the ip address. My initial thought was that
you need to hardcode the ncip anyway, which means you need the ipaddr etc,
too.
Using DHCP and setting the ncip to the delivered serverip should be ok, i
think.
> 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.
Is 02:00:00:RR:RR:RR, where RR is a random byte, ok?
--
Michael
next prev parent reply other threads:[~2012-03-29 11:30 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
2012-03-29 11:30 ` Michael Walle [this message]
-- 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=201203291330.40131.michael@walle.cc \
--to=michael@walle.cc \
--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