On Apr 8, 11:17 am, Grant Edwards wrote:
> On 2010-04-07, Max Kotasek wrote:
>
> > I'm trying to figure out how to parse the responses fromfcntl.ioctl()
> > calls that modify the serial lines in a way that asserts that the line
> > is now changed.
>
> Two comments:
>
> 1) None of the Linux seri
On 2010-04-08, Anssi Saari wrote:
> It seems to me also that RTS is always on after the port has been
> opened. I didn't dig out my voltmeter or anything to check this,
> though.
IIRC, that's generally true: RTS and DTR are both set to "on" by the
tty layer's open() handler _if_ the device's use
On 2010-04-07, Max Kotasek wrote:
> I'm trying to figure out how to parse the responses from fcntl.ioctl()
> calls that modify the serial lines in a way that asserts that the line
> is now changed.
Two comments:
1) None of the Linux serial drivers I've worked on return line states
except
Max Kotasek writes:
> Hello to all out there,
>
> I'm trying to figure out how to parse the responses from fcntl.ioctl()
> calls that modify the serial lines in a way that asserts that the line
> is now changed. For example I may want to drop RTS explicitly, and
> assert that the line has been d
Hello to all out there,
I'm trying to figure out how to parse the responses from fcntl.ioctl()
calls that modify the serial lines in a way that asserts that the line
is now changed. For example I may want to drop RTS explicitly, and
assert that the line has been dropped before returning.
Here is
