I think I had left that out before because of some incompatibility with
the corresponding IR driver. However now that you've reported success,
I'll get this patch applied to the driver and made available everywhere.
Thanks!
FYI to everyone here: Even without this change you might still have
working IR if your kernel is 2.6.29 or earlier or you are not using a
v4l-dvb snapshot. This is because I2C driver handling changed at that
point, and the issue found below is an effect from that change.
-Mike
On Fri, 23 Oct 2009, István Váradi wrote:
> Hi,
>
> I have a HVR 1900, and also managed to get the IR receiver (not the IR
> blaster) working. However, I needed this little patch to the
> out-of-kernel driver:
>
> --- pvrusb2-mci-20091011/driver/pvrusb2-i2c-core.c.orig 2009-09-14
> 06:00:56.000000000 +0200
> +++ pvrusb2-mci-20091011/driver/pvrusb2-i2c-core.c 2009-10-19
> 19:21:48.000000000 +0200
> @@ -57,6 +57,7 @@
>
> /* Mapping of IR schemes to known I2C addresses - if any */
> static const unsigned char ir_video_addresses[] = {
> + [PVR2_IR_SCHEME_ZILOG] = 0x71,
> [PVR2_IR_SCHEME_29XXX] = 0x18,
> [PVR2_IR_SCHEME_24XXX] = 0x18,
> };
>
> With this patch I need lirc_dev and lirc_i2c when LIRC is configured
> with the "hauppauge" driver. lirc_i2c then prints that my hardware is
> a HVR-1300, but otherwise thr LIRC daemon works with the same
> configuration that I used for a PVR150.
>
> Istvan
>
> On Mon, Oct 12, 2009 at 17:14, Nicholas Robbins <[email protected]> wrote:
> >
> >
> >
> >> > --- On Sun, 10/11/09, Mike Isely <[email protected]>
> >> wrote:
> >> >
> >> Yeah, that's what I wanted to see. Thanks.
> >>
> >>
> >> >
> >> > also, seems like I may have some rebooting issues, the
> >> soft boot
> >> > seemed ok, but a hard reboot might have things a
> >> little foobared.
> >>
> >> Can you be a little more specific? Hard reboot of the
> >> host? Power
> >> cycle the device?
> >>
> >> -Mike
> >
> >
> > Hard rebooting the host left the system in the following state: The other
> > two tuners (one USB, on miniPCI) took a while (~2 minutes) before udev
> > could sort them out. The system ignored usb keyboard input, and ssh
> > sessions were hanging after about a minute.
> >
> > Again, a soft reboot fixed the problems.
> >
> >
> >
> > _______________________________________________
> > pvrusb2 mailing list
> > [email protected]
> > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> >
> _______________________________________________
> pvrusb2 mailing list
> [email protected]
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> _______________________________________________
pvrusb2 mailing list
[email protected]
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
