From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Initial environment variables
Date: Thu, 16 Jul 2009 14:26:07 -0700 [thread overview]
Message-ID: <4A5F9AEF.9000507@gmail.com> (raw)
In-Reply-To: <618394.56077.qm@web83508.mail.sp1.yahoo.com>
ron_madrid at sbcglobal.net wrote:
> --- On Thu, 7/16/09, Ben Warren <biggerbadderben@gmail.com> wrote:
>
>
>> From: Ben Warren <biggerbadderben@gmail.com>
>> Subject: Re: [U-Boot] Initial environment variables
>> To: "Ron Madrid" <ron_madrid@sbcglobal.net>
>> Cc: u-boot at lists.denx.de, "Mike Frysinger" <vapier@gentoo.org>
>> Date: Thursday, July 16, 2009, 2:08 PM
>> Ron Madrid wrote:
>>
>>> --- On Thu, 7/16/09, Mike Frysinger <vapier@gentoo.org>
>>>
>> wrote:
>>
>>>
>>>
>>>> the board maintainer decides the default env
>>>>
>> values, not
>>
>>>> board users. Ben's comment was probably on
>>>>
>> the assumption that you are in the
>>
>>>> latter category.
>>>>
>>>>
>>> Ah, that could be why. Thankfully I am the
>>>
>> maintainer for the board. So I
>>
>>> am going to assume then that it would be OK for me to
>>>
>> add these variable
>>
>>> settings to my board's include/configs file and submit
>>>
>> a patch for it,
>>
>>> unless I here other objections.
>>>
>>> Ron
>>>
>>>
>> No, there should be no default net parameters, because
>> you're making likely-bogus assumptions about the network
>> that your board's going to go into. Just because your
>> LAN uses '192.168.0.x' doesn't mean anybody else's
>> does. It's even worse for MAC addresses - what if I
>> buy two of your boards and plug them into the same
>> switch? If the addresses are identical all sorts of
>> bad things can happen. Not to mention that public MAC
>> addresses are assigned (and paid for) and should be
>> guaranteed to be unique. And private (bit 41 set)
>> addresses are used in many different ways. One systems
>> company that I worked at would program these dynamically
>> based on which shelf/slot the board was plugged into.
>> It's best to fail loudly (a printf stating that MAC
>> addresses haven't been programmed) than to silently cause
>> network issues. I could go on and on, but hopefully
>> you get the point.
>>
>
> I do understand your points. I am confused then as to why there are
> around 100 different board configurations that include these variables.
>
> Ron
>
>
Sorry, before my time :) They should be cleaned up.
regards,
Ben
next prev parent reply other threads:[~2009-07-16 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 21:23 [U-Boot] Initial environment variables ron_madrid at sbcglobal.net
2009-07-16 21:26 ` Ben Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-16 21:00 Ron Madrid
2009-07-16 21:08 ` Ben Warren
2009-07-16 21:31 ` Mike Frysinger
2009-07-16 22:23 ` Wolfgang Denk
2009-07-16 20:46 Ron Madrid
2009-07-16 20:56 ` Mike Frysinger
2009-07-16 22:21 ` Wolfgang Denk
2009-07-16 22:57 ` Mike Frysinger
2009-07-16 18:57 Ron Madrid
2009-07-16 19:14 ` Mike Frysinger
2009-07-16 19:54 ` Ben Warren
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=4A5F9AEF.9000507@gmail.com \
--to=biggerbadderben@gmail.com \
--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