LKML Archive on
help / color / mirror / Atom feed
From: Frank Salomon <>
To: Dmitry Torokhov <>
Subject: Re: EV_MSC / driver/input/input.c (Input Handler)
Date: Fri, 09 Feb 2007 08:15:49 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.

> 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.

Best regards, Frank

  reply	other threads:[~2007-02-09  8:22 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 [this message]
2007-02-09 14:36     ` Dmitry Torokhov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: EV_MSC / driver/input/input.c (Input Handler)' \

* 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).