From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] API Licence
Date: Mon, 18 May 2009 18:07:20 -0400 [thread overview]
Message-ID: <200905181807.22971.vapier@gentoo.org> (raw)
In-Reply-To: <20090518212049.GJ17539@game.jcrosoft.org>
On Monday 18 May 2009 17:20:49 Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 17:16 Mon 18 May , Mike Frysinger wrote:
> > On Monday 18 May 2009 16:31:39 Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > I'd like to known if it's possible to update the COPYING
> > >
> > > NOTE! This copyright does *not* cover the so-called "standalone"
> > > applications that use U-Boot services by means of the jump table
> > > provided by U-Boot exactly for this purpose - this is merely
> > > considered normal use of U-Boot, and does *not* fall under the
> > > heading of "derived work".
> > >
> > > to also include the API as a non derived work as the standalone?
> >
> > that sounds like a bad idea. then people could add all the API hooks
> > they wanted rather than just the ones we deemed they could use.
> > basically you're opening up all of u-boot for direct access.
>
> The idea is not to open every think but allow as in the kernel allow just a
> part of it
which is a loop hole that i dont think we should follow
> > what exactly are you trying to accomplish ?
>
> I've to write an application that need to use the mmc and net but can not
> be under GPL
so ask for the API to be extended. we dont have any functions for working
with file systems and i think that's reasonable.
-mike
next prev parent reply other threads:[~2009-05-18 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 20:31 [U-Boot] [RFC] API Licence Jean-Christophe PLAGNIOL-VILLARD
2009-05-18 21:16 ` Mike Frysinger
2009-05-18 21:20 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-18 22:07 ` Mike Frysinger [this message]
2009-05-18 22:13 ` Wolfgang Denk
2009-05-19 9:00 ` Rafal Jaworowski
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=200905181807.22971.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