From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] exports.h and the GPL
Date: Fri, 24 Feb 2012 17:37:46 -0500 [thread overview]
Message-ID: <201202241737.47769.vapier@gentoo.org> (raw)
In-Reply-To: <201202242048.51624.michael@walle.cc>
On Friday 24 February 2012 14:48:51 Michael Walle wrote:
> Am Freitag 24 Februar 2012, 20:17:19 schrieb Mike Frysinger:
> > On Friday 24 February 2012 13:10:36 Michael Walle wrote:
> > > Who is responsible to define which functions are exported? Are the
> > > currently exported functions the only ones available to closed source
> > > applications or is it possible to add further ones which are needed.
> >
> > someone posts a request and the maintainers evaluate it. typically the
> > exported funcs should be "high level" and not hooks into u-boot
> > internals.
>
> Then i guess there is no way to support a board which has only evil closed
> source drivers for its networking card. That is, i can't export
> eth_register() to register my ops defined in the blob without violating
> the GPL.
that certainly goes against the spirit of the export logic (imo) so i'd be
against it. the export layer isn't there to support closed sourced drivers
the rest of u-boot would utilize.
you could ask Wolfgang, but i suspect he will say no.
-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/20120224/40ada51b/attachment.pgp>
next prev parent reply other threads:[~2012-02-24 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 18:10 [U-Boot] exports.h and the GPL Michael Walle
2012-02-24 19:17 ` Mike Frysinger
2012-02-24 19:48 ` Michael Walle
2012-02-24 22:37 ` Mike Frysinger [this message]
2012-02-24 23:37 ` Wolfgang Denk
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=201202241737.47769.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