From: Sean Young <sean@mess.org>
To: "David Härdeman" <david@hardeman.nu>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 6/6] rc-core: add protocol to EVIOC[GS]KEYCODE_V2 ioctl
Date: Fri, 28 Apr 2017 20:42:13 +0100 [thread overview]
Message-ID: <20170428194212.GA7376@gofer.mess.org> (raw)
In-Reply-To: <20170428165911.axrlw6aic3cqabas@hardeman.nu>
On Fri, Apr 28, 2017 at 06:59:11PM +0200, David Härdeman wrote:
> On Fri, Apr 28, 2017 at 08:31:33AM -0300, Mauro Carvalho Chehab wrote:
> >Em Thu, 27 Apr 2017 22:34:23 +0200
> >David Härdeman <david@hardeman.nu> escreveu:
> ...
> >> This patch changes how the "input_keymap_entry" struct is interpreted
> >> by rc-core by casting it to "rc_keymap_entry":
> >>
> >> struct rc_scancode {
> >> __u16 protocol;
> >> __u16 reserved[3];
> >> __u64 scancode;
> >> }
> >>
> >> struct rc_keymap_entry {
> >> __u8 flags;
> >> __u8 len;
> >> __u16 index;
> >> __u32 keycode;
> >> union {
> >> struct rc_scancode rc;
> >> __u8 raw[32];
> >> };
> >> };
> >>
> ...
> >
> >Nack.
>
> That's not a very constructive approach. If you have a better approach
> in mind I'm all ears. Because you're surely not suggesting that we stay
> with the current protocol-less approach forever?
Well, what problem are we trying to solve actually?
Looking at the keymaps we have already, there are many scancodes which
overlap and only a few of them use a different protocol. So having this
feature will not suddenly make it possible to load all our keymaps, it
will just make it possible to simultaneously load a few more.
> >No userspace breakages are allowed.
>
> That's a gross oversimplification.
This can be implemented without breaking userspace.
Sean
next prev parent reply other threads:[~2017-04-28 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 20:33 [PATCH 0/6] rc-core - protocol in keytables David Härdeman
2017-04-27 20:33 ` [PATCH 1/6] rc-core: fix input repeat handling David Härdeman
2017-04-27 20:34 ` [PATCH 2/6] rc-core: cleanup rc_register_device David Härdeman
2017-05-01 16:49 ` Sean Young
2017-05-01 17:47 ` David Härdeman
2017-05-02 18:53 ` David Härdeman
2017-05-02 20:48 ` Sean Young
2017-05-03 9:49 ` David Härdeman
2017-04-27 20:34 ` [PATCH 3/6] rc-core: cleanup rc_register_device pt2 David Härdeman
2017-04-27 20:34 ` [PATCH 4/6] rc-core: use the full 32 bits for NEC scancodes in wakefilters David Härdeman
2017-04-27 20:34 ` [PATCH 5/6] rc-core: use the full 32 bits for NEC scancodes David Härdeman
2017-04-28 11:58 ` Sean Young
2017-04-28 16:42 ` David Härdeman
2017-04-27 20:34 ` [PATCH 6/6] rc-core: add protocol to EVIOC[GS]KEYCODE_V2 ioctl David Härdeman
2017-04-28 11:31 ` Mauro Carvalho Chehab
2017-04-28 16:59 ` David Härdeman
2017-04-28 19:42 ` Sean Young [this message]
2017-04-29 8:44 ` David Härdeman
2017-06-11 16:17 ` Sean Young
2017-06-17 11:20 ` David Härdeman
2017-04-28 11:40 ` Sean Young
2017-04-28 16:46 ` David Härdeman
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=20170428194212.GA7376@gofer.mess.org \
--to=sean@mess.org \
--cc=david@hardeman.nu \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
/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