[lkml]   [2007]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: serio interface
Am 06.06.2007 11:51 schrieb Jan-Benedict Glaw:
> On Wed, 2007-06-06 11:34:49 +0200, Lars K.W. Gohlke <> 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:
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2007-06-07 18:13    [W:0.056 / U:2.672 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site