Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Marko Mlinar" <Marko.Mlinar@campus.fri.uni-lj.si>
To: "Andrew Cagney" <ac131313@cygnus.com>
Cc: <jtc@redback.com>, <gdb@sources.redhat.com>,
	"Damjan Lampret" <lampret@opencores.org>, <igorm@opencores.org>,
	"Johan Rydberg" <johan.rydberg@netinsight.se>
Subject: Re: gdb port to or1k
Date: Fri, 27 Apr 2001 23:07:00 -0000	[thread overview]
Message-ID: <00a401c0cfa9$88b108a0$dc4902c1@Javor> (raw)
In-Reply-To: <3AE9CE96.1E5168A6@cygnus.com>

> Provided your target is implemented correctly it will just build and
> work from any host.  There is also gdb/ser-unix.c which addresses many
> of the portability issues (provided it is talking to something that
> looks like a serial device).
Huh, do you know where can I get infos neeed for various platforms and
test them? What is the practice for this in GNU?

> One thing, people have found that trying to bash bits through lpt can be
> really slow.  There is an open source project that included a (linux)
> device driver to do that bit banging (I've lost the url? :-( ).
I've seen JTAG driver or BDM driver.
I am aware that JTAG driver is very slow.
We are hoping we can get troughput of 75kB/sec (with some extra logic),
and 15kB/sec without any logic.
Do you think that is enough?

> The GDB home page also lists several open source remote servers that you
> might be interested in.

thanks,
    Marko




  reply	other threads:[~2001-04-27 23:07 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 [this message]
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
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='00a401c0cfa9$88b108a0$dc4902c1@Javor' \
    --to=marko.mlinar@campus.fri.uni-lj.si \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sources.redhat.com \
    --cc=igorm@opencores.org \
    --cc=johan.rydberg@netinsight.se \
    --cc=jtc@redback.com \
    --cc=lampret@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