From: jimc at sdateam.com <jimc@sdateam.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot "public API" example desired
Date: Thu, 6 May 2010 10:59:47 -0500 [thread overview]
Message-ID: <8139.1273161587@sdateam.com> (raw)
Is there an example available of the use of the U-Boot "public API"
or of a "stand-alone application", that can be, or is, sanctioned by
someone who would definitely know (for example, Wolfgang Denk) as
being not a derived work?
I've seen several discussions in various mailing lists about these
interfaces but I have not seen a definite example that qualifies. It
is not clear that the examples in the U-Boot source trees completely
qualify. The most recent tree I've seen is 2010.03, which I got from
ftp://ftp.denx.de/pub/u-boot/u-boot-2010.03.tar.bz2.
Web searches I've done have revealed only theoretical discussion or
discussion of future needs and possible improvements. I've probably
missed it, can someone provide a pointer?
Thank you very much.
Jim
next reply other threads:[~2010-05-06 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 15:59 jimc at sdateam.com [this message]
2010-05-06 17:42 ` [U-Boot] U-Boot "public API" example desired Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2010-05-06 22:29 jimc at sdateam.com
2010-05-18 7:03 James E. Chargin Jr.
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=8139.1273161587@sdateam.com \
--to=jimc@sdateam.com \
--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