public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hermann Pitton <hermann-pitton@arcor.de>
To: "Paweł Sikora" <pluto@agmk.net>
Cc: Jean Delvare <khali@linux-fr.org>, LMML <linux-media@vger.kernel.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.
Date: Mon, 05 Oct 2009 00:34:41 +0200	[thread overview]
Message-ID: <1254695681.8731.16.camel@localhost> (raw)
In-Reply-To: <200910040908.05864.pluto@agmk.net>

Hi Pawel,

Am Sonntag, den 04.10.2009, 09:08 +0200 schrieb Paweł Sikora:
> On Sunday 04 October 2009 00:52:18 Hermann Pitton wrote:
> > Hi,
> > 
> > Am Samstag, den 03.10.2009, 21:09 +0200 schrieb Paweł Sikora:
> > > On Saturday 03 October 2009 20:15:27 Jean Delvare wrote:
> > > > > 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.
> > >
> > > i have such one: http://imgbin.org/index.php?page=image&id=812
> > 
> > hm, maybe it is some fake Pinnacle stuff, at least that remote is very
> > different from the supported ones with gray only or colored keys and
> > looks very poor.
> 
> i have pinnacle pctv analog pci 110i:
> 
> http://imgbin.org/index.php?page=image&id=813
> 
> 05:00.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135
>         Video Broadcast Decoder (rev d1)
>         Subsystem: Pinnacle Systems Inc. PCTV 110i (saa7133)                                          
>         Flags: bus master, medium devsel, latency 64, IRQ 16                                          
>         Memory at febff800 (32-bit, non-prefetchable) [size=2K]                                       
>         Capabilities: [40] Power Management version 2                                                 
>         Kernel driver in use: saa7134                                                                 
>         Kernel modules: saa7134
> 
> 05:00.0 0480: 1131:7133 (rev d1)

that does not make much difference.

On recent 310i variants is no response from 0x47 and they must use a
different solution.

Ricardo added support for the remote with the blue arrow buttons on a
110i that time, I tried with others on the new IRQ remote on Asus
devices.

Best information can be found on http://www.bttv-gallery.de

You can also see a PCTV 50i with remote with gray buttons. These two are
supported currently. The 40i is supposed to have no remote support.There
is also a comment about the i2c troubles on the 300i, obviously from
Gerd, and that they are assumed to be caused by a firmware bug.

We can also see your kind of transmitter on other Pinnacle devices and
likely it is already supported there.

Until we would have eeprom detection for different devices with the same
PCI subsystem, a new card entry with dedicated support for that remote
might be a workaround.

Cheers,
Hermann








  reply	other threads:[~2009-10-04 22:35 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                           ` [2.6.31] ir-kbd-i2c oops Jean Delvare
2009-10-03 19:09                             ` 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 [this message]
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=1254695681.8731.16.camel@localhost \
    --to=hermann-pitton@arcor.de \
    --cc=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