From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Build breakage due to "Standalone Apps: Standalone apps should only need exports.h"
Date: Wed, 7 Dec 2011 19:32:43 -0500 [thread overview]
Message-ID: <201112071932.44826.vapier@gentoo.org> (raw)
In-Reply-To: <CAMaS=DwfjxS3_x3mF4zHkQrjSobF-nrzFcDmH2bciYH44xCg9g@mail.gmail.com>
On Wednesday 07 December 2011 14:56:30 Mike Partington wrote:
> As I understand it, one of the main purposes of standalone applications is
> to enable proprietary code to be run with U-Boot. In order to realize this
> objective, however, the code cannot be forced to include anything that is
> GPL-encumbered. Note that spi.h does not meet this criteria. So, either
> spi.h needs to be changed, or the spi interfaces need to be added to
> exports.h in a way that does not require any additional typedefs or
> structures from other files. I'm not sure which path is best, but my
> preference would be to keep the interface between standalone applications
> and U-Boot as clean and well-defined as possible. To me this means as few
> files as possible.
in general, i don't think your statement here is correct. the U-Boot license
explicitly provides an exception for using the exported API.
also, please don't top post
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20111207/47d726ea/attachment.pgp>
prev parent reply other threads:[~2011-12-08 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 19:31 [U-Boot] Build breakage due to "Standalone Apps: Standalone apps should only need exports.h" Moffett, Kyle D
2011-12-07 19:56 ` Mike Partington
2011-12-08 0:32 ` Mike Frysinger [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=201112071932.44826.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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