[pvrusb2] HD-PVR and IR Blaster

[Mike Isely]

This is getting out of my subject matter area.  Feel free anyone, if you 
think you can contribute here...

The only thing I can point out is related to those i2c_master_recv 
failures.  The error code, -5, is -EIO which is what the pvrusb2 driver 
is going to spit out if the I2C transfer itself simply failed.  That 
sort of thing would happen if perhaps the wrong IR driver were loaded 
(seems not to be the case here) or if the driver were misconfigured, or 
if perhaps there is something going on which is keeping the 
corresponding hardware disabled.

Hmm, thinking along the lines of "hardware disabled" there was a patch 
applied about 1.5 years ago (roughly on 25-Jul-2008 to the standalone 
driver) to "take the IR chip out of reset" during device initialization.  
I wonder if you're running a driver that lacks this fix?...  The first 
standalone driver snapshot to contain this fix was 20080725.  Probably 
any kernel 2.6.27 or later should have this patch as well.

You might also try loading the pvrusb2 driver with i2c_scan=1 and see if 
the IR chip's address (0x71) shows up in the scan.

  -Mike


On Thu, 17 Dec 2009, greg pryzby wrote:

> All ideas are welcome!
> 
> 
> I followed the directions on blushingpenguin and have to be close....
> 
> The lircd.conf is an issue. When I start lirc with the file,
>     (mark/lmark/lircd.conf)
> 
> Dec 17 15:38:16 box lircd-0.8.6[1263]: caught signal
> Dec 17 15:38:18 box lircd-0.8.6[2234]: error in configfile line62:
> Dec 17 15:38:18 box lircd-0.8.6[2234]: "2147549184": must be a valid (lirc_t)
> number
> 
> 
> If I remove all the 'larger codes' then the file loads. When I test w/ irsend
>    irsend SEND_ONCE blaster <CODE_GOES_HERE>
> I get an error:
> 
> Dec 17 16:15:59 box kernel: lirc_zilog: i2c_master_recv failed with -5 -- 
> keeping last read buffer
> Dec 17 16:15:59 box kernel: lirc_zilog: i2c_master_recv failed with -5 -- 
> keeping last read buffer
> Dec 17 16:16:12 box lircd-0.8.6[2479]: caught signal
> 
> 
> 
> It appears to load everything ok
> 
> Dec 17 15:31:41 box kernel: lirc_dev: IR Remote Control driver registered,
> major 249
> Dec 17 15:31:41 box kernel: lirc_zilog: Zilog/Hauppauge IR driver initializing
> Dec 17 15:31:41 box kernel: lirc_zilog: chip found with RX and TX
> Dec 17 15:31:41 box kernel: i2c-adapter i2c-0: lirc_dev: driver lirc_zilog
> registered at minor = 0
> Dec 17 15:31:41 box kernel: Zilog/Hauppauge i2c IR 0-0071: firmware:
> requesting haup-ir-blaster.bin
> Dec 17 15:31:41 box avahi-daemon[1090]: Service "f12-hdpvr-190"
> (/services/ssh.service) successfully established.
> Dec 17 15:31:41 box kernel: lirc_zilog: Zilog/Hauppauge IR blaster firmware
> version 2.1.0 loaded
> Dec 17 15:31:41 box kernel: lirc_zilog: initialization complete
> Dec 17 15:31:42 box lircd-0.8.6[1263]: lircd(default) ready, using
> /var/run/lirc/lircd
> 
> 

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8