On Tue, 17 Jan 2006, Michael Krufky wrote:
> On 1/17/06, J.O. Aho <trizt@xxxxxxxxx> wrote:
>> I do understand that we don't want to have the same code repeated in may
>> places, as the PVR cards don't use the budget drivers, there is the
>> problem that when loading ir-kbd-i2c (which is needed together with the
>> ivtv drivers) the keytable won't be the right one.
>>
>> So maybe it's better to lift out the keytable to a header, which both
>> drivers can access and use.
>
> That's basically what Ricardo did today. He moved all of the v4l
> keytables from the individual drivers all into ir-keytab.c , and they
> are declared for external use inside ir-common.h .... right now, it
> doesnt look like DVB is using ir-common, but it CAN be made to.
> (would be nice) ... Now that all the v4l keytables are in a single
> file, we can easily prevent duplicates from being created.
Yes, I noticed that when I downloaded the latest CVS version. Something
that I think is a bit strange, is that when using xev to check the keys
(wanted to be sure the new driever managed to give me the right
keymapping), there are quite many that don't generate any results at all
(this made me belive the driver didn't work properly), but when using
lircd with irw the button does generate results
For the hauppauge_new the following keys don't generate anything in xev
KEY_RED
KEY_GREEN
KEY_BLUE
KEY_YELLOW
KEY_CHANNELUP
KEY_CHANNELDOWN
KEY_ZOOM
KEY_SELECT (shouldn't the 0x3b have been mapped to KEY_GO ?)
KEY_RADIO
If thise had generated results, then you could skipp the usage of lircd as
you could have those keyboard shortcuts.
--
//Aho
------------------------------------------------------------------------
E-Mail: trizt@xxxxxxxxx URL: http://www.kotiaho.net/~trizt/
ICQ: 13696780
System: Linux System (PPC7447/1000 AMD K7A/2000)
------------------------------------------------------------------------
EU forbids you to send spam without my permission
------------------------------------------------------------------------
