From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mohammed Illyas Mansoor <mansoor@cdotb.ernet.in>
To: bartv@cygnus.co.uk
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Serial device driver for linux synthetic target!
Date: Tue, 05 Oct 1999 08:10:00 -0000
Message-id: <37F9C7D7.665CCA26@cdotb.ernet.in>
References: <37F9865C.3496B9C3@cdotb.ernet.in> <199910051316.OAA06305@sheesh.cygnus.co.uk>
X-SW-Source: 1999-10/msg00021.html

Bart Veer wrote:

> Within Cygnus we have been thinking along slightly different lines,
> but nothing has been implemented yet. The basic idea involved having
> the synthetic target application talking over a pipe to an external
> multiplexer process (possibly a program, possibly a Tcl script running
> in a suitable interpreter, whatever).

            This would require a protocol between the pseudo_dev and the
multiplexer process as to which actual dev it wants to talk to for eg., lcd,
serial-dev or say a socket, also how this device would interact with the
eCos applications is also not very clear, as to how it would handle an
application requesting to open say /dev/ttyS0, probably it should be a
catch all device-driver, all this seems a bit complex to me.

          What I am aiming is to have an eCos application which was written to

talk with the serial-device on the actual-hardware,  should be able to run
on the linux synthetic target also, without any modification whatsoever, for
this a pseudo-serial device driver for linux would be sufficient just like for

all other archs. ie., having i386 directory in io/serial/current/src and in
that
a sub-dir called linux or sim (presently) later when eCos supports actual i386

target, the device driver would be written  in i386 directory.

        The actual aim of this synthetic device driver is to help me test
TCP/IP stack which I am planning to port, using the SLIP driver with a linux
box
attached on the other end running SLIP.

> The device-specific application could also send data back to the eCos
> application. This would arrive on the pipe, causing a SIGIO signal to
> be raised. The synthetic target's interrupt handling support would be
> rewritten around SIGIO.
>

    This is what extactly I was having in my mind also.

>
> Obviously there are plenty of details to be resolved, but this would
> be a very powerful extension to the synthetic target support.
>

    This pseudo-device would really be a nice thing to have in the synthetic
target, if the device driver handles all the details with respect to the
multiplexer
process transparent to the eCos application thread.


--With Regards,

M. I. Mansoor