From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] ARM and u-boot
Date: Mon, 3 Jun 2013 16:13:05 -0400 [thread overview]
Message-ID: <49c0921258dd6aa25b0d395e45e247fa@ladd.quanstro.net> (raw)
In-Reply-To: <CAGGHmKF9Wd0aF40PczxPjQWjDGSssuwq61gF2VMnYL-DvJ1duA@mail.gmail.com>
> Really? I've had very little problem with modifying U-Boot - the code base
> is fairly common for most Linux-like projects. The code was consistent, and
> well documented. As far as setting up the hardware, it's certainly
> interesting, but of small utility in the grand scheme of things.
perhaps this is vendor (or even part) specific, and i am falsely generalizing.
the vendor code i was dealing with was massive, poorly written, undocumented,
and #ifdef hell. flashing uboot took special tools (and 15 minutes
connected to a windows laptop), so the normal trick of printing to
see what code gets run was not easy.
> I think it's important to remember that U-Boot (and many other projects)
> all came into being out of necessity. As engineers (and hobbyists to some
> degree) we all tend to suffer from NIH. Decisions that some see as
> "mistakes" usually have a good reason for coming to being. Exitus acta
> probat, I suppose.
existance is not proof of necessity.
- erik
next prev parent reply other threads:[~2013-06-03 20:13 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
2013-06-03 20:02 ` Steven Stallion
2013-06-03 20:13 ` erik quanstrom [this message]
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=49c0921258dd6aa25b0d395e45e247fa@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).