Hello,
just a little update ( even if nobody seems to be interested :p ) :
I've been using this configuration for a while, and because i tend to
forget to reinstall that patch for each kernel update, i found out some
strange things.
First, very rarely ( it must have happened three times at most
So, if i understand correctly, i should change "in" to 0xBF to get the
missing bit.
( and if it work, i will be able to use ir_codes_adstech_dvb_t_pci
instead of rolling my own keymap )
Thanks.
hermann pitton a écrit :
Hi,
Am Sonntag, den 13.09.2009, 23:59 +0200 schrieb Morvan Le Meut:
j
Hi,
Am Sonntag, den 13.09.2009, 23:59 +0200 schrieb Morvan Le Meut:
> just out of curiosity ( and because google showed me a new trick to try
> ), i tried to load the module with gpio_tracking=1.
> this gave me a new thing in dmesg :
> gpio: mode=0x000 in=0x07f out=0x000 [pre-init]
>
just out of curiosity ( and because google showed me a new trick to try
), i tried to load the module with gpio_tracking=1.
this gave me a new thing in dmesg :
gpio: mode=0x000 in=0x07f out=0x000 [pre-init]
Am i correct by thinkig that the in=0x07f part is the mask ? If it
is tha
Am Samstag, den 12.09.2009, 10:14 +0200 schrieb Morvan Le Meut:
> Since i don't know where to look, i finally decided to use a basic
> incorrect keymap :
> /* ADS Tech Instant TV PCI Remote */
> static struct ir_scancode ir_codes_adstech_pci[] = {
> /* too many repeating codes : incorrect g
Since i don't know where to look, i finally decided to use a basic
incorrect keymap :
/* ADS Tech Instant TV PCI Remote */
static struct ir_scancode ir_codes_adstech_pci[] = {
/* too many repeating codes : incorrect gpio ?. */
{ 0x1f, KEY_MUTE },
{ 0x1d, KEY_SEARCH },
{ 0x17,
