Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v5] sim: bfin: new port
Date: Wed, 02 Mar 2011 01:13:00 -0000	[thread overview]
Message-ID: <201103020113.34913.pedro@codesourcery.com> (raw)
In-Reply-To: <201103011702.22120.vapier@gentoo.org>

On Tuesday 01 March 2011 22:02:21, Mike Frysinger wrote:
> On Tuesday, March 01, 2011 16:19:25 Pedro Alves wrote:
> > On Tuesday 22 February 2011 20:26:44, Mike Frysinger wrote:
> > > --- /dev/null
> > > +++ b/sim/bfin/linux-fixed-code.h
> > > @@ -0,0 +1,23 @@
> > > +/* DO NOT EDIT: Autogenerated.  */
> > > +/* Fixed code region of Linux userspace starting at 0x400.  Last
> > > produced +   from Linux-2.6.37 (not that the fixed code region changes
> > > often).  */ +static const unsigned char bfin_linux_fixed_code[] = {
> > > +0x28, 0xe1, 0xad, 0x00, 0xa0, 0x00, 0x00, 0x20,
> > 
> > (...)
> > 
> > > +0xa4, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> > > +};
> > 
> > Now this kernel code in question was probably (haven't
> > checked) largely written by ADI, and as such ADI could
> > probably contribute a standalone version of its source
> > to the FSF under GPLv3, along with some script or makefile
> > that compiles it with a bfin-gcc and then generates
> > the blob array.  Or you could write simple dumb
> > replacement implementations of the interface instead?
> 
> this code was written purely by ADI employees (2 or 3 of them to be exact), is 
> written in pure Blackfin assembly, and we've explicitly licensed this file 
> under GPLv2 or later.  so i dont think this is an issue.  it is not used by 
> the kernel at all ... the code is placed in a fixed location for userspace 
> binaries to call and is defined as part of the Blackfin ABI.  see below.
> -mike
> 

Thanks.  Since the Linux kernel is a mixture of code under GPLv2
and `GPLv2 or later', the resulting compiled binary is GPLv2
only (not later), so it's still an issue to dump from
the kernel binary.  And I think only the interface is
defined as part of the ABI, not the implementation?

To comply with the GPL, we need to provide the source of
that blob.  I guess it's easy to do what I suggested
above then?  Then the GPLv2-only of the Linux kernel
won't apply, and we're all happy.

-- 
Pedro Alves


  reply	other threads:[~2011-03-02  1:13 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16  1:41 [PATCH] " Mike Frysinger
2010-12-31 23:12 ` [PATCH v2] " Mike Frysinger
2011-02-14 20:18   ` [PATCH v3] " Mike Frysinger
2011-02-14 20:49     ` Pedro Alves
2011-02-14 21:12       ` Mike Frysinger
2011-02-14 21:55         ` Pedro Alves
2011-02-14 22:11           ` Mike Frysinger
2011-02-14 22:23             ` Mike Frysinger
2011-02-15 16:25             ` Pedro Alves
2011-02-16  1:34               ` Mike Frysinger
2011-02-16  5:34                 ` Joel Brobecker
2011-02-20  7:24     ` Mike Frysinger
2011-02-21 10:13       ` Joel Brobecker
2011-02-21 18:27         ` Mike Frysinger
2011-02-22  8:28           ` Joel Brobecker
2011-02-22 17:58             ` Mike Frysinger
2011-02-22 10:50           ` Pedro Alves
2011-02-22 18:07             ` Mike Frysinger
2011-02-22 10:08         ` Pedro Alves
2011-02-22 17:57           ` Mike Frysinger
2011-02-22 18:25             ` Pedro Alves
2011-02-22 20:54               ` Mike Frysinger
2011-02-22 20:29       ` [PATCH v5] " Mike Frysinger
2011-03-01  5:16         ` Mike Frysinger
2011-03-01 10:11         ` Joel Brobecker
2011-03-01 21:19         ` Pedro Alves
2011-03-01 23:42           ` Mike Frysinger
2011-03-02  1:13             ` Pedro Alves [this message]
2011-03-02  2:23               ` Mike Frysinger
2011-03-02  9:30                 ` Pedro Alves
2011-03-02 21:46                   ` Mike Frysinger
2011-03-02 23:32                     ` Pedro Alves
2011-03-02 23:32                     ` Pedro Alves
2011-03-03 21:40         ` [PATCH v6] " Mike Frysinger
2011-03-04 10:19           ` Pedro Alves
2011-03-04 21:12             ` Mike Frysinger

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=201103020113.34913.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /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