| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: 04 Feb 2007 04:03:00 +0100 From: lirc@...telmus.de (Christoph Bartelmus) To: penberg@...helsinki.fi cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] lirc: remove backwards compatibility macro obfuscation Hi Pekka, on 02 Feb 07 at 10:39, you wrote: [...] > On 02 Feb 2007 05:54:00 +0100, Christoph Bartelmus <lirc@...telmus.de> > wrote: >> Any help welcome. > Here's a start. As I'm running a 2.4 kernel myself you will probably understand that I am a bit reluctant to drop 2.4 support from LIRC right now. Possible ways to handle this: 1. lirc-0.8.2 will be the last release officially supporting 2.4. I remove backwards compatibility after this release. 2. I create a CVS branch for 2.6 only version. Drawbacks of 1.: also support for some older 2.6 kernels would have to be dropped as there have been API changes in 2.6 kernels. Drawbacks of 2.: have to maintain 2 branches in parallel for some time. But before continuing to discuss the further procedure and minor code optimisations you should know which major changes need to be done to LIRC drivers before thinking of a merge to the kernel: 1. LIRC requires an official device major number! A minor number system should be defined. 2. Some of the drivers need to be rewritten to support more than one device at a time. Esp. lirc_serial needs to be rewritten to handle more than one serial port in parallel. Christoph - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists