From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] mx28evk: extend default environment
Date: Tue, 29 May 2012 23:30:08 +0200 [thread overview]
Message-ID: <20120529213008.8EE242073AD@gemini.denx.de> (raw)
In-Reply-To: <201205292314.04143.marex@denx.de>
Dear Marek,
In message <201205292314.04143.marex@denx.de> you wrote:
>
> > Not because I consider it inherently bad, but for example because it
> > is different from what we, our customers, our documentation and our
> > test scripts are used to.
>
> Then I guess some kind of "common env" for all boards won't happen ?
I don't see a real chance. Pick any of the bigger vendors - say
Freescale: do you consider it a realistic chance that all their
boards (PPC, ARM, ColdFire, what else) get converted to a common
environment? Do you expect that TI and Samsung and Marvell and ...
agree with this approach and apply it on thier boards as ell? Or vice
versa?
I think the best we can do is factor out some parts we consider well
designed, and use these in the boards in our own responsibility. Then
we can start pointing people at that and try to convince them to
accept this for new stuff added.
But reorganizing existing environents is basicly impossible - all the
bigger vendors will tell you how much effort it would take to update
just all the documentation, not to mention to update all the boards
and scrpts and handle the resulting board breakages / brickages.
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
"What the scientists have in their briefcases is terrifying."
- Nikita Khrushchev
next prev parent reply other threads:[~2012-05-29 21:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 20:59 [U-Boot] [PATCH 1/3] m28evk: use same notation to alloc the 128kB stack Otavio Salvador
2012-05-15 20:59 ` [U-Boot] [PATCH 2/3] m28evk: drop duplicated definition of CONFIG_OF_LIBFDT Otavio Salvador
2012-05-15 21:14 ` Marek Vasut
2012-05-15 21:34 ` Otavio Salvador
2012-05-15 22:05 ` Marek Vasut
2012-05-15 23:03 ` Otavio Salvador
2012-05-15 23:18 ` Marek Vasut
2012-05-15 23:55 ` Otavio Salvador
2012-05-16 1:00 ` Marek Vasut
2012-06-13 9:06 ` Stefano Babic
2012-05-15 20:59 ` [U-Boot] [PATCH 3/3] mx28evk: extend default environment Otavio Salvador
2012-05-15 21:08 ` Fabio Estevam
2012-05-15 21:18 ` Otavio Salvador
2012-05-15 21:31 ` Otavio Salvador
2012-05-29 20:57 ` Wolfgang Denk
2012-05-29 21:02 ` Otavio Salvador
2012-05-15 21:16 ` Marek Vasut
[not found] ` <CAP9ODKrZ5kObb8C=BWRLh0MJWsQz1H2WRe9sJHh1Tq0DcRR2Ag@mail.gmail.com>
2012-05-15 21:21 ` Marek Vasut
2012-05-15 21:27 ` Otavio Salvador
2012-05-29 20:55 ` Wolfgang Denk
2012-05-29 21:14 ` Marek Vasut
2012-05-29 21:30 ` Wolfgang Denk [this message]
2012-05-29 20:52 ` Wolfgang Denk
2012-05-15 21:14 ` [U-Boot] [PATCH 1/3] m28evk: use same notation to alloc the 128kB stack Marek Vasut
2012-05-15 21:32 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2012-06-17 12:58 [U-Boot] [PATCH 0/3] i.MX refactoring patchset Otavio Salvador
2012-06-17 12:58 ` [U-Boot] [PATCH 3/3] mx28evk: extend default environment Otavio Salvador
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=20120529213008.8EE242073AD@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