From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5304 invoked by alias); 18 Mar 2003 16:53:42 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5250 invoked from network); 18 Mar 2003 16:53:42 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 18 Mar 2003 16:53:42 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 1A9D62B11; Tue, 18 Mar 2003 11:53:38 -0500 (EST) Message-ID: <3E774F11.70409@redhat.com> Date: Tue, 18 Mar 2003 16:53:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: msarasa@fh-konstanz.de Cc: gdb@sources.redhat.com Subject: Re: ser-tcp ser-unix question References: <1048004350.3e7746ff02818@webmail.fh-konstanz.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00278.txt.bz2 > 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