From: Mike Frysinger <vapier@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] sim: bfin: new port
Date: Mon, 14 Feb 2011 22:11:00 -0000 [thread overview]
Message-ID: <201102141710.54603.vapier@gmail.com> (raw)
In-Reply-To: <201102142144.37425.pedro@codesourcery.com>
On Monday, February 14, 2011 16:44:37 Pedro Alves wrote:
> On Monday 14 February 2011 20:49:50, Mike Frysinger wrote:
> > On Monday, February 14, 2011 15:40:18 Pedro Alves wrote:
> > > On Monday 14 February 2011 20:14:32, Mike Frysinger wrote:
> > > >+++ b/sim/bfin/bfroms/bf59x_l1-0.1.h
> > > >
> > > > @@ -0,0 +1,8195 @@
> > > > +/* DO NOT EDIT: Autogenerated. */
> > > > +static const char bfrom_bf59x_l1_0_1[] = {
> > >
> > > What are these generated from?
> >
> > memory dumps of the rom from actual hardware
>
> 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.
> What's the copyright and license for this?
ADI releases the source code to these roms for anyone to view/play with, but
they hold the copyrights. i'm not sure there is any license mention in the
source files, but they arent terribly useful for anything else considering
they're written in pure assembly, assume rom locations in the processor,
generally require proprietary ADI tools to compile/link, and no one else can
make a Blackfin processor.
but that is the source code, not the final binary which is what we're talking
about here: gcc foo.c -o foo; objcopy -O binary foo foo.bin; <convert foo.bin
into a header>. what license would be necessary for inclusion ? i'm fairly
certain a redistributable license (if not already in place) would be trivial
to get seeing as i am an ADI employee. i dont think copyright makes much
sense with these things.
-mike
next prev parent reply other threads:[~2011-02-14 22:11 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 [this message]
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
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=201102141710.54603.vapier@gmail.com \
--to=vapier@gmail.com \
--cc=gdb-patches@sourceware.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