Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Damjan Lampret" <lampret@opencores.org>
To: "Marko Mlinar" <Marko.Mlinar@campus.fri.uni-lj.si>, <jtc@redback.com>
Cc: "Johan Rydberg" <johan.rydberg@netinsight.se>,
	<igorm@opencores.org>, <gdb@sources.redhat.com>
Subject: Re: gdb port to or1k
Date: Mon, 30 Apr 2001 10:49:00 -0000	[thread overview]
Message-ID: <001901c0d19f$05c07c80$0a01010a@xxx.si> (raw)
In-Reply-To: <5mhez69uqr.fsf@jtc.redback.com>

----- Original Message -----
From: "J.T. Conklin" <jtc@redback.com>

> Please note that it is a GDB goal (or at least one of my my goals as
> a GDB hacker) that features be available on as many host machines as
> possible.  While there have been back ends which have been integrated
> into GDB that need a special vendor-supplied DLL which ties it to a
> single host platform (ie. windows), I'd rather avoid this if at all
> possible.
>
> If I understand your intentions, you intend to use a bi-directional
> parallel port to bit-bang a JTAG like interface.  This limits the
> feature to machines with bi-directional parallel hardware running
> OS's that allow user-level programs access to the individual lines.
> I think this is OK.
>

In fact this is our goal as well. We'd like to be able to use any platform
in order to debug our target (Linux, Solaris, Windows etc).

So we don't want to have a low level driver for a parallel port that would
work just on Linux/i386. At the moment we are investigating compatibility
between parallel ports on different platforms and it seems that basic
centronics (8 out + 5 in) is supported by majority of them. We could
certainly use help from GDB community to help us test different parallel
port implementations and access to them under different operating systems
(Marko and me only have access to i386 HW running Linux or Windows and to
Sun Blade 100 running Solaris 8).

I think it would be great to have a "standard" parallel port interface for
all targets that use JTAG/BDM or something similar. As you probably know a
lot of microcontrollers lately use some kind of serial debug protocol and
having a common infrastructure in GDB to support all of them through a much
faster parallel port would be great (something faster than a serial port on
a host).

regards,
Damjan



  reply	other threads:[~2001-04-30 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 11:17 Marko Mlinar
2001-04-26 15:04 ` J.T. Conklin
2001-04-27  0:04   ` Marko Mlinar
2001-04-27 12:56     ` Andrew Cagney
2001-04-27 23:07       ` Marko Mlinar
2001-04-30  9:45         ` Andrew Cagney
2001-04-30 10:44         ` J.T. Conklin
2001-04-30 10:13     ` J.T. Conklin
2001-04-30 10:49       ` Damjan Lampret [this message]
2001-04-30 18:07       ` Andrew Cagney
2001-04-30 22:15       ` 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='001901c0d19f$05c07c80$0a01010a@xxx.si' \
    --to=lampret@opencores.org \
    --cc=Marko.Mlinar@campus.fri.uni-lj.si \
    --cc=gdb@sources.redhat.com \
    --cc=igorm@opencores.org \
    --cc=johan.rydberg@netinsight.se \
    --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