public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Peter Reilley" <micrio@mv.com>
To: <insight@sources.redhat.com>
Cc: "Jim MacGregor" <jamesm@macraigor.com>
Subject: Re: General question
Date: Wed, 20 Aug 2003 02:31:00 -0000	[thread overview]
Message-ID: <038901c366c3$2dc2c1a0$c9d145cc@lndnnh.adelphia.net> (raw)
In-Reply-To: <1061343799.1660.10.camel@lindt.uglyboxes.com>


----- Original Message ----- 
From: "Keith Seitz" <keiths@redhat.com>
To: <insight@sources.redhat.com>
Sent: Tuesday, August 19, 2003 9:43 PM
Subject: Re: General question


> On Tue, 2003-08-19 at 16:53, Rod Boyce wrote:
> > Bdm/wiggler is not a supported configuration by gdb (a
> > proprietary DLL in gdb violates the GPL).
> 
> Ok, to clarify: whether or not using a proprietary DLL with gdb is
> violation of the GPL. Some say yes, some say no. In the end, device
> support is not an Insight issue: it's a gdb issue, and gdb folk have
> apparently decided that although this appears not to violate the letter
> of the GPL, it appears to violate the intent of the GPL. Consequently,
> ser-ocd.c and most on-chip support was dropped from gdb.
> 
> See, for example,
> http://sources.redhat.com/ml/gdb/2001-05/msg00092.html.
> 
> There are many such thread in the gdb mailing list. I suggest you search
> or query the gdb mailing list for the most up-to-date stance on this
> issue.
> 
> Keith

The issue of the DLL was hashed out a few years ago.   I show an email
from Dec. 2000 discussing the issue.   The resolution was that all
code that interfaced to the Macraigor DLL would be removed.   We
did not have a problem with this.   Macraigor moved to using
a LibRemote daemon.   Any left over code such as ser-ocd.c is
not used by Macraigor any more.

The issue of the DLL has been long since resolved.   I thought
that all parties to the issue were happy with the outcome.
Is there some remaining issue to be resolved?

Pete.
Macraigor Systems LLC.

  reply	other threads:[~2003-08-20  2:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  9:37 Hylla, Kai
2003-08-19 16:04 ` Keith Seitz
2003-08-19 17:25   ` Peter Reilley
2003-08-19 19:43   ` Rod Boyce
2003-08-19 23:33     ` Peter Reilley
2003-08-19 23:54       ` Rod Boyce
2003-08-20  1:41         ` Keith Seitz
2003-08-20  2:31           ` Peter Reilley [this message]
2003-08-20  2:42             ` Keith Seitz
2003-08-19 17:13 ` Peter Reilley
2003-08-20  8:57 Hylla, Kai

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='038901c366c3$2dc2c1a0$c9d145cc@lndnnh.adelphia.net' \
    --to=micrio@mv.com \
    --cc=insight@sources.redhat.com \
    --cc=jamesm@macraigor.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).