public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: William Hubbs <w.d.hubbs@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	gregkh@suse.de, Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Chris Brannon <cmbrannon79@gmail.com>,
	Kirk Reiser <kirk@reisers.ca>
Subject: Re: request for assistance:  accessing ttys from kernel space
Date: Tue, 26 Jan 2010 02:13:06 +0000	[thread overview]
Message-ID: <20100126021306.16809e71@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20100126020203.GA23551@linux1>

> 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)

  reply	other threads:[~2010-01-26  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  2:02 request for assistance: accessing ttys from kernel space William Hubbs
2010-01-26  2:13 ` Alan Cox [this message]
2010-01-26  2:40   ` Samuel Thibault
2010-01-26 13:39     ` Alan Cox
2010-01-28  0:45       ` Samuel Thibault
2010-01-26  2:27 ` Samuel Thibault

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100126021306.16809e71@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=cmbrannon79@gmail.com \
    --cc=gregkh@suse.de \
    --cc=kirk@reisers.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=w.d.hubbs@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox