LIRC logic doesn't work properly with Haupaugge transmitters

[Andrew Barbaccia]

When you select the "pvr150" transmitter, the lirc_pvr150 module is loaded.

The lirc_pvr150 module creates a node (/dev/lirc0 for example) which is both a transmitter and a receiver.

If a hauppauge remote is selected, a lircd instance should just be created (and do not load the lirc_i2c driver which conflicts with this one).

Additionally, the hauppauge ir blaster requires a firmware (should be in /lib/firmware) and different configuration files from those currently specified. I can make a tar.gz of configuration files to be used and upload to the bug report if needed.

The logic should be:

If pvr150 blaster is choosen and other remote is to be used, load pvr150 module w new configuration file
If pvr150 blaster is choosen and hauppauge remote is to be used, load pvr150 module once, and do not load lirc_i2c module. Both lirc devices should be told to use /dev/lirc0

[Andrew Barbaccia (andrew-barbaccia)]

Sorry, the above is not too clear.

The lirc0 node that is created represents both the hauppauge remote and the hauppauge blaster.

[Kheops_74 (sang)]

Any news about this bug?

[Mario Limonciello (superm1)]

we're gonna drop pvr-150 support for karmic. this patch won't be making it upstream and it's too much work to maintain it at the ubuntu level.