From: Andrew Cagney <ac131313@redhat.com>
To: msarasa@fh-konstanz.de
Cc: gdb@sources.redhat.com
Subject: Re: ser-tcp ser-unix question
Date: Tue, 18 Mar 2003 16:53:00 -0000 [thread overview]
Message-ID: <3E774F11.70409@redhat.com> (raw)
In-Reply-To: <1048004350.3e7746ff02818@webmail.fh-konstanz.de>
> We're trying to make a new file to define how should gdb connect to a
> simulated UART, as I said before. Forget the other question.
> I see that there are three files called ser-tcp.c , ser-unix.c , ser-pipe.c ,
> and also a pair called ser-something.c.
> In configure.in from gdb there's a point in which SER_HARDWIRE = "ser-unix.c
> ser-tcp.c ser-pipe.c" is shown. But, I'm trying to configure this (just for a
> probe) with SER_HARDWIRE = "ser-unix.o ser-tcp.o ser-pipe.o ser-simuart.o"
> with no results.
>
> I would like to do a new ser-simuart.c file , with all the methods to
> send-receive data to a simulated uart. So I could connect easily gdb to a
> software board simulator that reads/writes to a simulated UART. Before I make
> this ser-simuart.c file, how should I integrate this with the rest of the gdb
> code? Should I do something more or just a new file?
Add the new file. Modify the serial.c code so that it recognizes and
selects the new device (you mentioned this in your previous e-mail).
Get an FSF assignment.
Andrew
next prev parent reply other threads:[~2003-03-18 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 16:18 msarasa
2003-03-18 16:53 ` Andrew Cagney [this message]
2003-03-19 11:42 ` msarasa
2003-03-20 0:14 ` Andrew Cagney
2003-03-20 9:17 ` msarasa
2003-03-20 14:53 ` Andrew Cagney
2003-03-19 11:42 ` msarasa
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=3E774F11.70409@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msarasa@fh-konstanz.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).