public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Design principles
Date: Sat, 27 Mar 2010 11:21:15 +0100	[thread overview]
Message-ID: <20100327102115.21903EAD184@gemini.denx.de> (raw)
In-Reply-To: <4BADB479.6050604@denx.de>

Dear Heiko,

in message <4BADB479.6050604@denx.de> you wrote:
> 
> > My request was to apply the fix that Heiko submitted for fec_mxc.c to
> > all other drivers as well that have the sam problem (as far as we
> 
> I can make such an attempt, if It gets accepted here?

As far as I am concerned, I already said so.

> > know about these, of course). So if kirkwood_egiga is clean (in this
> > respect), there is no need to change it.
> 
> It ends in the same problem, as the fec_mxc.c driver has ...
> 
> If not running network commands in u-boot, the mac is not setup
> which results in the problem with booting an arm Linux Kernel.
> 
> If running network commands in u-boot, the mac is setup properly
> with the content from ethaddr ...

Right.

> So, what to do? Accept the arm solution with first booting
> an intrd and setup the mac with userspace tools, or waiting
> for "arm Linux with DTS", or fixing this in u-boot now(maybe with
> a comment that this is not in line with u-boot design goals,
> and should go away, if arm linux is fixed (fixed is maybe not
> the right word ... ))?

It makes obviously no sense to embedded systems to boot a ramdisk
just to set the MAC address so we can then boot for example with root
file system over NFS.  I feel that people suggesting this must be (at
least in this respekt) so narrow minded that they coold look through
a keyhole with both eyes.

It definitely is a good idea to support all activities to bring
device-tree support for ARM, as this will solve a number of other
issues as well.


In U-Boot, we cannot change the whole world. We can strive to get
clean interfaces to the Linux kernel, and object against adding new
code to U-Boot that violates the design principles.  On the other
hand, no review is perfect, and there are many places in the U-Boot
code that are far from perfect.  And if these imperfect pieces of code
contain obvious bugs (as is the case here), it makes perfect sense at
least to fix these bugs as long it is not possible yet (for whatever
reasons) to replace the whole code with a Perfect Implementation (TM).

So please go on and (re-) submit your (extended) patch.

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
Be wiser than other people if you can, but do not tell them so.
                                       -- Philip Earl of Chesterfield

  reply	other threads:[~2010-03-27 10:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 11:56 [U-Boot] [PATCH] net, fec_mxc: use mac address stored in env before looking in eeprom Heiko Schocher
2010-03-24 12:35 ` Stefano Babic
2010-03-24 12:52   ` Detlev Zundel
2010-03-24 20:39     ` Mike Frysinger
2010-03-24 13:07   ` Heiko Schocher
2010-03-24 20:35 ` Mike Frysinger
2010-03-25  6:31   ` Heiko Schocher
2010-03-25  9:40     ` Wolfgang Denk
2010-03-25 13:16       ` Detlev Zundel
2010-03-25 14:02         ` Wolfgang Denk
2010-03-26  8:39           ` [U-Boot] Design principles (was: Re: [PATCH] net, fec_mxc: use mac address stored in env before looking in eeprom) Detlev Zundel
2010-03-26 10:40             ` Wolfgang Denk
2010-03-26 11:47               ` [U-Boot] Design principles Detlev Zundel
2010-03-26 12:38                 ` Wolfgang Denk
2010-03-26 13:02                   ` Detlev Zundel
2010-03-26 18:21                     ` Wolfgang Denk
2010-03-27  7:32                       ` Heiko Schocher
2010-03-27 10:21                         ` Wolfgang Denk [this message]
2010-03-25 17:49         ` [U-Boot] [PATCH] net, fec_mxc: use mac address stored in env before looking in eeprom Mike Frysinger
2010-03-25 17:38       ` Mike Frysinger
2010-03-25 19:11         ` Wolfgang Denk
2010-03-25 19:22           ` Mike Frysinger

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=20100327102115.21903EAD184@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