Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Will Cohen <wcohen@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: jtc@redback.com, gdb-patches@sources.redhat.com
Subject: Re: Patch to provide m68k simulator to gdb
Date: Wed, 28 Feb 2001 08:58:00 -0000	[thread overview]
Message-ID: <3A9D2E2C.7F87D4A2@redhat.com> (raw)
In-Reply-To: <3A9D206A.D08A91A0@cygnus.com>

Andrew Cagney wrote:
> 
> "J.T. Conklin" wrote:
> >
> > >>>>> "Will" == Will Cohen <wcohen@redhat.com> writes:
> > Will> DJ Delorie and I have integrated the m68k emulator from the Un*x
> > Will> Amiga Emulator (UAE) with gdb. UAE is GPL'ed software. The
> > Will> ChangeLog entries and patch file are attached to this mail.  I
> > Will> would like to get this incorporated into gdb. Other people
> > Will> might find this patch useful.
> >
> > Cool.  I've wanted a simulator for the m68k family for some time.
> >
> > Some issues:
> >
> >   * You say that UAE is GPL'd (and the UAE webpage also states this),
> >     but there is nothing in the source files that indicate this.  The
> >     files have the copyright statements of individual persons with no
> >     redistribution or licencing info.  I personally am very hesitant
> >     to integrate such code as is.
> 
> Ah yes.  Over the years, there have been many proposals to integrate an
> m68k simulator into the sim source tree only in the past they ended up
> tripping up on the GPL.  Sigh.  Hopefully this one can finally be
> integrated.
> 
> While the copyright doesn't need to be transfered to the FSF the source
> code does need a very clear copyright status.  If someone contributed a
> significant change then that copyright would need to have clearly been
> transfered.
> 
> As a an example PSIM is (C) me.  The contents of one file are (C) IBM.
> The ditribution of that file has been approved - I have bits of paper to
> prove it :-)
> 
>         Andrew
How do we go about and get the pieces of paper to prove that
distribution of that file is approved?

Here is some additional information on the copyrights. I have made a
list of the files in the m68k patch and identified the copyright
listed in each file.  This is the list of UAE authors:

Bernd Schmidt
Herman ten Brugge
Ed Hanway
Samuel Devulder


File					copyright
src/dejagnu/baseboards/m68k-sim.exp	new file
src/gdb/config/m68k/monitor.mt		already in gdb
src/sim/configure			already in gdb
src/sim/configure.in			already in gdb
src/sim/m68k/ChangeLog			new file
src/sim/m68k/Makefile.in		made from gdb's src/sim/sh/Makefile.in
src/sim/m68k/README			new file
src/sim/m68k/build68k.c			Copyright 1995,1996 Bernd Schmidt
src/sim/m68k/compiler.h			(c) 1995 Bernd Schmidt
src/sim/m68k/config.h			Copyright 1995 - 1998 Bernd Schmidt
src/sim/m68k/config.in			made from gdb's src/sim/sh/config.in
src/sim/m68k/configure			made from gdb's src/sim/sh/configure
src/sim/m68k/custom.h			(c) 1995 Bernd Schmidt
src/sim/m68k/fpp.c			Copyright 1996 Herman ten Brugge
src/sim/m68k/gencpu.c			Copyright 1995, 1996, 1997, 1998, 1999, 2000 Bernd Schmidt

src/sim/m68k/include/autoconf.h		(c) 1996 Ed Hanway
src/sim/m68k/include/debug.h		(c) 1995 Bernd Schmidt
src/sim/m68k/include/ersatz.h		(c) 1995 Bernd Schmidt
src/sim/m68k/include/memory.h		Copyright 1995 Bernd Schmidt
src/sim/m68k/include/options.h  	Copyright 1995, 1996 Ed Hanway
					Copyright 1995-98 Bernd Schmidt

src/sim/m68k/include/readcpu.h		none listed (from UAE)
src/sim/m68k/include/sysdeps.h  	Copyright 1996, 1997 Bernd Schmidt
src/sim/m68k/include/uae.h		Copyright 1996 Bernd Schmidt
src/sim/m68k/include/uaeexe.h		(c) 1997 by Samuel Devulder
src/sim/m68k/include/zfile.h		(c) 1996 Samuel Devulder
src/sim/m68k/interp.c			made from gdb's  src/sim/sh/interp.c
src/sim/m68k/machdep/m68k.h		Copyright 1996 Bernd Schmidt
src/sim/m68k/machdep/maccess.h		Copyright 1996 Bernd Schmidt
src/sim/m68k/machdep/rpt.h		Copyright 1997, 1998 Bernd Schmidt
src/sim/m68k/md-fpp.h			Copyright 1996 Herman ten Brugge
src/sim/m68k/memory.c			(c) 1995 Bernd Schmidt
src/sim/m68k/missing.c			Copyright 1997 Bernd Schmidt
src/sim/m68k/newcpu.c			(c) 1995 Bernd Schmidt
src/sim/m68k/newcpu.h			Copyright 1995 Bernd Schmidt
src/sim/m68k/readcpu.c			Copyright 1995,1996 Bernd Schmidt
src/sim/m68k/support.c			Copyright 1996 Bernd Schmidt
src/sim/m68k/sysconfig.h		none listed (from UAE)
src/sim/m68k/table68k			none listed (from UAE)
src/sim/m68k/target.h			Copyright 1997 Bernd Schmidt

-Will


  reply	other threads:[~2001-02-28  8:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 14:59 Will Cohen
2001-02-27 15:35 ` J.T. Conklin
2001-02-28  8:02   ` Andrew Cagney
2001-02-28  8:58     ` Will Cohen [this message]
2001-02-28  9:17       ` Andrew Cagney
2001-03-05 13:12         ` Will Cohen
2001-02-28  8:39 ` Andrew Cagney
2001-02-28  9:01   ` Will Cohen
2001-03-01 11:24   ` Will Cohen
2001-03-01 11:54     ` Andrew Cagney
2001-03-05 13:25   ` Will Cohen
2001-03-05 14:57     ` Andrew Cagney
2001-03-06  8:22       ` Will Cohen
2001-03-06 10:07         ` Frank Ch. Eigler
2001-03-09 12:54           ` Andrew Cagney
2001-03-05 15:12     ` Andrew Cagney
2001-03-06 10:11       ` Frank Ch. Eigler

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=3A9D2E2C.7F87D4A2@redhat.com \
    --to=wcohen@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jtc@redback.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