Blocking serial support

Ned Konz ned at bike-nomad.com
Wed Jun 12 04:32:14 UTC 2002


On Tuesday 11 June 2002 09:05 pm, Craig Latta wrote:
> > > What do you think of the framework put forth by Flow
> > > (http://netjam.org/flow)? I think the things you want would fit
> > > nicely there.
> >
> > They probably would. I'd use it if it were available for 3.2.
> >
> > Do both the full- and half- duplex modes of operation work
> > simply? i.e. having one process reading/writing or have two
> > processes, one reading and one writing?
>
> 	I think so. Can you give an example? (Also, I'm not sure I was
> able to parse your last sentence correctly. :)  What test scenario
> do you recommend I use?

Two scenarios:

1. Independent processes (a la communications terminal program): one 
process reads the port input and acts when data is received, and one 
process writes out to the port.

2. One process (like, say, a serially connected robot) alternates 
sending and receiving: send a command, process blocks till (some) 
data is available.

Also, it would be nice to have access to the various flags and 
characters for tcsetattr(). Like CLOCAL, HUPCL, VMIN, VTIME. Also 
tcsendbreak(), tcdrain() and tcflush().

As well as modem control:
TIOCMGET, TIOCMBIS, TIOCMSET, TIOCMBIC 
For:
 TIOCM_DSR, TIOM_CD, TIOC_CTS, TIOC_RI, and TIOC_DTR and TIOC_RTS 

> 	So, I'll get back onto my normal schedule of first-friday
> releases, and say Friday 5 July.

Sounds good!

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE




More information about the Squeak-dev mailing list