Re: [PATCH] v4l: saa7134: support ir-remote for 10moons TM300

> On Fri, 2007-05-11 at 11:51 +0400, Nickolay V. Shmyrev wrote: > > Great, now another correction, sorry for not noticing it before. With > > correction of bit 0x4 -> 0x2 your remote is exactly the same as > > ir_codes_encore_enltv so probably there is sense just to reuse

Re: [PATCH] v4l: saa7134: support ir-remote for 10moons TM300

В Птн, 11/05/2007 в 11:02 +0800, Tony Wan пишет: > Enable the IR-remote of the 10moons TM300 card and add the key-codes for > it's remote. > > It has been tested using lirc. All the key codes are accepted. > > Signed-off-by: Tony Wan <[EMAIL PROTECTED]> > --- > drivers/media/common/ir-keymaps.c

Re: [PATCH 2/3] v4l: saa7134: enable ir-remote for 10moons TM300 card

Hello Tony. Very nice patch, thanks. В Чтв, 10/05/2007 в 11:04 +0800, Tony Wan пишет: > Enable the IR-remote of the 10moons TM300 card and add the key-codes for > it's remote. But to enable all the keys, "IR_KEYTAB_SIZE", the size of > code tables should be at least 256. > It has been tested usin

initrd support in 2.6 kernels

Hallo Guys! I has initrd, that nice loaded by all 2.4 kernels. But 2.6.9 kernel has some difference in loading initrd(as i discovered). This warning produced by kernel on boot: ...SKIP... Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x0080,32M ...SKIP... checking if image is

Re: Digi Neo 8: linux-2.6.12_r2 jsm driver

Christoph Hellwig wrote: On Tue, Apr 12, 2005 at 04:13:43PM +0400, Ihalainen Nickolay wrote: Also the driver has changed a little in -mm, can you provide a diff against that? Sorry. diff -up -r linux-2.6.12-rc2/drivers/serial/jsm/jsm_driver.c linux-2.6.12-rc2-modified/drivers/serial/jsm

Digi Neo 8: linux-2.6.12_r2 jsm driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I compile linux-2.6.12_r2 sources with jsm support, but Digi Neo 8 is unsupported. after some code-modifications it works fine. lspci -v :00:09.0 Serial controller: Digi International Digi Neo 8 (rev 02) (prog-if 02 [16550]) ~Subsystem: Digi

Kernel Oopses, can anyone fix it?

Hello Guys! I has some shit happens after 2-3 days system working. After 2-3 days in kernel.debug i has many oopses. Stock 2.4.27 kernel. At time oopses started, system can't fork no one process. Below first two: OOPS No 1 --- Jan 2 16:43:00 localhost kernel: Unable to handle kernel paging

oops after 2-3 days working...

Hello Guys! I has host, running my applications. After 2-3 days, i can't logon to system via network, and can't login from console. In kernel.debug many oopses for processes telnetd, sshd, crond, bash and other... Kernel - stock 2.4.27. After oopsing started, system working 5-6 hours and hanged.