Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up.
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 until now
), the remotes keys tends to be misidentified as keyboards keys
shortcuts : volume up seems to like to be identified as search files
in Gnome.
Second, the stability of the whole OS seems to suffer from my hack.I'm
not very certain about that since my computer have a tendency to hangs
when playing a video with the proprietary Nvidia driver and flash
loaded, but my computer tend to shut down all on its own ( like pressing
the power button for more than 3 secs ) only when i enable the remote
support. It take a while ( maybe a day or two ), and i've see it happen
only once ( but it happened at least one other time while i was away
from the computer, it could have been a power grid failure )
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, KEY_EPG },/* Guide */
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x0, KEY_VIDEO },
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
};
struct ir_scancode_table ir_codes_adstech_pci_table = {
.scan = ir_codes_adstech_pci,
.size = ARRAY_SIZE(ir_codes_adstech_pci),
};
EXPORT_SYMBOL_GPL(ir_codes_adstech_pci_table);
No numbers in favor of arrows and ch+/- Vol+/- . Well 246 will be arrows
and 5 select, 7 and 8 are undefined, 9 become vol-, 1 epg and 3 is tuner.
If someone, one day, wants to find that missig bit, i'll be happy to
help. ( Strange anyway : it's as if there was a 0x7f mask even when i
specify a 0xff one )
Feel free to write a patch.
Morvan Le Meut a écrit :
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
--
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
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up.
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 that then i am a problem : i did specify it as 0xff. Did i miss
something ?
hermann pitton a écrit :
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 ?. */
{ 0x1f, KEY_MUTE },
{ 0x1d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x0, KEY_VIDEO },
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
};
struct ir_scancode_table ir_codes_adstech_pci_table = {
.scan = ir_codes_adstech_pci,
.size = ARRAY_SIZE(ir_codes_adstech_pci),
};
EXPORT_SYMBOL_GPL(ir_codes_adstech_pci_table);
No numbers in favor of arrows and ch+/- Vol+/- . Well 246 will be arrows
and 5 select, 7 and 8 are undefined, 9 become vol-, 1 epg and 3 is tuner.
If someone, one day, wants to find that missig bit, i'll be happy to
help. ( Strange anyway : it's as if there was a 0x7f mask even when i
specify a 0xff one )
Feel free to write a patch.
Morvan Le Meut a écrit :
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,
I still have a huge mail backlash and are not in details what you may
have tried already, but if you have a missing/unknown gpio on such a
remote, you start to test for that one with mask_keycode = 0x0 in
saa7134-input.c and if it is then found, you do add it to that mask.
If that doesn't help, it might be something special.
Cheers,
Hermann
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up.
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 i correct by thinkig that the in=0x07f part is the mask ? If it
is that then i am a problem : i did specify it as 0xff. Did i miss
something ?
it does not cover the IR gpio settings, but what happens in the card
entry at saa7134-cards.c.
mode is the gpio mask defined there, if any. You have nothing set
there.
in is the actual configuration of the gpio pins. This can reflect
changes made to them, for example from using an other cards entry
previously, which can change some pins or changes in different modes on
them, which are not yet reset. By default it shows the manufacturers
gpio configuration. 0x7f can mean that the first seven pins (0-6) are
used for the gpio remote. That would be your mask keycode then.
out is what the driver writes to the gpios of that card.
In this mode only pins are changed, which are high in the mask,
this is called masked writes. In your case nothing happens.
See my next mail for a simple example of changing the single gpio21 pin
to 0 in Television mode.
Cheers,
Hermann
hermann pitton a écrit :
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 ?. */
{ 0x1f, KEY_MUTE },
{ 0x1d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x0, KEY_VIDEO },
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
};
struct ir_scancode_table ir_codes_adstech_pci_table = {
.scan = ir_codes_adstech_pci,
.size = ARRAY_SIZE(ir_codes_adstech_pci),
};
EXPORT_SYMBOL_GPL(ir_codes_adstech_pci_table);
No numbers in favor of arrows and ch+/- Vol+/- . Well 246 will be arrows
and 5 select, 7 and 8 are undefined, 9 become vol-, 1 epg and 3 is tuner.
If someone, one day, wants to find that missig bit, i'll be happy to
help. ( Strange anyway : it's as if there was a 0x7f mask even when i
specify a 0xff one )
Feel free to write a patch.
Morvan Le Meut a écrit :
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,
I still have a huge mail backlash and are not in details what you may
have tried already, but if you have a missing/unknown gpio on such a
remote, you start to test for that one with mask_keycode = 0x0 in
saa7134-input.c and if it is then found, you do add it to that mask.
If that doesn't help, it might be something special.
Cheers,
Hermann
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up.
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, KEY_EPG },/* Guide */
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x0, KEY_VIDEO },
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
};
struct ir_scancode_table ir_codes_adstech_pci_table = {
.scan = ir_codes_adstech_pci,
.size = ARRAY_SIZE(ir_codes_adstech_pci),
};
EXPORT_SYMBOL_GPL(ir_codes_adstech_pci_table);
No numbers in favor of arrows and ch+/- Vol+/- . Well 246 will be arrows
and 5 select, 7 and 8 are undefined, 9 become vol-, 1 epg and 3 is tuner.
If someone, one day, wants to find that missig bit, i'll be happy to
help. ( Strange anyway : it's as if there was a 0x7f mask even when i
specify a 0xff one )
Feel free to write a patch.
Morvan Le Meut a écrit :
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
--
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
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, giving up.
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 ?. */
{ 0x1f, KEY_MUTE },
{ 0x1d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x0, KEY_VIDEO },
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
};
struct ir_scancode_table ir_codes_adstech_pci_table = {
.scan = ir_codes_adstech_pci,
.size = ARRAY_SIZE(ir_codes_adstech_pci),
};
EXPORT_SYMBOL_GPL(ir_codes_adstech_pci_table);
No numbers in favor of arrows and ch+/- Vol+/- . Well 246 will be arrows
and 5 select, 7 and 8 are undefined, 9 become vol-, 1 epg and 3 is tuner.
If someone, one day, wants to find that missig bit, i'll be happy to
help. ( Strange anyway : it's as if there was a 0x7f mask even when i
specify a 0xff one )
Feel free to write a patch.
Morvan Le Meut a écrit :
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,
I still have a huge mail backlash and are not in details what you may
have tried already, but if you have a missing/unknown gpio on such a
remote, you start to test for that one with mask_keycode = 0x0 in
saa7134-input.c and if it is then found, you do add it to that mask.
If that doesn't help, it might be something special.
Cheers,
Hermann
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, no idea what to try.
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 = MO_GP1_IO; ir-mask_keycode = 0xbf; ir-mask_keyup = 0x40; ir-polling = 50; /* ms */ break; I'm not sure how much of the adstech instant tv dvb-t pci can be copied for the non dvb-t one but could the solution be something along the lines of that ir-gpio_addr thing ? or is that specific to the cx88 driver ? -- 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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 },
{ 0x4c, KEY_8 },
{ 0x5c, KEY_9 },
pci
{ 0xd, KEY_0 },
{ 0x17, KEY_1 },
{ 0xf, KEY_2 },
{ 0x13, KEY_3 },
{ 0x16, KEY_4 },
{ 0xe, KEY_5 },
{ 0x1e, KEY_6 },
{ 0x14, KEY_7 },
{ 0xc, KEY_8 },
{ 0x1c, KEY_9 },
if manufacturers are half as lazy as i am, and since the remote is the
same ( or at least looks the same ), it looks like i am indeed missing
part of the gpio. ( no mark, got the output with ir_debug=1 )
now for the rest of the keys :
dvb-t
{ 0x5b, KEY_POWER },
{ 0x5f, KEY_MUTE },
{ 0x55, KEY_GOTO },
{ 0x5d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x1f, KEY_MENU },
{ 0x0f, KEY_UP },
{ 0x46, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x5a, KEY_INFO },
{ 0x52, KEY_EXIT },
{ 0x59, KEY_PREVIOUS },
{ 0x51, KEY_NEXT },
{ 0x58, KEY_REWIND },
{ 0x50, KEY_FORWARD },
{ 0x44, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x12, KEY_B },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x00, KEY_PROG3 },/* 3 */
{ 0x06, KEY_DVD },
{ 0x48, KEY_AUX },/* Photo */
{ 0x40, KEY_VIDEO },
{ 0x19, KEY_AUDIO },/* Music */
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
pci
{ 0x1b, KEY_POWER },
{ 0x1f, KEY_MUTE },
{ 0x15, KEY_GOTO },
{ 0x1d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x1f, KEY_MENU },
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x12, KEY_B },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x00, KEY_PROG3 },/* 3 */
{ 0x06, KEY_DVD },
{ 0x8, KEY_AUX },/* Photo */
{ 0x0, KEY_VIDEO },
{ 0x19, KEY_AUDIO },/* Music */
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
as you can see, for most of the keycodes, i am missing 0x40, which mean
i am missing one bit.
And i don't even know where i should start looking to solve that problem.
thanks for any help/solution.
Morvan Le Meut a écrit :
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.
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support, no idea what to try.
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;
I'm not sure how much of the adstech instant tv dvb-t pci can be copied
for the non dvb-t one but could the solution be something along the
lines of that ir-gpio_addr thing ? or is that specific to the cx88
driver ?
Morvan Le Meut a écrit :
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 },
{ 0x4c, KEY_8 },
{ 0x5c, KEY_9 },
pci
{ 0xd, KEY_0 },
{ 0x17, KEY_1 },
{ 0xf, KEY_2 },
{ 0x13, KEY_3 },
{ 0x16, KEY_4 },
{ 0xe, KEY_5 },
{ 0x1e, KEY_6 },
{ 0x14, KEY_7 },
{ 0xc, KEY_8 },
{ 0x1c, KEY_9 },
if manufacturers are half as lazy as i am, and since the remote is the
same ( or at least looks the same ), it looks like i am indeed missing
part of the gpio. ( no mark, got the output with ir_debug=1 )
now for the rest of the keys :
dvb-t
{ 0x5b, KEY_POWER },
{ 0x5f, KEY_MUTE },
{ 0x55, KEY_GOTO },
{ 0x5d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x1f, KEY_MENU },
{ 0x0f, KEY_UP },
{ 0x46, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x5a, KEY_INFO },
{ 0x52, KEY_EXIT },
{ 0x59, KEY_PREVIOUS },
{ 0x51, KEY_NEXT },
{ 0x58, KEY_REWIND },
{ 0x50, KEY_FORWARD },
{ 0x44, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x12, KEY_B },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x00, KEY_PROG3 },/* 3 */
{ 0x06, KEY_DVD },
{ 0x48, KEY_AUX },/* Photo */
{ 0x40, KEY_VIDEO },
{ 0x19, KEY_AUDIO },/* Music */
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
pci
{ 0x1b, KEY_POWER },
{ 0x1f, KEY_MUTE },
{ 0x15, KEY_GOTO },
{ 0x1d, KEY_SEARCH },
{ 0x17, KEY_EPG },/* Guide */
{ 0x1f, KEY_MENU },
{ 0x0f, KEY_UP },
{ 0x6, KEY_DOWN },
{ 0x16, KEY_LEFT },
{ 0x1e, KEY_RIGHT },
{ 0x0e, KEY_SELECT },/* Enter */
{ 0x1a, KEY_INFO },
{ 0x12, KEY_EXIT },
{ 0x19, KEY_PREVIOUS },
{ 0x11, KEY_NEXT },
{ 0x18, KEY_REWIND },
{ 0x10, KEY_FORWARD },
{ 0x4, KEY_PLAYPAUSE },
{ 0x07, KEY_STOP },
{ 0x1b, KEY_RECORD },
{ 0x13, KEY_TUNER },/* Live */
{ 0x0a, KEY_A },
{ 0x12, KEY_B },
{ 0x03, KEY_PROG1 },/* 1 */
{ 0x01, KEY_PROG2 },/* 2 */
{ 0x00, KEY_PROG3 },/* 3 */
{ 0x06, KEY_DVD },
{ 0x8, KEY_AUX },/* Photo */
{ 0x0, KEY_VIDEO },
{ 0x19, KEY_AUDIO },/* Music */
{ 0x0b, KEY_CHANNELUP },
{ 0x08, KEY_CHANNELDOWN },
{ 0x15, KEY_VOLUMEUP },
{ 0x1c, KEY_VOLUMEDOWN },
as you can see, for most of the keycodes, i am missing 0x40, which
mean i am missing one bit.
And i don't even know where i should start looking to solve that problem.
thanks for any help/solution.
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 correctly identified ) i guess using ir_codes_adstech_dvb_t_pci was not such a bright idea after all :p ( i included a full dmesg output ) For now, it is enough work on my part, i'll try to correct those keycodes later. It is amazing what you can do even when you don't understand most of it :D . Working on it, but i don't think everything is correct : some totaly unrelated keys have the same keycode. For example Jump and Volume+ or Search and Volume-. Beside, i keep getting Sep 9 10:17:16 debian kernel: [ 2029.892014] saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=0 Sep 9 10:17:16 debian kernel: [ 2029.944029] saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=1 for each recognized keypress I'll need a lot of help there : i don't know what to do. -- 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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 Sep 9 10:43:41 debian kernel: [ 3615.112017] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (mute) Sep 9 10:43:44 debian kernel: [ 3618.440021] saa7133[0]/ir: build_key gpio=0x1f mask=0x7f data=31 Sep 9 10:43:44 debian kernel: [ 3618.492019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (1) Sep 9 10:50:42 debian kernel: [ 4036.796017] saa7133[0]/ir: build_key gpio=0x17 mask=0x7f data=23 Sep 9 10:50:43 debian kernel: [ 4036.900019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (2) Sep 9 10:51:14 debian kernel: [ 4068.776014] saa7133[0]/ir: build_key gpio=0xf mask=0x7f data=15 Sep 9 10:51:14 debian kernel: [ 4068.828017] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (3) Sep 9 10:51:36 debian kernel: [ 4090.408016] saa7133[0]/ir: build_key gpio=0x13 mask=0x7f data=19 Sep 9 10:51:36 debian kernel: [ 4090.460020] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (4) Sep 9 10:51:47 debian kernel: [ 4101.380016] saa7133[0]/ir: build_key gpio=0x16 mask=0x7f data=22 Sep 9 10:51:47 debian kernel: [ 4101.432019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (5) Sep 9 10:52:00 debian kernel: [ 4114.068019] saa7133[0]/ir: build_key gpio=0xe mask=0x7f data=14 Sep 9 10:52:00 debian kernel: [ 4114.120020] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (6) Sep 9 10:52:15 debian kernel: [ 4129.672020] saa7133[0]/ir: build_key gpio=0x1e mask=0x7f data=30 Sep 9 10:52:15 debian kernel: [ 4129.776019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (7) Sep 9 10:52:34 debian kernel: [ 4148.132020] saa7133[0]/ir: build_key gpio=0x14 mask=0x7f data=20 Sep 9 10:52:34 debian kernel: [ 4148.236020] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (8) Sep 9 10:52:49 debian kernel: [ 4163.160020] saa7133[0]/ir: build_key gpio=0xc mask=0x7f data=12 Sep 9 10:52:49 debian kernel: [ 4163.212022] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (9) Sep 9 10:53:02 debian kernel: [ 4176.056016] saa7133[0]/ir: build_key gpio=0x1c mask=0x7f data=28 Sep 9 10:53:02 debian kernel: [ 4176.108017] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (jump) Sep 9 10:48:56 debian kernel: [ 3930.144021] saa7133[0]/ir: build_key gpio=0x15 mask=0x7f data=21 Sep 9 10:48:56 debian kernel: [ 3930.196019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (0) Sep 9 10:56:55 debian kernel: [ 4409.016020] saa7133[0]/ir: build_key gpio=0xd mask=0x7f data=13 Sep 9 10:56:55 debian kernel: [ 4409.068023] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (search) Sep 9 10:57:05 debian kernel: [ 4419.520021] saa7133[0]/ir: build_key gpio=0x1d mask=0x7f data=29 Sep 9 10:57:05 debian kernel: [ 4419.624019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (guide) Sep 9 10:57:14 debian kernel: [ 4428.568017] saa7133[0]/ir: build_key gpio=0x17 mask=0x7f data=23 Sep 9 10:57:14 debian kernel: [ 4428.620017] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (up arrow) Sep 9 10:57:20 debian kernel: [ 4434.236015] saa7133[0]/ir: build_key gpio=0xf mask=0x7f data=15 Sep 9 10:57:20 debian kernel: [ 4434.340019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (menu) Sep 9 10:57:29 debian kernel: [ 4443.180017] saa7133[0]/ir: build_key gpio=0x1f mask=0x7f data=31 Sep 9 10:57:29 debian kernel: [ 4443.232019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (left arrow) Sep 9 10:57:41 debian kernel: [ 4455.504014] saa7133[0]/ir: build_key gpio=0x16 mask=0x7f data=22 Sep 9 10:57:41 debian kernel: [ 4455.556015] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (enter) Sep 9 10:57:50 debian kernel: [ 4464.604018] saa7133[0]/ir: build_key gpio=0xe mask=0x7f data=14 Sep 9 10:57:50 debian kernel: [ 4464.656017] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (right arrow) Sep 9 10:58:02 debian kernel: [ 4476.668018] saa7133[0]/ir: build_key gpio=0x1e mask=0x7f data=30 Sep 9 10:58:02 debian kernel: [ 4476.772019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (info) Sep 9 10:58:12 debian kernel: [ 4485.976016] saa7133[0]/ir: build_key gpio=0x1a mask=0x7f data=26 Sep 9 10:58:12 debian kernel: [ 4486.028018] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (down arrow) Sep 9 10:58:21 debian kernel: [ 4494.920015] saa7133[0]/ir: build_key gpio=0x6 mask=0x7f data=6 Sep 9 10:58:21 debian kernel: [ 4495.024019] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127 (exit) Sep 9 10:58:30 debian kernel: [ 4504.332020] saa7133[0]/ir: build_key gpio=0x12 mask=0x7f data=18 Sep 9 10:58:30 debian kernel: [ 4504.384020] saa7133[0]/ir: build_key gpio=0x7f mask=0x7f data=127
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 keys are misidentified ( Power as RECORD, Mute as Menu, Down as DVD and DVD is correctly identified ) i guess using ir_codes_adstech_dvb_t_pci was not such a bright idea after all :p ( i included a full dmesg output ) For now, it is enough work on my part, i'll try to correct those keycodes later. It is amazing what you can do even when you don't understand most of it :D . Working on it, but i don't think everything is correct : some totaly unrelated keys have the same keycode. For example Jump and Volume+ or Search and Volume-. Beside, i keep getting Sep 9 10:17:16 debian kernel: [ 2029.892014] saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=0 Sep 9 10:17:16 debian kernel: [ 2029.944029] saa7134 IR (ADS Tech Instant TV: unknown key: key=0x7f raw=0x7f down=1 for each recognized keypress I'll need a lot of help there : i don't know what to do. I think that correct gpio mask in saa7134-input.c would give unique keycodes for every keypress. It's most likely that you need to invent new gpio mask, but I'm not sure about this: (http://linuxtv.org/wiki/index.php/Remote_controllers-V4L#How_to_add_remote_control_support_to_a_card_.28GPIO_remotes.29) I'm sorry that I can't help you any further, it's getting far beyond my knowledge. I'm leaving this to somebody else... -- 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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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); dev-has_remote = SAA7134_REMOTE_GPIO; break; ? could it be that the repeating keys come from not using that saa_writeb thing ? Morvan Le Meut a écrit : wait, from that webpage, the gpio would be different for each key, independently from the mask, so my previous attempt with ir_debug=1 means that the gpio itself is read incorrectly .. :( -- 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 -- 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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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; // This remote seems to return 0x7f after each button is pushed. // No button may be repeated ; no release message. Only 1 msg with // raw data = button idx, followed by one message with raw data = 0x7f mask_keycode = 0xff; mask_keyup = 0xff; mask_keydown = 0xff; polling = 50; // ms break; Have you tried to follow the tutorial on the web?, By tutorial you need to modify with something like this: case SAA7134_BOARD_ADS_INSTANT_TV: ir_codes = AdsInstantTvPci_codes; mask_keycode = 0; polling = 50; // ms break; And then try to find correct gpio masks. i did try it ( well, i left the keyup and keydown part and i also tried it by setting it to 0 ) but the gpio still repeat (saa7133[0]/ir: build_key gpio=0x1b mask=0x0 data=0 for Power and Record, each followed by gpio=7f ). Which is why i believe i am missing part of that code ( got the dvb-t version too on another computer, and given the software used, there should be no duplicate keys ). I guess i will have to wait for someone to solve the problem. I can at least use the remote in a broken way. -- 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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 0 ) but the gpio still repeat (saa7133[0]/ir: build_key gpio=0x1b mask=0x0 data=0 for Power and Record, each followed by gpio=7f ). Which is why i believe i am missing part of that code ( got the dvb-t version too on another computer, and given the software used, there should be no duplicate keys ). I guess i will have to wait for someone to solve the problem. I can at least use the remote in a broken way. -- 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 -- 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
(Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 :
http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/saa7134_patch_for_AdsInstantTVPCI.gz
( The webpage talking about it is
http://tfpsly.free.fr/francais/index.html?url=http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/index.html
in french )
But since i found out long ago that i shouldn't even think of altering
a source file, could someone adapt that old patch to correct this ? (
should be quick, i guess )
Thanks.
--
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
Well, i'm trying it myself ( by hand, since the patch looks old ) :
adding
case SAA7134_BOARD_ADS_INSTANT_TV: at line 6659 in saa7134-cards.c
(before dev-has_remote = SAA7134_REMOTE_GPIO; )
is that correct ?
but from the diff file i should add what seems to be the remote keycode
in saa7134-input.c
+static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
+// Buttons are in the top to bottom physical order
+// Some buttons return the same raw code, so they are currently
disabled
+[ 127] = KEY_FINANCE, // release all keys code - prevent
repeating enlessly a key
+
+[ 27 ] = KEY_POWER,
( and so on )
Since i didn't see other keycodes for the other cards, i guess this is
wrong, so where should i add them ?
( i barely understand what i am doing right now :p )
Thanks
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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
see it )
I found an old patch to add remote support to it here :
http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/saa7134_patch_for_AdsInstantTVPCI.gz
( The webpage talking about it is
http://tfpsly.free.fr/francais/index.html?url=http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/index.html
in french )
But since i found out long ago that i shouldn't even think of altering
a source file, could someone adapt that old patch to correct this ? (
should be quick, i guess )
Thanks.
-- 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
Well, i'm trying it myself ( by hand, since the patch looks old ) :
adding
case SAA7134_BOARD_ADS_INSTANT_TV: at line 6659 in saa7134-cards.c
(before dev-has_remote = SAA7134_REMOTE_GPIO; )
is that correct ?
but from the diff file i should add what seems to be the remote keycode
in saa7134-input.c
+static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
+// Buttons are in the top to bottom physical order
+// Some buttons return the same raw code, so they are currently
disabled
+[ 127] = KEY_FINANCE, // release all keys code - prevent
repeating enlessly a key
+ +[ 27 ] = KEY_POWER,
( and so on )
Since i didn't see other keycodes for the other cards, i guess this is
wrong, so where should i add them ?
( i barely understand what i am doing right now :p )
Thanks
Hi Morvan,
I'm not a developer, however I've done someting similar in the past...
This keycodes looks pretty strange to me, but then again I'm not a
developer.
Just add it by hand and compile it, and install it.
After successful load of all new modules, you should get some response in
terminal, or in dmesg output like Unknown key... if keymap table is
wrong by pressing buttons on remote. If this gpio's are correct:
+ mask_keycode = 0xff;
+ mask_keyup = 0xff;
+ mask_keydown = 0xff;
+ polling = 50; // ms
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 wonder why my computer
don't see it )
I found an old patch to add remote support to it here :
http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/saa7134_patch_for_AdsInstantTVPCI.gz
( The webpage talking about it is
http://tfpsly.free.fr/francais/index.html?url=http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/index.html
in french )
But since i found out long ago that i shouldn't even think of
altering a source file, could someone adapt that old patch to
correct this ? ( should be quick, i guess )
Thanks.
-- 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
Well, i'm trying it myself ( by hand, since the patch looks old ) :
adding
case SAA7134_BOARD_ADS_INSTANT_TV: at line 6659 in saa7134-cards.c
(before dev-has_remote = SAA7134_REMOTE_GPIO; )
is that correct ?
but from the diff file i should add what seems to be the remote
keycode in saa7134-input.c
+static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
+// Buttons are in the top to bottom physical order
+// Some buttons return the same raw code, so they are currently
disabled
+[ 127] = KEY_FINANCE, // release all keys code - prevent
repeating enlessly a key
+ +[ 27 ] = KEY_POWER,
( and so on )
Since i didn't see other keycodes for the other cards, i guess this
is wrong, so where should i add them ?
( i barely understand what i am doing right now :p )
Thanks
Hi Morvan,
I'm not a developer, however I've done someting similar in the past...
This keycodes looks pretty strange to me, but then again I'm not a
developer.
Just add it by hand and compile it, and install it.
After successful load of all new modules, you should get some response
in terminal, or in dmesg output like Unknown key... if keymap table
is wrong by pressing buttons on remote. If this gpio's are correct:
+mask_keycode = 0xff;
+mask_keyup = 0xff;
+mask_keydown = 0xff;
+polling = 50; // ms
Still working on it, i found out where thoses keycodes should go :
ir-keymaps.c
i'm not a developer either, but i tried to learn C a few years ago
so i'm not completly lost, i just can't understand what all that code is
doing ...
But it is strange that such an old card had this lack of remote support
go unnoticed.
( I really have no luck when it come to TV cards : first, my PC Basic
EC168 card ( tnt usb basic v5 ) doesn't work where it should, then my
HVR-1120 works but not with mythtv and now the remote i wanted to use
isn't supported :D )
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 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 :
http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/saa7134_patch_for_AdsInstantTVPCI.gz
( The webpage talking about it is
http://tfpsly.free.fr/francais/index.html?url=http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/index.html
in french )
But since i found out long ago that i shouldn't even think of
altering a source file, could someone adapt that old patch to
correct this ? ( should be quick, i guess )
Thanks.
-- 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
Well, i'm trying it myself ( by hand, since the patch looks old ) :
adding
case SAA7134_BOARD_ADS_INSTANT_TV: at line 6659 in saa7134-cards.c
(before dev-has_remote = SAA7134_REMOTE_GPIO; )
is that correct ?
but from the diff file i should add what seems to be the remote
keycode in saa7134-input.c
+static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
+// Buttons are in the top to bottom physical order
+// Some buttons return the same raw code, so they are currently
disabled
+[ 127] = KEY_FINANCE, // release all keys code - prevent
repeating enlessly a key
+ +[ 27 ] = KEY_POWER,
( and so on )
Since i didn't see other keycodes for the other cards, i guess this
is wrong, so where should i add them ?
( i barely understand what i am doing right now :p )
Thanks
Hi Morvan,
I'm not a developer, however I've done someting similar in the past...
This keycodes looks pretty strange to me, but then again I'm not a
developer.
Just add it by hand and compile it, and install it.
After successful load of all new modules, you should get some
response in terminal, or in dmesg output like Unknown key... if
keymap table is wrong by pressing buttons on remote. If this gpio's
are correct:
+mask_keycode = 0xff;
+mask_keyup = 0xff;
+mask_keydown = 0xff;
+polling = 50; // ms
Still working on it, i found out where thoses keycodes should go :
ir-keymaps.c
i'm not a developer either, but i tried to learn C a few years ago
so i'm not completly lost, i just can't understand what all that code
is doing ...
But it is strange that such an old card had this lack of remote
support go unnoticed.
( I really have no luck when it come to TV cards : first, my PC Basic
EC168 card ( tnt usb basic v5 ) doesn't work where it should, then my
HVR-1120 works but not with mythtv and now the remote i wanted to use
isn't supported :D )
--
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
/home/momo/TNT/v4l-dvb/v4l/saa7134-input.c: In function
'saa7134_input_init1':
/home/momo/TNT/v4l-dvb/v4l/saa7134-input.c:655: error:
'AdsInstantTvPci_codes' undeclared (first use in this function)
guess i missed something, i'll have to wait for someone to correct it :)
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 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 :
http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/saa7134_patch_for_AdsInstantTVPCI.gz
( The webpage talking about it is
http://tfpsly.free.fr/francais/index.html?url=http://tfpsly.free.fr/Files/Instant_TV_PCI_remote/index.html
in french )
But since i found out long ago that i shouldn't even think of
altering a source file, could someone adapt that old patch to
correct this ? ( should be quick, i guess )
Thanks.
-- 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
Well, i'm trying it myself ( by hand, since the patch looks old ) :
adding
case SAA7134_BOARD_ADS_INSTANT_TV: at line 6659 in saa7134-cards.c
(before dev-has_remote = SAA7134_REMOTE_GPIO; )
is that correct ?
but from the diff file i should add what seems to be the remote
keycode in saa7134-input.c
+static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
+// Buttons are in the top to bottom physical order
+// Some buttons return the same raw code, so they are
currently disabled
+[ 127] = KEY_FINANCE, // release all keys code - prevent
repeating enlessly a key
+ +[ 27 ] = KEY_POWER,
( and so on )
Since i didn't see other keycodes for the other cards, i guess
this is wrong, so where should i add them ?
( i barely understand what i am doing right now :p )
Thanks
Hi Morvan,
I'm not a developer, however I've done someting similar in the past...
This keycodes looks pretty strange to me, but then again I'm not a
developer.
Just add it by hand and compile it, and install it.
After successful load of all new modules, you should get some
response in terminal, or in dmesg output like Unknown key... if
keymap table is wrong by pressing buttons on remote. If this gpio's
are correct:
+mask_keycode = 0xff;
+mask_keyup = 0xff;
+mask_keydown = 0xff;
+polling = 50; // ms
Still working on it, i found out where thoses keycodes should go :
ir-keymaps.c
i'm not a developer either, but i tried to learn C a few years ago
so i'm not completly lost, i just can't understand what all that code
is doing ...
But it is strange that such an old card had this lack of remote
support go unnoticed.
( I really have no luck when it come to TV cards : first, my PC Basic
EC168 card ( tnt usb basic v5 ) doesn't work where it should, then my
HVR-1120 works but not with mythtv and now the remote i wanted to use
isn't supported :D )
--
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
/home/momo/TNT/v4l-dvb/v4l/saa7134-input.c: In function
'saa7134_input_init1':
/home/momo/TNT/v4l-dvb/v4l/saa7134-input.c:655: error:
'AdsInstantTvPci_codes' undeclared (first use in this function)
guess i missed something, i'll have to wait for someone to correct it :)
--
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
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 :D ) but since the remote looks the same ...
If by chance it work, i'll try to better document what i did for someone
to write a patch. ( Or at least, to serve as a reminder the next time
i'll encounter the problem :) )
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 work, i'll try to better document what i did for someone
to write a patch. ( Or at least, to serve as a reminder the next time i'll
encounter the problem )
Hi,
If gpio's are correct, than all you need to do is write a new keymap.
These is how I did it: If codes from original keymap are wrong erase the
keycodes in ir-keymaps.c, but leave the header, pointer or whatever is
called. In your case like that:
/* Sylvain Vignaud sylv...@vignaud.org */
static IR_KEYTAB_TYPE AdsInstantTvPci_codes[IR_KEYTAB_SIZE] = {
// Buttons are in the top to bottom physical order
// Some buttons return the same raw code, so they are currently
};
Compile/install/load the drivers. You should get something like these in
dmesg:
dmesg example for a single button pressed (my card):
saa7134 IR (Compro Videomate DV: unknown key: key=0x29 raw=0x29 down=1
saa7134 IR (Compro Videomate DV: unknown key: key=0x29 raw=0x29 down=0
The keycode (0x29) must be unique for every button pressed, and this is
what you write in ir-keymaps.c e.g.
[0x29] = KEY_POWER, /* power */
There has been standardization of keys recently, so this is how things
must be mapped now:
(http://linuxtv.org/wiki/index.php/Remote_Controllers)
Read also:
(http://linuxtv.org/wiki/index.php/Remote_controllers-V4L)
--
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
Re: (Saa7134) Re: ADS-Tech Instant TV PCI, no remote support
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 reason, saa7131_alsa was preventing snd_hda_intel from creating a /dev/dsp device ( hda-intel: Error creating card! ) -- 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
