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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 26 Jan 2010 02:13:06 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	William Hubbs <w.d.hubbs@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
	gregkh@...e.de, Samuel Thibault <samuel.thibault@...-lyon.org>,
	Chris Brannon <cmbrannon79@...il.com>,
	Kirk Reiser <kirk@...sers.ca>
Subject: Re: request for assistance:  accessing ttys from kernel space

> Currently, speakup is using direct hardware access to communicate with
> serial ports.  Doing so, however, has limitations since we are hard
> coding port addresses and IRQ numbers.  For example, we have a user

I pointed this out several years ago

> What I would like to discuss is how we can access ttys from kernel
> space.  If we could do this, it would definitely make things much easier
> for us in speakup.

Basically - use a line discipline, that lets you sit on top of a tty and
interact with the hardware

> We need to be able to access the ttys as early as possible in the boot
> sequence.  Any help, suggestions, or guidance you could give us would be
> greatly appreciated.

We may need to make some special provision for that aspect - we already
do so for the early serial console support. The ldisc is the start point
then there may be some bits that need to be extended around it.

A bigger problem is going to be the fact non USB serial is vanishing bit
by bit. We do have a USB console but it's truely crazy stuff and
extending it scares me 8)
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ