[Bluetooth] Use non-canonical TTY by default for RFCOMM
While the RFCOMM TTY emulation can act like a real serial port, in reality it is not used like this. So to not mess up stupid applications, use the non-canonical mode by default. Signed-off-by: Denis Kenzior <denis.kenzior@trolltech.com> Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
This commit is contained in:
parent
78c6a1744f
commit
ca37bdd53b
|
@ -1123,6 +1123,7 @@ int rfcomm_init_ttys(void)
|
||||||
rfcomm_tty_driver->flags = TTY_DRIVER_REAL_RAW | TTY_DRIVER_DYNAMIC_DEV;
|
rfcomm_tty_driver->flags = TTY_DRIVER_REAL_RAW | TTY_DRIVER_DYNAMIC_DEV;
|
||||||
rfcomm_tty_driver->init_termios = tty_std_termios;
|
rfcomm_tty_driver->init_termios = tty_std_termios;
|
||||||
rfcomm_tty_driver->init_termios.c_cflag = B9600 | CS8 | CREAD | HUPCL | CLOCAL;
|
rfcomm_tty_driver->init_termios.c_cflag = B9600 | CS8 | CREAD | HUPCL | CLOCAL;
|
||||||
|
rfcomm_tty_driver->init_termios.c_lflag &= ~ICANON;
|
||||||
tty_set_operations(rfcomm_tty_driver, &rfcomm_ops);
|
tty_set_operations(rfcomm_tty_driver, &rfcomm_ops);
|
||||||
|
|
||||||
if (tty_register_driver(rfcomm_tty_driver)) {
|
if (tty_register_driver(rfcomm_tty_driver)) {
|
||||||
|
|
Loading…
Reference in a new issue