LKML Archive on
help / color / mirror / Atom feed
From: (Christoph Bartelmus)
Subject: Re: [PATCH] lirc: remove backwards compatibility macro obfuscation
Date: 04 Feb 2007 04:03:00 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.64.0702021038270.21422@sbz-30.cs.Helsinki.FI>

Hi Pekka,

on 02 Feb 07 at 10:39, you wrote:
> On 02 Feb 2007 05:54:00 +0100, Christoph Bartelmus <>
> 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.


      parent reply	other threads:[~2007-02-04  3:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02  8:39 [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!) Pekka J Enberg
2007-02-02 11:04 ` Vincent Vanackere
2007-02-04  3:04   ` [PATCH] lirc: remove backwards compatibility macro obfuscation Christoph Bartelmus
2007-02-02 11:10 ` [PATCH] lirc: remove backwards compatibility macro obfuscation (Was: Free Linux Driver Development!) Jan Dittmer
2007-02-02 11:32   ` Pekka Enberg
2007-02-02 12:51     ` Jan Dittmer
2007-02-04  3:03 ` Christoph Bartelmus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).