| 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: Thu, 8 Mar 2007 15:23:39 -0500 From: Robin Getz <rgetz@...ckfin.uclinux.org> To: "Russell King" <rmk+lkml@....linux.org.uk> Cc: "Oleksiy Kebkal" <kebkal@...il.com>, "Krzysztof Halasa" <khc@...waw.pl>, "Mike Frysinger" <vapier.adi@...il.com>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, linux-serial@...r.kernel.org Subject: Re: should RTS init in serial core be tied to CRTSCTS On Thu 8 Mar 2007 08:48, Russell King pondered: > On Thu, Mar 08, 2007 at 08:44:31AM -0500, Robin Getz wrote: > > That would let you change things are run time, but the problem is at > > boot time. A default setting needs to be set, so when things initialize, > > and proc does not exist yet, it is still set properly... > > I disagree. "proc does not exist yet" - the only time that applies is > long before userspace as active. Right - We both agree - And setting console=/dev/null in the bootargs still does not help. When the kernel initializes the UART Port, it asserts RTS - which confuses the host it is attached to (in this case, the Linux system is the serial peripheral). How about adding a module_param to serial core, which the default is to assert RTS (as is today), and someone (like me) can override with serial_core.RTS=0 -Robin - 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