linux-kernel - Re: serio interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 6 Jun 2007 11:51:59 +0200
From:	Jan-Benedict Glaw <jbglaw@...-owl.de>
To:	linux-kernel@...r.kernel.org, "Lars K.W. Gohlke" <lkwg82@....de>
Subject: Re: serio interface

On Wed, 2007-06-06 11:34:49 +0200, Lars K.W. Gohlke <lkwg82@....de> wrote:
> Jan-Benedict Glaw schrieb:
> > On Wed, 2007-06-06 11:11:23 +0200, Lars K.W. Gohlke <lkwg82@....de> wrote:
> > > wouldsomebody explain me the serio interface or give me a code link for
> > > very simple example.
> >
> > What do you want to do with it?  Do you want on the serial port side,
> > or on the mouse/keyboard/gadget side?  See for example the various
> > serial keyboards and mice drivers.
>
> 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?

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@...-owl.de              +49-172-7608481
Signature of:                     Eine Freie Meinung in einem Freien Kopf
the second  :                   für einen Freien Staat voll Freier Bürger.

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)