From: Andrew Batchelor <A.C.Batchelor-99@student.lboro.ac.uk>
To: Jim Blandy <jimb@redhat.com>
Cc: GDB Newsgroup <gdb@sources.redhat.com>
Subject: Re: GDB --> Parallel Port --> Target??
Date: Wed, 08 Oct 2003 13:44:00 -0000 [thread overview]
Message-ID: <1065620784.1045.330.camel@And.Linux> (raw)
In-Reply-To: <vt2ad8dt3ms.fsf@zenia.home>
On Tue, 2003-10-07 at 17:27, Jim Blandy wrote:
> Andrew Batchelor <A.C.Batchelor-99@student.lboro.ac.uk> writes:
>
> > Hello,
> >
> > I was wondering how straightforward it would be to write an extension
> > for GDB to use the parallel port to connect to a target instead of the
> > serial port? (Changing only a few files? Many files? Which ones?,
> > etc.)
> >
> > Now I'm not really very familiar with GDB and before I jump in at the
> > deep end, I was wondering if any of you guys could give me any pointers?
> > At the moment I'm just having a read through the User Manual and the
> > Internals Manual and looking at some of the C files that look like they
> > might be of some help - can any of you guys point me in the right
> > direction?
> >
> > Any help or advice you could offer would be much appreciated.
Hi Jim,
Thanks for your reply.
> If it turns out that doesn't work because the parallel device needs
> special handling, that can be done pretty easily.
> Someone asked about this regarding USB recently:
>
> http://sources.redhat.com/ml/insight/2003-q4/msg00016.html
Ah, that all looks more like what I'm after.
> Oddly enough, it seems like someone was thinking about this at some
> point. In serial.c:
[.....]
> But this is just parsing what comes after "target remote". So "target
> remote lpt" would try to find a serial interface named "parallel".
> But there is no code I could find that registered an interface by that
> name, so the open would fail.
Yeah, I couldn't find anything either.
Looks like I need to have a stab at writing something myself:
Can I check the flow of things?
1) Create new serial_ops structure pointing to initialise functions,
etc.
2) Then call this serial_add_interface to register the new structure.
3) Add a new case to serial_open in serial.c for argument parsing to
'target remote'.
I may need to do some protocol conversion from the Remote Serial
Protocol to something else.
Could you offer any advice on this?
Andy
next prev parent reply other threads:[~2003-10-08 13:44 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 [this message]
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
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=1065620784.1045.330.camel@And.Linux \
--to=a.c.batchelor-99@student.lboro.ac.uk \
--cc=gdb@sources.redhat.com \
--cc=jimb@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