Re: ntdll: Store full line status register in the internal structure, not just the TIOCSER_TEMT bit. Take 2.

Dmitry Timoshkov dmi...@baikal.ru writes: Printing complete lsr value in the log may help with diagnosing test failures on Alexandre's machine. I don't see how, since TIOCSER_TEMT is the only defined bit. Do you actually have a driver that returns other status? -- Alexandre Julliard

Re: ntdll: Store full line status register in the internal structure, not just the TIOCSER_TEMT bit. Take 2.

Alexandre Julliard julli...@winehq.org wrote: Printing complete lsr value in the log may help with diagnosing test failures on Alexandre's machine. I don't see how, since TIOCSER_TEMT is the only defined bit. Do you actually have a driver that returns other status? I don't, but maybe

Re: ntdll: Store full line status register in the internal structure, not just the TIOCSER_TEMT bit. Take 2.

Dmitry Timoshkov dmi...@baikal.ru writes: Alexandre Julliard julli...@winehq.org wrote: Printing complete lsr value in the log may help with diagnosing test failures on Alexandre's machine. I don't see how, since TIOCSER_TEMT is the only defined bit. Do you actually have a driver that

Re: ntdll: Store full line status register in the internal structure, not just the TIOCSER_TEMT bit. Take 2.

Alexandre Julliard julli...@winehq.org wrote: Printing complete lsr value in the log may help with diagnosing test failures on Alexandre's machine. I don't see how, since TIOCSER_TEMT is the only defined bit. Do you actually have a driver that returns other status? I don't, but

Re: ntdll: Store full line status register in the internal structure, not just the TIOCSER_TEMT bit. Take 2.

Dmitry Timoshkov dmi...@baikal.ru writes: Alexandre Julliard julli...@winehq.org wrote: Printing complete lsr value in the log may help with diagnosing test failures on Alexandre's machine. I don't see how, since TIOCSER_TEMT is the only defined bit. Do you actually have a driver