文件列表:

bttv\audiochip.h (1130, 2003-11-07)
bttv\bt832.c (8146, 2003-11-07)
bttv\bt832.h (11110, 2003-11-07)
bttv\bt848.h (12161, 2003-11-13)
bttv\btcx-risc.c (6658, 2003-11-07)
bttv\btcx-risc.h (899, 2003-11-07)
bttv\bttv-cards.c (114216, 2003-12-05)
bttv\bttv-driver.c (103864, 2003-12-03)
bttv\bttv-gpio.c (5085, 2003-11-24)
bttv\bttv-i2c.c (11903, 2003-11-26)
bttv\bttv-if.c (3974, 2003-11-07)
bttv\bttv-risc.c (23808, 2003-11-07)
bttv\bttv-vbi.c (6310, 2003-11-07)
bttv\bttv.h (11559, 2003-12-05)
bttv\bttvp.h (12462, 2003-12-03)
bttv\doc\CARDLIST.bttv (4551, 2003-11-13)
bttv\doc\CARDLIST.saa7134 (1408, 2003-11-13)
bttv\doc\CARDLIST.tuner (1607, 2003-11-13)
bttv\doc\Cards (27685, 2003-02-14)
bttv\doc\insmod-options (6420, 2003-11-13)
bttv\doc\MAKEDEV (571, 2003-11-13)
bttv\doc\Sound-FAQ (6064, 2003-11-13)
bttv\doc\Tuners (3281, 2003-02-14)
bttv\doc (0, 2005-01-05)
bttv\i2c-compat.h (1106, 2003-11-07)
bttv\id.h (1019, 2003-11-07)
bttv\ir-common.c (7704, 2003-12-01)
bttv\ir-common.h (2932, 2003-12-02)
bttv\ir-kbd-gpio.c (9774, 2003-12-08)
bttv\ir-kbd-i2c.c (9351, 2003-11-07)
bttv\Make.config (191, 2003-12-09)
bttv\Makefile (3896, 2003-12-09)
bttv\msp3400.c (47327, 2003-11-26)
bttv\msp3400.h (321, 2003-11-07)
bttv\tda9887.c (13616, 2003-11-07)
bttv\tuner.c (32875, 2003-12-08)
... ...

infrared remote control support in video4linux drivers ====================================================== basics ------ Current versions use the linux input layer to support infrared remote controls. I suggest to download my input layer tools from http://bytesex.org/snapshot/input-.tar.gz Modules you have to load: saa7134 statically built in, i.e. just the driver :) bttv ir-kbd-gpio or ir-kbd-i2c depending on your card. ir-kbd-gpio and ir-kbd-i2c don't support all cards lirc supports (yet), mainly for the reason that the code of lirc_i2c and lirc_gpio was very confusing and I decided to basically start over from scratch. Feel free to contact me in case of trouble. Note that the ir-kbd-* modules work on 2.6.x kernels only through ... how it works ------------ The modules register the remote as keyboard within the linux input layer, i.e. you'll see the keys of the remote as normal key strokes (if CONFIG_INPUT_KEYBOARD is enabled). Using the event devices (CONFIG_INPUT_EVDEV) it is possible for applications to access the remote via /dev/input/event devices. You might have to create the special files using "/sbin/MAKEDEV input". The input layer tools mentioned above use the event device. The input layer tools are nice for trouble shooting, i.e. to check whenever the input device is really present, which of the devices it is, check whenever pressing keys on the remote actually generates events and the like. You can also use the kbd utility to change the keymaps (2.6.x kernels only through). using with lircd ================ The cvs version of the lircd daemon supports reading events from the linux input layer (via event device). The input layer tools tarball comes with a lircd config file. using without lircd =================== XFree86 likely can be configured to recognise the remote keys. Once I simply tried to configure one of the multimedia keyboards as input device, which had the effect that XFree86 recognised some of the keys of my remote control and passed volume up/down key presses as XF86AudioRaiseVolume and XF86AudioLowerVolume key events to the X11 clients. It likely is possible to make that fly with a nice xkb config file, I know next to nothing about that through. Have fun, Gerd -- Gerd Knorr

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：