Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Batchelor <A.C.Batchelor-99@student.lboro.ac.uk>
To: Andrew Cagney <ac131313@redhat.com>
Cc: GDB Newsgroup <gdb@sources.redhat.com>
Subject: Re: GDB --> Parallel Port --> Target??
Date: Fri, 10 Oct 2003 16:53:00 -0000	[thread overview]
Message-ID: <1065804937.1168.19.camel@And.Linux> (raw)
In-Reply-To: <3F846765.6070403@redhat.com>

On Wed, 2003-10-08 at 20:37, Andrew Cagney wrote:
> FYI, it should just work.  For GDB, there should really be no difference 
> between a serial and parallel character interface.
[.....]
> The correct kernel driver will let GDB talk though to the USB connected 
> device as if it was a normal serial device.
[.....] 
> Of course, if it's the actual USB chip that your trying to communicate 
> with, things can get a bit messy.  While having the USB chip include a 
> pseudo-serial interface that talked remote-protocol would work, I've 
> seen implementations that ended up having a debug agent translate remote 
> protocol into USB primatives.

Thanks for your reply.

Oh, right - I guess that saves me a bit of coding then.  Have you read
the other emails?  I'll probably be needing to alter the way GDB sends
the characters to the parallel port when I code this protocol
converter.  Any idea what files I'll be looking at?

I've scanned a bit through serial.c and remote.c and found most things I
think.


Andy


      reply	other threads:[~2003-10-10 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 10:00 Andrew Batchelor
2003-10-07 16:28 ` Jim Blandy
2003-10-08 13:44   ` Andrew Batchelor
2003-10-08 17:55     ` Jim Blandy
2003-10-10 16:49       ` Andrew Batchelor
2003-10-10 19:32         ` Jim Blandy
2003-10-08 19:37   ` Andrew Cagney
2003-10-10 16:53     ` Andrew Batchelor [this message]

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=1065804937.1168.19.camel@And.Linux \
    --to=a.c.batchelor-99@student.lboro.ac.uk \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.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