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

On Tuesday, February 15, 2011 10:56:55 Pedro Alves wrote:
> On Tuesday 15 February 2011 22:10:54, Mike Frysinger wrote:
> > > What kind of rom, and what kind of hardware?
> > 
> > it's the on-chip rom that exists on all Blackfin parts.  usually it's
> > used for bootstrapping a part, but it also has helper functions which
> > are sometimes used at runtime by the boot loader (i.e. u-boot).
> > 
> > > What tool does one use to extract this rom?
> > 
> > it's memory mapped, so any code that runs on the processor can read it. 
> > which is fairly trivial when the part can boot linux.
> 
> So it sounds like these would qualify as device firmware, which are
> okay to have source trees in some circles, but I'm obviously not a lawyer,
> and certainly not an FSF representative in any way regarding
> licensing/copyright, so I may be totally wrong, and I don't know if
> FSF repositories belong in the circles that allow such blobs.

it depends how you qualify it.  this is not microcode that is loaded at 
runtime and/or can be modified in any way.  it is completely burned into the 
hardware.  every Blackfin processor has a static ROM when it comes out of the 
factory sitting at address 0xef000000.  it's not like we're talking firmware 
blobs that get loaded into a parallel processor at runtime (i.e. WiFi drivers) 
which could in practice be tweaked by end users.

> Is there any other similar case in the sim/ for other
> architectures, perhaps?

i couldnt really find anything.  but i get the feeling that people stopped 
doing this level of development on the GNU sim some time ago.

> I think you'll need to find out about that redistributable license, and
> someone other than me will have to bless having such binaries in
> the tree.  I suggest contacting FSF legal.
> 
> Patch-wise, I expect you'll at least need to put your answers above
> in the sources in some form, and add mentions of the copyright and
> licensing that applies to these files and blobs.

sounds more like i'll just drop it for now since it is a minor part of the 
bigger picture.
-mike


  reply	other threads:[~2011-02-15 21:56 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 [this message]
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
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=201102151656.34375.vapier@gmail.com \
    --to=vapier@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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