Archived:Em2820:Talk: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(No difference)

Revision as of 14:30, 17 February 2006

audio for my gadmei utv310

To open my sound for Gadmei utv310 (em2820 based, audio is seperated from usb line), I add a line into em2820_v4l2_open: em2820_write_regs_req(dev, 0x00, 0x08, "\xfd", 1); and close it in em2820_v4l2_close: em2820_write_regs_req(dev, 0x00, 0x08, "\xfe", 1). wish it will help you for your gadmei utv310 TV BOX. Now I am trying to make the IR remote control works. Ir address is 0xc6 in it.


hi! if you need some help let me know, be careful when playing around with GPIO writes em2820_v4l2_open isn't the right place for such things...

for the remote have a look at ir-kbd-i2c.c

       static const int probe_em28XX[] = { 0x30, 0x47, -1 }

add your i2c address to it shifted by 1 to the right, afterwards em28xx-input.c (em28xx_set_ir) it would be nice if you could autodetect your device.

p.s if you read this please move everything to em2820 or em2820:Talk please

Markus


very thanks for your advise. I have no em2820 datasheet, and so the command is came from its windows' driver sniffer. its works fine in my machine. BTW, where is the i4-kbd-i2c.c, I can not find it in my linux kernel-2.6.15 source code tree, now I have checked all the key code for my remote control panel. at your opinion, where should I open my sound in the driver, or I should let it to the client, i.e. when client open the device and wanna sound, then open...? thanks again!


this isn't documented in the datasheet, neither is the remote described there. the file is called ir-kbd-i2c.c not i4-kbd-i2c.c you should have it somewhere. A keymap for your device might already defined in ir-keymaps.c, if not just add it (don't forget to add the remote definition to ir-common.h too) Would be nice if you could prepare a patch I'd review and add it to my experimental repository then. Some core functionality will change in future since I'm about to add VBI/teletext