From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "jonsmirl@gmail.com" <jonsmirl@gmail.com>,
Linux Input <linux-input@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, Jarod Wilson <jarod@redhat.com>
Subject: Re: ir-core and default IR maps
Date: Tue, 9 Nov 2010 22:51:33 -0800 [thread overview]
Message-ID: <20101110065133.GA22666@core.coreip.homeip.net> (raw)
In-Reply-To: <4CD920AE.8090406@redhat.com>
On Tue, Nov 09, 2010 at 08:21:34AM -0200, Mauro Carvalho Chehab wrote:
> Em 09-11-2010 04:32, Dmitry Torokhov escreveu:
> > On Mon, Nov 08, 2010 at 12:14:48PM -0200, Mauro Carvalho Chehab wrote:
> >> Em 08-11-2010 11:41, jonsmirl@gmail.com escreveu:
> >>> On Mon, Nov 8, 2010 at 8:34 AM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
> >>>> To achieve plug and play at least one of four choices has to happen:
> >>>
> >>> There is another option, the IR maps get integrated into user space
> >>> keyboard mapping package. This may be possible with the new
> >>> libxkbcommon package.
> >>
> >> That seems interesting.
> >>
> >
> > I disagree here. libxkbcommon provides X interface while applications
> > might want to access evdev nodes directly.
>
> Let me express better: I don't think we should integrate X with the udev tool,
> but, eventually, we could make some X package dependent of v4l-utils. Not sure
> if libxkbdcommon is the better way to do it, as I don't have it installed here
> on my machines.
>
> > If anything, parts of
> > ir-utils dealing with keymap selection should be moved into udev. Maybe
> > we should split utilities that select protocol from the keymap setting
> > and use udev keymap utilities to do the task.
>
> It doesn't make sense to split keymap and protocol selection. Just loading a
> keyboard table but not changing the IR protocol is useless, as the device will
> not be selected. Besides that, the tool that do both is really simple (and, btw,
> it also allows changing the map for a non-RC device, by using one parameter that
> skips the usage of the sysfs nodes at /sys/class/rc):
>
> # ir-keytable -d /dev/input/event4 -r
> scancode 0x0000 = KEY_LEFTCTRL (0x1d)
> Enabled protocols:
OTOH loading keymap and selecting protocol are 2 distinct actions and
udev already has a tool to load keymaps that should also work for all
devices, including remotes.
Basically I do not see the reason for having 2 tools doing pretty much
the same thing.
--
Dmitry
next prev parent reply other threads:[~2010-11-10 6:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 22:08 ir-core and default IR maps jonsmirl
2010-11-07 6:01 ` Dmitry Torokhov
2010-11-07 14:36 ` jonsmirl
2010-11-08 7:23 ` Dmitry Torokhov
2010-11-08 13:09 ` Mauro Carvalho Chehab
2010-11-08 13:34 ` jonsmirl
2010-11-08 13:41 ` jonsmirl
2010-11-08 14:14 ` Mauro Carvalho Chehab
2010-11-09 6:32 ` Dmitry Torokhov
2010-11-09 10:21 ` Mauro Carvalho Chehab
2010-11-10 6:51 ` Dmitry Torokhov [this message]
2010-11-10 13:30 ` Mauro Carvalho Chehab
2010-11-11 1:37 ` Dmitry Torokhov
2010-11-09 12:07 ` jonsmirl
2010-11-08 14:11 ` Mauro Carvalho Chehab
2010-11-08 15:07 ` jonsmirl
2010-11-08 15:38 ` Jarod Wilson
2010-11-08 16:33 ` Mauro Carvalho Chehab
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=20101110065133.GA22666@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jarod@redhat.com \
--cc=jkosina@suse.cz \
--cc=jonsmirl@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mchehab@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.