From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Documented feature list anyone?
Date: 22 Sep 2003 18:07:07 +0200 [thread overview]
Message-ID: <87isnkst78.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <3F6E41AD.1030106@tait.co.nz>
Hello Robin,
> Does anyone have a u-boot 'feature list' I could cut 'n paste into a
> document that justifies the use of u-boot in a project?
>
> I started picking a few things from the README file and from the top of
> my head but it all sounds very dry and unexciting :-))
>
> I'm sure that someone has composed some prose that is elequent and
> technically correct without being bloated by too much 'boiler plating' !!
No sorry, I don't have such a document ready. I just wanted to remind
you that if you have such a document available, be sure it finds its
way into our documentation system[1] - either by yourself or mail a
copy to the list.
Thanks!
Detlev
[1] http://www.denx.de/twiki/bin/view/DULG/Manual
--
The continental people think life is a game. The English think
cricket is a game.
-- George Mikes
prev parent reply other threads:[~2003-09-22 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 0:26 [U-Boot-Users] Documented feature list anyone? Robin Gilks
2003-09-22 16:07 ` Detlev Zundel [this message]
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=87isnkst78.fsf@deepthought.outer.space.org \
--to=dzu@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