public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot] Initial environment variables
@ 2009-07-16 21:23 ron_madrid at sbcglobal.net
  2009-07-16 21:26 ` Ben Warren
  0 siblings, 1 reply; 13+ messages in thread
From: ron_madrid at sbcglobal.net @ 2009-07-16 21:23 UTC (permalink / raw)
  To: u-boot


--- 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

^ permalink raw reply	[flat|nested] 13+ messages in thread
* [U-Boot] Initial environment variables
@ 2009-07-16 21:00 Ron Madrid
  2009-07-16 21:08 ` Ben Warren
  2009-07-16 22:23 ` Wolfgang Denk
  0 siblings, 2 replies; 13+ messages in thread
From: Ron Madrid @ 2009-07-16 21:00 UTC (permalink / raw)
  To: u-boot


--- 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

^ permalink raw reply	[flat|nested] 13+ messages in thread
* [U-Boot] Initial environment variables
@ 2009-07-16 20:46 Ron Madrid
  2009-07-16 20:56 ` Mike Frysinger
  0 siblings, 1 reply; 13+ messages in thread
From: Ron Madrid @ 2009-07-16 20:46 UTC (permalink / raw)
  To: u-boot



> Ron Madrid wrote:
> > When I submitted patches for my new board SIMPC8313 I
> recall being told that
> > I had inappropriately initialized some of my
> environment variables.  Most
> > specifically I am interested in having default
> serverip, ipaddr, and ethaddr
> > environment variables.  Is this most
> appropriately done with a specific
> > #define (such as #define CONFIG_SERVERIP) or within
> #define
> > CONFIG_EXTRA_ENV_SETTINGS?
> >
> >   
> You can set CONFIGs for all of these things in your own
> private build 
> and they'll work, but they're inappropriate for main-line
> U-boot.  I 
> hope the reasoning is obvious.

I'm do not understand why and I see in several include/configs/*.h files that these environment variable are being set as default.  I'm guessing that there's something that I'm missing.

Ron

^ permalink raw reply	[flat|nested] 13+ messages in thread
* [U-Boot] Initial environment variables
@ 2009-07-16 18:57 Ron Madrid
  2009-07-16 19:14 ` Mike Frysinger
  2009-07-16 19:54 ` Ben Warren
  0 siblings, 2 replies; 13+ messages in thread
From: Ron Madrid @ 2009-07-16 18:57 UTC (permalink / raw)
  To: u-boot


When I submitted patches for my new board SIMPC8313 I recall being told that
I had inappropriately initialized some of my environment variables.  Most
specifically I am interested in having default serverip, ipaddr, and ethaddr
environment variables.  Is this most appropriately done with a specific
#define (such as #define CONFIG_SERVERIP) or within #define
CONFIG_EXTRA_ENV_SETTINGS?

Thanks for the help.

Ron

^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2009-07-16 22:57 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-16 21:23 [U-Boot] Initial environment variables ron_madrid at sbcglobal.net
2009-07-16 21:26 ` Ben Warren
  -- 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox