From: Jean Delvare <khali@linux-fr.org>
To: "Paweł Sikora" <pluto@agmk.net>, LMML <linux-media@vger.kernel.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.
Date: Sat, 3 Oct 2009 20:15:27 +0200 [thread overview]
Message-ID: <20091003201527.110b69e3@hyperion.delvare> (raw)
In-Reply-To: <200910031730.45021.pluto@agmk.net>
Hi Pawel,
Please keep the list Cc'd.
On Sat, 3 Oct 2009 17:30:44 +0200, Paweł Sikora wrote:
> On Saturday 03 October 2009 14:04:47 you wrote:
> > OK. So the bug is exactly what I said on my very first reply. And the
> > patch I pointed you to back then should have fixed it:
> > http://patchwork.kernel.org/patch/45707/
> > You said it didn't, which makes me wonder if you really tested it
> > properly...
>
> hmm, it's possible that i've ran system with wrong initrd
> and it had loaded unpatched /lib/modules/$build.
> i've tested patch 45707 today and it works, so my fault.
>
> moreover, with this patch i'm observing a flood in dmesg:
>
> [ 938.313245] i2c IR (Pinnacle PCTV): unknown key: key=0x12 raw=0x12 down=1
> [ 938.419914] i2c IR (Pinnacle PCTV): unknown key: key=0x12 raw=0x12 down=0
> [ 939.273249] i2c IR (Pinnacle PCTV): unknown key: key=0x24 raw=0x24 down=1
> [ 939.379955] i2c IR (Pinnacle PCTV): unknown key: key=0x24 raw=0x24 down=0
Different issue, and I don't know much about IR support, but these keys
aren't listed in ir_codes_pinnacle_color. Maybe you have a different
variant of this remote control with more keys and we need to add their
definitions. Which keys are triggering these messages?
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
next prev parent reply other threads:[~2009-10-03 18:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200909160300.28382.pluto@agmk.net>
2009-09-16 6:57 ` [2.6.31] ir-kbd-i2c oops Jean Delvare
2009-09-16 8:03 ` Paweł Sikora
2009-09-29 14:16 ` Jean Delvare
2009-09-29 23:26 ` Hermann Pitton
2009-09-30 8:16 ` Paweł Sikora
2009-09-30 10:57 ` Jean Delvare
2009-09-30 11:52 ` Paweł Sikora
2009-09-30 12:25 ` Jean Delvare
2009-09-30 16:22 ` Paweł Sikora
2009-09-30 23:52 ` Andy Walls
2009-10-01 11:43 ` Jean Delvare
[not found] ` <200910031208.36524.pluto@agmk.net>
2009-10-03 12:04 ` Jean Delvare
2009-10-03 12:57 ` [PATCH 1/3] gspca_gl860 Olivier Lorin
2009-10-03 13:01 ` [PATCH 2/3] gspca_gl860 Olivier Lorin
2009-10-03 13:03 ` [PATCH 3/3] gspca_gl860 Olivier Lorin
[not found] ` <200910031730.45021.pluto@agmk.net>
2009-10-03 18:15 ` Jean Delvare [this message]
2009-10-03 19:09 ` [2.6.31] ir-kbd-i2c oops Paweł Sikora
2009-10-03 22:52 ` Hermann Pitton
2009-10-04 4:19 ` hermann pitton
2009-10-04 7:08 ` Paweł Sikora
2009-10-04 22:34 ` Hermann Pitton
2009-09-30 23:42 ` Andy Walls
2009-10-01 10:06 ` Jean Delvare
2009-10-01 10:17 ` Paweł Sikora
2009-10-01 10:42 ` Jean Delvare
2009-10-01 10:47 ` Paweł Sikora
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=20091003201527.110b69e3@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-media@vger.kernel.org \
--cc=pluto@agmk.net \
/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