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] bf537-stamp board compilation problem
Date: Fri, 23 Apr 2010 21:44:22 +0200	[thread overview]
Message-ID: <20100423194422.0D1E419F60@gemini.denx.de> (raw)
In-Reply-To: <201004231533.58136.vapier@gentoo.org>

Dear Mike Frysinger,

In message <201004231533.58136.vapier@gentoo.org> you wrote:
>
> it.  i could just as easily say "i'd rather the code didnt assume powerpc 
> everywhere", but it isnt like that gets us from point a to point b.

I would have preferred an architecture neutral implementation as well,
but you know how it works: you start with just one specific processor
in mind, then another CPU of the same architecture gets added, and
when you try to add support for another architecture some rework and
cleanup is needed.  Same story here: first came MPC823E, then PPC440EX.
Both happened to be PPC...

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
"The more data I punch in this card,  the lighter it becomes, and the
lower the mailing cost."
                     - Stan Kelly-Bootle, "The Devil's DP Dictionary"

  reply	other threads:[~2010-04-23 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 14:10 [U-Boot] bf537-stamp board compilation problem Michael Zaidman
2010-04-23 14:56 ` Mike Frysinger
2010-04-23 15:21   ` Michael Zaidman
2010-04-23 15:37     ` Mike Frysinger
2010-04-23 16:31       ` Michael Zaidman
2010-04-23 16:45         ` Mike Frysinger
2010-04-23 19:30       ` Wolfgang Denk
2010-04-23 19:33         ` Mike Frysinger
2010-04-23 19:44           ` Wolfgang Denk [this message]
2010-04-24 17:53         ` Michael Zaidman

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=20100423194422.0D1E419F60@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