From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ARM and u-boot
Date: Mon, 3 Jun 2013 14:43:17 -0400 [thread overview]
Message-ID: <2b4a6ce59f768eb51d6df3d9024427a6@ladd.quanstro.net> (raw)
In-Reply-To: <CAGGHmKHh=ZAKZh9yXLwcw0BRHZO6rUrdRqq3z8NubmAy180LfA@mail.gmail.com>
> It's more than that. Many board vendors will use a secured stage 1
> bootloader that assumes U-Boot. It's probably possible to shove in a
good point. what are the secure loaders assuming?
> Every SoC is going to have a different process - in the end, you'll have
> something that will probably look quite a bit like U-Boot without any real
> benefit. I'd rather tilt at other windmills...
that was my opinion, and i argued it pretty loudly—
until u-boot didn't cover my needs and i had to fix
u-boot. i had to eat my words.
u-boot is really terrible to work with. there is no
danger of writing something that looks like u-boot. :-)
but if u-boot works out of the box, i would totally agree,
why not use it? but don't fall for the trap of modifying
it. that's a terrible waste. instead of learning about the
internals of u-boot, you could spend time learning how
the hardware in hand is really set up.
- erik
next prev parent reply other threads:[~2013-06-03 18:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 7:19 tlaronde
2013-06-01 8:04 ` lucio
2013-06-01 9:30 ` tlaronde
2013-06-01 13:31 ` erik quanstrom
2013-06-01 15:02 ` tlaronde
2013-06-01 19:29 ` tlaronde
2013-06-01 22:10 ` erik quanstrom
2013-06-02 6:14 ` tlaronde
2013-06-02 4:06 ` Steven Stallion
2013-06-02 6:02 ` tlaronde
2013-06-02 13:09 ` erik quanstrom
2013-06-02 15:50 ` Richard Miller
2013-06-03 3:53 ` erik quanstrom
2013-06-03 4:29 ` Skip Tavakkolian
2013-06-03 10:35 ` Richard Miller
2013-06-03 12:34 ` Skip Tavakkolian
2013-06-03 16:58 ` Bakul Shah
2013-06-03 18:21 ` Richard Miller
2013-06-03 18:35 ` Bakul Shah
2013-06-03 18:40 ` Richard Miller
2013-06-03 10:41 ` Richard Miller
2013-06-03 13:19 ` erik quanstrom
2013-06-03 18:21 ` Steven Stallion
2013-06-03 18:43 ` erik quanstrom [this message]
2013-06-03 20:02 ` Steven Stallion
2013-06-03 20:13 ` erik quanstrom
2013-06-03 20:19 ` erik quanstrom
2013-06-03 5:40 ` Steven Stallion
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=2b4a6ce59f768eb51d6df3d9024427a6@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).