[linux-dvb] [PATCH]: Hauppauge Grey Remote support added

Darren Salt linux at youmustbejoking.demon.co.uk
Tue Jan 17 23:16:04 CET 2006

I demand that J.O. Aho may or may not have written...

> On Tue, 17 Jan 2006, Darren Salt wrote:
>> I demand that J.O. Aho may or may not have written...

> English ain't my strong side, for me that statment don't make much sense.

Read (or watch or listen to) "The Hitch-Hiker's Guide to the Galaxy" and
you'll soon understand :-)

> This is partly the same code I last year posted to the linux-kernel
> maillist with the modification of using parm to select the remote type.

I may not have seen that...

>> [snip]
>>>   		name        = "Hauppauge";
>>>   		ir->get_key = get_key_haup;
>>>   		ir_type     = IR_TYPE_RC5;
>>> -		ir_codes    = ir_codes_rc5_tv;
>>> +		/* We have two options here black or grey remote */
>>> +		/*                    J.O. Aho <trizt at iname.com> */
>>> +		if(hauppauge==0) {
>>> +		   /* We use black remote */
>>> +		   ir_codes    = ir_codes_rc5_tv;
>>> +		} else {
>>> +		   /* We use grey remote  */
>>> +		   ir_codes    = ir_codes_rc5_tv_grey;

>> The raw key codes and the comments for that latter mapping happen to
>> exactly match my Nova-T remote control's keys - which, as I've said
>> elsewhere, are a subset of the newer (cx88) Nova-T remote control's keys.

> Didn't know about the nova-t until now, found it after a bit of seaching in
> the v4l/nova-t-usb2.c and yes, it seems to be quite similar, just 11 more
> keys on the nova-t remote.

My Nova-T is the older SAA7146/TDA10045 variety.

>> I'd choose ir_codes_hauppauge_new for this, but that's just me...

> I'm a bit worried about a thing here, I have seen some pages concerning
> lirc configuration that does refer the grey/black remote as the old one and
> on the current photos from hauppauge the remotes shipped nowadays with the
> PVR cards are grey and has 11 extra keys compared with the older models.

Maybe there are three varieties...? That would appear to be consistent with
the keymap in .../ttpci/budget-ci.c, but confusion may have arisen because
other cards which can be driven by budget-ci use different remote controls
and there's only the one mapping in that module.

If anybody has any of those cards and can produce raw mapping data for their
remote controls, that would be *very* useful. PCI ID and subsystem ID would
also be useful; note that mine is 1131:7146, subsystem 13C2:1011.

My recent patch for budget-ci uses ir_codes_hauppauge_new because this
defines a superset of the available keys on the remote control which I have;
those which are present are appropriately mapped. Needless to say, I'm using
this patch :-)

> I guess we need better names for the hauppauge remotes in general, so that
> people will have easier to know which is which, specially if all would
> happen to be using the same driver (don't know anything about the current
> one)

Maybe I should get hold of a newer Nova-T and see if its remote control
generates signals which are accepted by my existing card... :-)

> Older grey remote:
> http://www.kotiaho.net/~trizt/tmpimg/hauppauge-grey.jpg

That looks the same as mine.

> Current grey remote:
> http://www.hauppauge.com/images/pvr250_w_remote.jpg

That's the variety which is included with current Nova-T and Nova-S-Plus
cards (according to their UK site) and, it seems likely, other cards too.

| Darren Salt | d youmustbejoking,demon,co,uk | nr. Ashington,
| Debian,     | s zap,tartarus,org            | Northumberland
| RISC OS     | @                             | Toon Army
|   <URL:http://www.youmustbejoking.demon.co.uk/> (PGP 2.6, GPG keys)

Any given program, when running, is obsolete.

More information about the linux-dvb mailing list