From: Dan Malek <dan@embeddededge.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Fix 8250 probe on ppc32
Date: Mon, 7 Nov 2005 12:25:12 -0500 [thread overview]
Message-ID: <da56f10d9e365f6194e129205a690c02@embeddededge.com> (raw)
In-Reply-To: <20051107163144.GF3839@smtp.west.cox.net>
On Nov 7, 2005, at 11:31 AM, Tom Rini wrote:
> ..... If everything going forward ships from the hw
> vendor with U-Boot,
You can't make that assumption. Very few production
systems ship with U-Boot, whether we like it or not.
For those of us that developed all of this "boot wrapper"
code and remember why it was done, all of those reasons
still exist. More people are using U-Boot, but it's mostly
during development. The other embedded software we
are trying to displace with Linux sometimes doesn't have
the rom space, and there is the "we didn't have it before"
mentality that is hard to change.
Don't cast this old boot code too far away, people still use it.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-11-07 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 10:04 [PATCH] Fix 8250 probe on ppc32 David Woodhouse
2005-11-07 16:09 ` Tom Rini
2005-11-07 16:20 ` David Woodhouse
2005-11-07 16:31 ` Tom Rini
2005-11-07 17:25 ` Dan Malek [this message]
2005-11-07 16:54 ` Christoph Hellwig
2005-11-07 17:02 ` David Woodhouse
2005-11-16 8:51 ` David Woodhouse
2005-11-16 9:12 ` Paul Mackerras
2005-11-16 10:25 ` David Woodhouse
2005-11-16 15:24 ` Kumar Gala
2005-11-18 1:12 ` Paul Mackerras
2005-11-18 3:26 ` Kumar Gala
2005-11-18 3:50 ` Benjamin Herrenschmidt
2005-11-18 8:23 ` Christoph Hellwig
2005-11-18 10:51 ` Benjamin Herrenschmidt
2005-11-18 14:46 ` Kumar Gala
2005-11-18 21:36 ` Benjamin Herrenschmidt
2005-11-18 21:39 ` David Woodhouse
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=da56f10d9e365f6194e129205a690c02@embeddededge.com \
--to=dan@embeddededge.com \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.org \
/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).