From: Timur Tabi <timur@freescale.com>
To: linux-console@vger.kernel.org
Subject: Is this mailing list dead?
Date: Wed, 27 Oct 2010 15:38:01 -0500 [thread overview]
Message-ID: <4CC88DA9.7010103@freescale.com> (raw)
Is anyone reading this mailing list? I presume that since it's called
"linux-console" and hosted on kernel.org, that this is the right place to ask
for help with writing console drivers. However, it doesn't appear that anyone
is actually reading this list, so I want to make sure I'm not wasting my time here.
I'm trying to write a console/TTY driver that is not a UART driver, and I can't
seem to find a good example of such a driver out there. Specfically, my driver
has an interrupt handler that calls tty_insert_flip_string() when it receives
new input. What I don't understand is how am I supposed to know what "struct
tty_struct" to use for this function. It appears that it's possible to open the
TTY device multiple times, each time with a different struct tty_struct. But I
can only have one interrupt handler, so I don't know how I'm supposed to
determine which of the many struct tty_struct pointers to use.
--
Timur Tabi
Linux kernel developer at Freescale
reply other threads:[~2010-10-27 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CC88DA9.7010103@freescale.com \
--to=timur@freescale.com \
--cc=linux-console@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).