From: Wolfgang Denk <wd@denx.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Pantelis Antoniou <panto@intracom.gr>,
Meriin Michael-BMM063 <Meriin@motorola.com>,
"'Ricardo DIz'" <rdiz@alumni.deec.uc.pt>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: U-Boot and kernel 2.6
Date: Fri, 11 Jun 2004 17:11:16 +0200 [thread overview]
Message-ID: <20040611151121.62F07C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 11 Jun 2004 15:34:13 BST." <1086964452.15845.1308.camel@hades.cambridge.redhat.com>
In message <1086964452.15845.1308.camel@hades.cambridge.redhat.com> you wrote:
> On Fri, 2004-06-11 at 17:16 +0300, Pantelis Antoniou wrote:
> > Yeah, having the bi_recs interface actually working
> > would be ideal, but at the present time nothing is
> > working and as AFAIK no-one is working on it.
>
> So we should offer some gentle encouragement. Like refusing to accept
> any further modifications to include/asm-ppc/ppcboot.h.
Then you must also refuse to accept any further modifications that
define "struct bd_info" for any boards. Or please explain why you
think that one definiton of bd_info which gets used by many boards is
worse then several private definitions of the same structure used by
one board only in each case?
Let's see:
linuxppc-2.4 linuxppc-2.5
----------------------------------------------------
-> cd arch/ppc/platforms -> cd arch/ppc/platforms
-> grep bd_info * | wc -l -> grep bd_info * | wc -l
6 8
-> grep ppcboot.h * | wc -l -> grep ppcboot.h * | wc -l
9 12
Before phasing out a working solution, even if it's a poor design,
you should provide a new, better solution.
I promise: I will make sure that U-Boot supports the new interface as
soon as there is any definitive agreement about what it's going to
look like. As mentioned before - I'd be happy to accept what has been
discussed more than two years ago, especially Mark's proposal.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Experience is what causes a person to make new mistakes instead of
old ones.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-11 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 6:45 U-Boot and kernel 2.6 Meriin Michael-BMM063
2004-06-11 10:36 ` David Woodhouse
2004-06-11 11:03 ` Pantelis Antoniou
2004-06-11 11:20 ` David Woodhouse
2004-06-11 13:03 ` Wolfgang Denk
2004-06-11 13:23 ` Pantelis Antoniou
2004-06-11 14:09 ` Wolfgang Denk
[not found] ` <40C9BED6.3010809@intracom.gr>
2004-06-11 14:34 ` David Woodhouse
2004-06-11 15:11 ` Wolfgang Denk [this message]
2004-06-11 17:17 ` Greg Goodwin
2004-06-11 15:31 ` Mark Chambers
2004-06-11 16:22 ` Wolfgang Denk
2004-06-11 16:48 ` Kenneth Johansson
2004-06-11 14:43 ` Wolfgang Denk
2004-06-11 21:35 ` Mark A. Greer
2004-06-11 23:18 ` Mark Chambers
2004-06-11 23:27 ` Mark A. Greer
2004-06-12 2:12 ` Kumar Gala
2004-06-11 16:48 ` Tom Rini
[not found] ` <0F48024310E5D6118D200002B3A440DB08B07A3D@zil01exm08.mcil.comm.mot.com >
2004-06-11 19:27 ` Ricardo DIz
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 17:47 Ricardo DIz
2006-08-01 5:12 ` Dmitry Chichkov
2006-08-01 7:10 ` Wolfgang Denk
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=20040611151121.62F07C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=Meriin@motorola.com \
--cc=dwmw2@infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=panto@intracom.gr \
--cc=rdiz@alumni.deec.uc.pt \
/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;
as well as URLs for NNTP newsgroup(s).