From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: BUG: bttv does not load module ir-kbd-i2c for Hauppauge model 37284, rev B421
Date: Sat, 05 Jan 2013 15:00:18 +0100 [thread overview]
Message-ID: <50E831F2.70400@googlemail.com> (raw)
While we are at it ;) :
[ 15.280772] bttv: Bt8xx card found (0)
[ 15.281349] bttv: 0: Bt878 (rev 17) at 0000:01:08.0, irq: 18,
latency: 32, mmio: 0xfdfff000
[ 15.281386] bttv: 0: detected: Hauppauge WinTV [card=10], PCI
subsystem ID is 0070:13eb
[ 15.281391] bttv: 0: using: Hauppauge (bt878) [card=10,insmod option]
[ 15.283964] bttv: 0: Hauppauge/Voodoo msp34xx: reset line init [5]
[ 15.316043] tveeprom 4-0050: Hauppauge model 37284, rev B421, serial#
5111944
[ 15.316049] tveeprom 4-0050: tuner model is Philips FM1216 (idx 21,
type 5)
[ 15.316054] tveeprom 4-0050: TV standards PAL(B/G) (eeprom 0x04)
[ 15.316059] tveeprom 4-0050: audio processor is MSP3410D (idx 5)
[ 15.316063] tveeprom 4-0050: has radio
[ 15.316066] bttv: 0: Hauppauge eeprom indicates model#37284
[ 15.316071] bttv: 0: tuner type=5
[ 16.178816] bttv: 0: registered device video0
[ 16.179071] bttv: 0: registered device vbi0
[ 16.180587] bttv: 0: registered device radio0
When I load module ir-kbd-i2c manually:
Registered IR keymap rc-hauppauge
input: i2c IR (Hauppauge) as /devices/virtual/rc/rc0/input6
rc0: i2c IR (Hauppauge) as /devices/virtual/rc/rc0
ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-4/4-0018/ir0 [bt878 #0 [sw]]
Remote control works fine then.
Regards,
rank
next reply other threads:[~2013-01-05 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 14:00 Frank Schäfer [this message]
2013-01-05 15:57 ` BUG: bttv does not load module ir-kbd-i2c for Hauppauge model 37284, rev B421 Mauro Carvalho Chehab
2013-01-06 20:36 ` Frank Schäfer
2013-01-07 16:29 ` Mauro Carvalho Chehab
2013-01-08 17:46 ` Frank Schäfer
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=50E831F2.70400@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@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.