Hello Jarod and Devin, as I said previously I don't qualify for driver development nor I'm familiar with design of underlying hardware but anyway I followed some tips from your posts trying to at least bring more information to the discussion. I've made some changes in the saa7134-input.c and saa7134-cards.c files from the latest v4l-dvb tree as per the .diff files attached; also attached is the output of dmesg with debug flags on for the module. Devin has warned the IR is not supported yet but I wanted to at least try to get an input device for it under /proc : I: Bus=0018 Vendor=0000 Product=0000 Version=0000 N: Name="i2c IR (HVR 1150)" P: Phys=i2c-1/1-0071/ir0 S: Sysfs=/devices/virtual/rc/rc0/input4 U: Uniq= H: Handlers=kbd event4 B: EV=100003 B: KEY=100fc312 214a802 0 0 0 0 18000 41a8 4801 9e1680 0 0 10000ffc Of course, it did not worked since the device is probably not a i2c remote as was HVR-1110. That makes me wondering what have changed at the IR level from the HVR-1110 to 1120 and then to 1150 and if the remote control is working for anybody having the 1120 board. I would be glad to make any tests you judge that could be helpful. Regards, Fernando On Thu, Feb 17, 2011 at 12:18 PM, Jarod Wilson <jarod@xxxxxxxxxx> wrote: > On Thu, Feb 17, 2011 at 09:24:27AM -0200, Fernando Laudares Camargos wrote: >> Ok, Devin. >> >> I'm not sure about how it would went but if you think it would be >> worth trying to get info about the components of the 1150 directly >> from Hauppauge, I can give them a call and see what happens. > > I'm pretty sure Devin already has access to all the necessary info about > the components, and contacting someone at Hauppauge would be entirely > redundant... :) > > -- > Jarod Wilson > jarod@xxxxxxxxxx > >
Attachment:
dmesg.out
Description: Binary data
diff -r abd3aac6644e linux/drivers/media/video/saa7134/saa7134-cards.c --- a/linux/drivers/media/video/saa7134/saa7134-cards.c Fri Jul 02 00:38:54 2010 -0300 +++ b/linux/drivers/media/video/saa7134/saa7134-cards.c Thu Mar 03 10:26:52 2011 -0300 @@ -7192,7 +7192,6 @@ saa_writeb (SAA7134_PRODUCTION_TEST_MODE, 0x00); break; - case SAA7134_BOARD_HAUPPAUGE_HVR1150: case SAA7134_BOARD_HAUPPAUGE_HVR1120: /* GPIO 26 high for digital, low for analog */ saa7134_set_gpio(dev, 26, 0); @@ -7208,6 +7207,7 @@ case SAA7134_BOARD_UPMOST_PURPLE_TV: case SAA7134_BOARD_MSI_TVATANYWHERE_PLUS: case SAA7134_BOARD_HAUPPAUGE_HVR1110: + case SAA7134_BOARD_HAUPPAUGE_HVR1150: case SAA7134_BOARD_BEHOLD_607FM_MK3: case SAA7134_BOARD_BEHOLD_607FM_MK5: case SAA7134_BOARD_BEHOLD_609FM_MK3: @@ -7482,6 +7482,7 @@ } break; case SAA7134_BOARD_HAUPPAUGE_HVR1150: + hauppauge_eeprom(dev, dev->eedata+0x80); case SAA7134_BOARD_HAUPPAUGE_HVR1120: hauppauge_eeprom(dev, dev->eedata+0x80); break;
diff -r abd3aac6644e linux/drivers/media/video/saa7134/saa7134-input.c --- a/linux/drivers/media/video/saa7134/saa7134-input.c Fri Jul 02 00:38:54 2010 -0300 +++ b/linux/drivers/media/video/saa7134/saa7134-input.c Thu Mar 03 10:27:02 2011 -0300 @@ -1080,6 +1080,11 @@ dev->init_data.ir_codes = RC_MAP_HAUPPAUGE_NEW; info.addr = 0x71; #endif + case SAA7134_BOARD_HAUPPAUGE_HVR1150: + dev->init_data.name = "HVR 1150"; + dev->init_data.get_key = get_key_hvr1110; + dev->init_data.ir_codes = RC_MAP_HAUPPAUGE_NEW; + info.addr = 0x71; break; case SAA7134_BOARD_BEHOLD_607FM_MK3: case SAA7134_BOARD_BEHOLD_607FM_MK5:
