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
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
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]
Am
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,
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 gpio
um .. help, please ?
how can i make the driver read 1011011 instead of 011011 when i press
Power instead of record on the remote ?
thanks
Morvan Le Meut a écrit :
from cx88-input.c
case CX88_BOARD_ADSTECH_DVB_T_PCI:
ir_codes = ir_codes_adstech_dvb_t_pci;
ir-gpio_addr =
Still rambling about it :)
i was just comparing the instant TV dvb-t pci keymap with what i got
for the instant tv pci :
dvb-t
{ 0x4d, KEY_0 },
{ 0x57, KEY_1 },
{ 0x4f, KEY_2 },
{ 0x53, KEY_3 },
{ 0x56, KEY_4 },
{ 0x4e, KEY_5 },
{ 0x5e, KEY_6 },
{ 0x54, KEY_7 },
{
from cx88-input.c
case CX88_BOARD_ADSTECH_DVB_T_PCI:
ir_codes = ir_codes_adstech_dvb_t_pci;
ir-gpio_addr = MO_GP1_IO;
ir-mask_keycode = 0xbf;
ir-mask_keyup = 0x40;
ir-polling = 50; /* ms */
break;
Morvan Le Meut a écrit :
i can use the remote now ( using devinput in lirc ) but a few quirks
remains :
- dmesg gives a lot of saa7134 IR (ADS Tech Instant TV: unknown key:
key=0x7f raw=0x7f down=1
- in irw most keys are misidentified ( Power as RECORD, Mute as Menu,
Down as DVD and DVD is
i tried to load the saa7134 module with ir_debug=1 and removed all
keycodes in ir-keymaps.c , here is what i got after pressing the buttons
(left to right then going down on the remote ):
(power)
Sep 9 10:43:41 debian kernel: [ 3615.060015] saa7133[0]/ir: build_key
gpio=0x1b mask=0x7f data=27
On Wed, 09 Sep 2009 10:31:46 +0200, Morvan Le Meut mlem...@gmail.com
wrote:
Morvan Le Meut a écrit :
i can use the remote now ( using devinput in lirc ) but a few quirks
remains :
- dmesg gives a lot of saa7134 IR (ADS Tech Instant TV: unknown key:
key=0x7f raw=0x7f down=1
- in irw most
just out of curiosity, what's the difference between
case SAA7134_BOARD_ADS_INSTANT_TV:
dev-has_remote = SAA7134_REMOTE_GPIO;
break;
and
case SAA7134_BOARD_FLYDVBS_LR300:
saa_writeb(SAA7134_GPIO_GPMODE3, 0x80);
saa_writeb(SAA7134_GPIO_GPSTATUS2, 0x40);
Samuel Rakitnican a écrit :
No, this is used for some autodetection routine for different version
of the same card. This has nothing to do with your case.
The key is here, you need to find correct value.
case SAA7134_BOARD_ADS_INSTANT_TV:
ir_codes = AdsInstantTvPci_codes;
I don't know if i mentioned it before but something i find strange is
saa7134 IR (ADS Tech Instant TV: unknown key: key=0x00 raw=0x00 down=1
as soon as the module is loaded.
Morvan Le Meut a écrit :
i did try it ( well, i left the keyup and keydown part and i also
tried it by setting it to
Morvan Le Meut a écrit :
Hello all
This is an old card i bough by error ( wanted the DVB-T version ) but
i tried it and i see a small problem :
The remote isn't supported. ( If it is, i wonder why my computer don't
see it )
I found an old patch to add remote support to it here :
On Tue, 08 Sep 2009 10:25:44 +0200, Morvan Le Meut mlem...@gmail.com
wrote:
Morvan Le Meut a écrit :
Hello all
This is an old card i bough by error ( wanted the DVB-T version ) but i
tried it and i see a small problem :
The remote isn't supported. ( If it is, i wonder why my computer don't
Samuel Rakitnican a écrit :
On Tue, 08 Sep 2009 10:25:44 +0200, Morvan Le Meut mlem...@gmail.com
wrote:
Morvan Le Meut a écrit :
Hello all
This is an old card i bough by error ( wanted the DVB-T version )
but i tried it and i see a small problem :
The remote isn't supported. ( If it is, i
Morvan Le Meut a écrit :
Samuel Rakitnican a écrit :
On Tue, 08 Sep 2009 10:25:44 +0200, Morvan Le Meut
mlem...@gmail.com wrote:
Morvan Le Meut a écrit :
Hello all
This is an old card i bough by error ( wanted the DVB-T version )
but i tried it and i see a small problem :
The remote isn't
Morvan Le Meut a écrit :
Morvan Le Meut a écrit :
Samuel Rakitnican a écrit :
On Tue, 08 Sep 2009 10:25:44 +0200, Morvan Le Meut
mlem...@gmail.com wrote:
Morvan Le Meut a écrit :
Hello all
This is an old card i bough by error ( wanted the DVB-T version )
but i tried it and i see a small
new problem, maybe not related but : i've no sound anymore.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 08 Sep 2009 18:18:05 +0200, Morvan Le Meut mlem...@gmail.com
wrote:
[...]
Since it doesn't work with thoses keycodes, i'm trying it with
ir_codes_adstech_dvb_t_pci. I'm sure it won't work ( it would be toot
easy otherwise ) but since the remote looks the same ...
If by chance it
Morvan Le Meut a écrit :
new problem, maybe not related but : i've no sound anymore.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
eh, for some
22 matches
Mail list logo
