From: Tilman Schmidt <tilman@imap.cc>
To: linux-kernel@vger.kernel.org
Subject: Re: serio interface
Date: Thu, 07 Jun 2007 18:13:07 +0200 [thread overview]
Message-ID: <46682E93.1020602@imap.cc> (raw)
In-Reply-To: <20070606095159.GK2649@lug-owl.de>
[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]
Am 06.06.2007 11:51 schrieb Jan-Benedict Glaw:
> On Wed, 2007-06-06 11:34:49 +0200, Lars K.W. Gohlke <lkwg82@gmx.de> wrote:
>> I want on the kernelside process data from first uart-hardware interface
>> aka ttyS0.
>>
>> I don't understand the structure of e.g. input/mouse/sermouse.c
>>
>> where is said, which hardware is used for reading data from?
>
> I'm not entirely sure, but I guess that most of the time, you assign a
> serial port with the help of `inputattach' to a given device driver,
> which expects to find its hardware on that port.
>
> OTOH, why do you want to do the serial stuff in kernel land? Isn't it
> a *lot* easier to do it in userspace? What's your specific device you
> want to work on?
May I chime in here, as it's a topic I am interested in too.
Have a look at drivers/isdn/gigaset/ser-gigaset.c if you like,
a driver for an ISDN adapter attached via RS232.
This is currently implemented as a line discipline, but I consider
that a hack. For one thing, it doesn't really fit the concept of a
line discipline because it doesn't transform the serial datastream
but instead diverts it completely to the isdn4linux subsystem. And
second, it means that a userspace daemon is needed which does
nothing but open the serial port, set the line discipline on it,
and go to sleep in order to keep the line discipline loaded.
The serio approach used by input/mouse/sermouse.c might provide a
more sensible way of driving that kind of device.
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-06-07 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 9:11 serio interface Lars K.W. Gohlke
2007-06-06 9:15 ` Jan-Benedict Glaw
2007-06-06 9:34 ` Lars K.W. Gohlke
2007-06-06 9:51 ` Jan-Benedict Glaw
2007-06-06 10:39 ` Lars K.W. Gohlke
2007-06-06 10:44 ` Jan-Benedict Glaw
2007-06-06 10:52 ` Lars K.W. Gohlke
2007-06-06 11:26 ` Jan-Benedict Glaw
2007-06-06 11:36 ` Lars K.W. Gohlke
2007-06-07 16:13 ` Tilman Schmidt [this message]
2007-06-08 10:21 ` Tilman Schmidt
2007-06-06 11:20 ` Jiri Slaby
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=46682E93.1020602@imap.cc \
--to=tilman@imap.cc \
--cc=linux-kernel@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