From: "Benoit Boissinot" <bboissin@gmail.com>
To: "Néstor Amigo Cairo" <nestorac@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
samuel.thibault@ens-lyon.org
Subject: Re: QUESTION: How can I make a driver for a special serial keyboard which also supports output (maybe via serio_raw)?
Date: Tue, 27 May 2008 19:40:32 +0200 [thread overview]
Message-ID: <40f323d00805271040xcabb660obf8f0a69f9e850b5@mail.gmail.com> (raw)
In-Reply-To: <b321594e0805271027w4f4f003ar20ad0eb95f57721a@mail.gmail.com>
[please keep the cc list and reply to all]
On Tue, May 27, 2008 at 7:27 PM, Néstor Amigo Cairo <nestorac@gmail.com> wrote:
> I have been thinking on it, but it's easier to reimplement some
> widgets on Qt for just three keys (I can reuse them easily because of
> OOP), than managing focus on every widget communicating the
> application directly with the serial port (I've been using a switch
> structure for this purpose, which is not very kindly). I saw the
> device as a keyboard with just three keys and which can also receive
> some bytes from the application. This makes debugging and testing much
> easier than dealing directly with the serial interface for changing
> the focus and managing the application. The only problem is that a
> driver must be written for the device, but my long-term idea is to
> write some kind of programmable driver, so it could be reused easily
> (by instance, assigning a matrix of values to binary data sent to the
> serial port, and converting those bytes into Keys using these values,
> as in the original driver, but allowing userspace apps to change this
> behaviour). I'm not sure if it would be helpful for anyone else. And I
> also lack any knowledge of the kernel internals, as you can see.
If you just want to use it in X, then you could use ttyx (you can find
it at http://youpibouh.thefreecat.org/download/) It translates events
from the serial device to X keyboard event, it was developped by
Samuel for a similar project (a device with a couple buttons that sends
the key via a serial port).
I thinks it would be quite easy to add a table to translate to a different
key if you need that.
regards,
Benoit
next prev parent reply other threads:[~2008-05-27 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b321594e0805250952q18465dc2h8af60aa25143693d@mail.gmail.com>
2008-05-27 12:53 ` Dmitry Torokhov
[not found] ` <b321594e0805271025ia60c356hc19a040920587713@mail.gmail.com>
2008-05-27 17:27 ` Fwd: " Néstor Amigo Cairo
2008-05-27 17:40 ` Benoit Boissinot [this message]
[not found] ` <b321594e0805271451l79912cfcpaf05406a319800aa@mail.gmail.com>
2008-05-28 8:00 ` Néstor Amigo Cairo
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=40f323d00805271040xcabb660obf8f0a69f9e850b5@mail.gmail.com \
--to=bboissin@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nestorac@gmail.com \
--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
all inboxes | Powered by JetHome®