From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Cc: gregkh@suse.de, Samuel Thibault <samuel.thibault@ens-lyon.org>,
Chris Brannon <cmbrannon79@gmail.com>,
Kirk Reiser <kirk@reisers.ca>
Subject: request for assistance: accessing ttys from kernel space
Date: Mon, 25 Jan 2010 20:02:03 -0600 [thread overview]
Message-ID: <20100126020203.GA23551@linux1> (raw)
Hello.
I am the lead developer for gentoo linux's accessibility team[1], and I
am on the development team for the speakup screen reader [2].
I received these addresses from Samuel, and Chris and Kirk are the other
developers on the speakup team.
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
right now who is wanting to use a PCI Express serial card for his
synthesizer, but the port and IRQ are not standard, so speakup is unable
to use it. He says that the kernel does recognize the card however.
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.
For reference, our git repository is at
http://linux-speakup.org/speakup.git. We are looking to write another
.c file similar to serialio.c but using ttys or some other way to access
the serial ports which works better than hard coading ports and IRQs.
We found another example of attempting this on the web [3], but this
doesn't work any longer according to the thread.
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.
Thanks much,
William
[1] http://www.gentoo.org/proj/en/desktop/accessibility
[2] http://linux-speakup.org
[3]
http://www.linuxquestions.org/questions/programming-9/accessing-tty-in-kernel-space-596538/
next reply other threads:[~2010-01-26 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 2:02 William Hubbs [this message]
2010-01-26 2:13 ` request for assistance: accessing ttys from kernel space Alan Cox
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=20100126020203.GA23551@linux1 \
--to=w.d.hubbs@gmail.com \
--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 \
/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