Path: utzoo!mnetor!uunet!oddjob!gargoyle!ihnp4!occrsh!uokmax!rmtodd From: rmtodd@uokmax.UUCP (Richard Michael Todd) Newsgroups: comp.os.minix Subject: Re: Why no ispeed/ospeed?? Message-ID: <1079@uokmax.UUCP> Date: 2 Mar 88 15:35:26 GMT References: <213@gould.doc.ic.ac.uk> Reply-To: rmtodd@uokmax.UUCP () Distribution: comp Organization: University of Oklahoma, Norman, OK Lines: 15 In article <213@gould.doc.ic.ac.uk> lmjm@icdoc.UUCP writes: >I was looking at it with an eye to modem control and such. I must confess >to being quite suprised to find that there was no sg_ispeed and sg_ospeed >fields in the sgttyb structure. Indeed there is no baud rate control >anywhere that I can find. That's because the original MINIX didn't have any drivers at all for the serial port. There isn't much point in changing the speed of the port if you can't read or write to it. Thus the ioctl() implementation wasn't designed to handle ispeed and ospeed >How are you supposed to achieve this? Currently you don't. In the current implementation of Jim Paradis's serial- port device driver, the baud rate is hardwired into the kernel. Not great, but better than no serial port access at all, which is what we had before. Supposedly Jim's going to redo the ioctl() implementation to add ispeed and ospeed.