Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Marko Mlinar <markom@opencores.org>
Cc: Andrew Cagney <ac131313@ges.redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Merging OC gdb with official gdb
Date: Wed, 02 Oct 2002 16:07:00 -0000	[thread overview]
Message-ID: <3D9B7C39.5080502@redhat.com> (raw)
In-Reply-To: <200209190849.10674.markom@opencores.org>

>> > I've prepared preliminary patch (current version) port for or1k cpu (see
>> > below).
>> > There are also attached files, that should be added:
>> > gdb/or1k-tdep.c (target description file)
>> > gdb/remote-or1k.c (proprietary jtag protocol)
>> > gdb/jtag.c (remote jtag communication client)
>> > gdb/config (dir)
>> > gdb/config/or32.mt (target definition)
>> > gdb/config/tm-or1k.h (or1k architecture macros)
>> > gdb/config/tm-or32.h (or32 implementation target macros)
>> >
>> > Originaly it was written for gdb-5.0, but recently we wanted to join it
>> > with official release, so I coded the macros in gdbarch.
> 
>>
>> Yep, we're getting there.  Before anything else, the file jtag.c:
> 
>> > /* Remote debugging interface for JTAG debugging protocol.
>> >    JTAG connects to or1k target ops. See or1k-tdep.c
>> >
>> >    Copyright 1993-1995, 2000 Free Software Foundation, Inc.
>> >    Contributed by Cygnus Support.  Written by Marko Mlinar
>> >    <markom@opencores.org>
>> >    Areas noted by (CZ) were modified by Chris Ziomkowski
>> >    <chris@asics.ws>
> 
>>
>> I don't see any paper work for ChrisZ.  Lets separate out this file and
>> any thing related (remote-or1k.c?) and leave it for later.
> 
> CZ did some small changes to my code. AFAIK this is not a problem, right?
> You can also check our cvs 
> (http://www.opencores.org/cvsweb.shtml/or1k/binutils/) for his updates.
> 
> 
>> (It also wasn't contributed by Cygnus Support.)
> 
> sorry ;) I copied this header from somewhere and forgot to correct it.

I'm about to go walkabout which means somewhat sporadic e-mail.  I'll 
pick this part up in a few weeks :-( (unless someone else wants to).

Andrew



  reply	other threads:[~2002-10-02 23:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200209041256.47379.markom@opencores.org>
     [not found] ` <3D7CC5F0.7040100@ges.redhat.com>
     [not found]   ` <200209161329.37700.markom@opencores.org>
2002-09-17  5:44     ` Marko Mlinar
2002-09-18 12:59       ` Andrew Cagney
2002-09-18 23:49         ` Marko Mlinar
2002-10-02 16:07           ` Andrew Cagney [this message]
2002-09-18 13:53       ` Andrew Cagney
2002-09-19  2:00         ` Marko Mlinar
2002-09-19 17:33           ` Andrew Cagney
2002-09-20  5:01             ` Marko Mlinar
2002-10-02 16:51               ` Andrew Cagney
2002-10-03 23:11                 ` Marko Mlinar
2002-10-09  5:00                 ` Marko Mlinar
2002-10-09 16:11                   ` David Carlton
2002-10-10  0:42                     ` Marko Mlinar
2002-10-10 12:34                       ` David Carlton
2002-09-23  4:48             ` Marko Mlinar
2002-09-23 22:05               ` Eli Zaretskii
2002-09-24  5:03                 ` Marko Mlinar
2002-09-24  8:20                   ` Eli Zaretskii
2002-09-24 23:59                     ` Marko Mlinar
2002-10-03  7:06 Marko Mlinar

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=3D9B7C39.5080502@redhat.com \
    --to=ac131313@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=markom@opencores.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