mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: randmedia@123mail.org
To: Jim Bos <jim876@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to correctly disable LIRC-related MCE*/IR_* modules, to remove ID of RemoteControl as BOTH keyboard & remote?
Date: Wed, 13 Nov 2013 09:12:45 -0800	[thread overview]
Message-ID: <1384362765.13620.47030097.09D237AE@webmail.messagingengine.com> (raw)
In-Reply-To: <5283AE49.6030302@xs4all.nl>

Hi Jim,

On Wed, Nov 13, 2013, at 08:52 AM, Jim Bos wrote:
> Have you looked at this sysfs-file, specifically tried this:
> 
> echo lirc > /sys/class/rc/rc0/protocols

In short, yes.

atm, I've this udev rule,

	cat /etc/udev/rules.d/70-infrared.rules
		ACTION=="add", SUBSYSTEM=="rc",
		RUN+="/usr/bin/ir-keytable --clear --protocol=LIRC
		--write=/etc/rc_keymaps/my_streamzap_rpi"

which ensures after boot

	ir-keytable
	Found /sys/class/rc/rc0/ (/dev/input/event2) with:
	        Driver streamzap, table rc-streamzap
	        Supported protocols: LIRC 
	        Enabled protocols: LIRC 
	        Repeat delay = 500 ms, repeat period = 125 ms

which correlates to

	cat  /sys/class/rc/rc0/protocols 
		[lirc]

i.e., the same effect as the manual intervetion of

	echo lirc > /sys/class/rc/rc0/protocols

nonetheless, that _alone_, does NOT 'do the trick'.  if those MCE*
kernel mods are around, i.e., if I have NOT disabled them in the kernel
(re)compile, or, similarly, use the distro-provided kernel which
compiles the mods by default, then -- at boot -- the Streamzap is
recognized/assigned as an MCE keyboard/remote.

rand

  parent reply	other threads:[~2013-11-13 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 16:31 randmedia
     [not found] ` <5283AE49.6030302@xs4all.nl>
2013-11-13 17:12   ` randmedia [this message]
2013-11-15  3:44     ` randmedia

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=1384362765.13620.47030097.09D237AE@webmail.messagingengine.com \
    --to=randmedia@123mail.org \
    --cc=jim876@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®