| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 19 Jul 2009 15:34:48 +0200 From: Samuel Thibault <samuel.thibault@...-lyon.org> To: Tilman Schmidt <tilman@...p.cc> Cc: Janusz Krzysztofik <jkrzyszt@....icnet.pl>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>, "alsa-devel@...a-project.org" <alsa-devel@...a-project.org> Subject: Re: [RFC] tty (or char) bus? Tilman Schmidt, le Sun 19 Jul 2009 15:19:22 +0200, a écrit : > The only inconvenience is how LDs are loaded and attached to a serial > interface, via the TIOCSETD ioctl, because you need a userspace daemon > which keeps the tty device open so that the LD stays attached to it. Yes, that's a burden for me also, while I could just tell my module to use ttyS0 through parameters for instance. Samuel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists