LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: frank.salomon@wincor-nixdorf.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: EV_MSC / driver/input/input.c (Input Handler)
Date: Fri, 9 Feb 2007 09:36:28 -0500	[thread overview]
Message-ID: <d120d5000702090636r8243772u91908d7608eae0cc@mail.gmail.com> (raw)
In-Reply-To: <45CC1FA5.3090507@wincor-nixdorf.com>

Hi Frank,

On 2/9/07, Frank Salomon <frank.salomon@wincor-nixdorf.com> wrote:
> Hi Dmitry,
>
> Dmitry Torokhov wrote:
>
> > That is because by default atkbd uses software-emulated raw mode.
> > bootk with atkbd.softraw=0 or switch it off after boot through sysfs
> > attribute to get EV_MSC/MSC_RAW passed through).
>
> Thank you for your advice, but I really don't know, what will be the
> secondary effect if it will be switched off.
>
> > No, input core should not pass any events device did not claim to support.
>
> I am not sure, but I think the function input_event in
> drivers/input/input.c has 2 tasks:
> One is to send events to the device (first part: "switch (type){").
>
> The other one is to send the events to the handler (second part:
> "list_for_each_entry(handle, &dev->h_list, d_node)").
>
> This is the reason why I had the idea of changing the code as I have
> described it before.
>
> With the current implementation, the device sends events to the handler.
> But only events, known/claimed by the device are passed through to the
> handler. I believe, this should be handled transparently.
>

Thta is the policy. Unless device claims to support certain events
they will not be passed through so there is no "surprises". This way
userspace applications can query device capabilities, classify them
and adjust behavior accordingly.

> > What are you trying to do though? Why are you interested in raw atkbd
> > events? What will your handler do with events from other input devices
> > that might emit raw events?
>
> I have to connected special Point Of Sales Keyboards. Sometimes they are
> sending none standard scan codes, only make codes and no break codes. I
> had successfully implemented this in kernel version 2.4 and now I have
> to do it in 2.6.
>

You probably want to use serio_raw module for that that provides raw
access to a PS/2 port (2.4-style) and possibly uinput driver to nject
parsed event stream back into kernel for standard delivery to
userspace apps.

-- 
Dmitry

      reply	other threads:[~2007-02-09 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08  8:56 Frank Salomon
2007-02-08 15:15 ` Dmitry Torokhov
2007-02-09  7:15   ` Frank Salomon
2007-02-09 14:36     ` Dmitry Torokhov [this message]

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=d120d5000702090636r8243772u91908d7608eae0cc@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=frank.salomon@wincor-nixdorf.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: EV_MSC / driver/input/input.c (Input Handler)' \
    /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

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 NNTP newsgroup(s).