Re: Status of lirc. should I create new reciever driver against it?

[Maxim L. <max...@gm...>]

On Thu, 2009-05-28 at 17:35 +0300, Maxim Levitsky wrote:
> Hi,
> 
> My notebook has a IR receiver, so called ENE CIR.
> It is actually a embedded controller, which has a IR sampler inside.
> 
> It is found in my acer aspire 5720G, and is exposed in acpi tables as
> ENE0100.
> 
> While its windows driver works only with MS approved remotes, and
> moreover I have seen on the web that only a bundled remote works with
> it, it is actually a generic receiver, and works here fine with all my
> remotes (since I reverse engineered it).
> 
> The only catch is that it holds only 8 bytes of IR timing, which are
> divided in 2 halfs, one is active, other is supposed to be read by host.
> Thus my current userspace app sucks, since it can't use interrupts.
> 
> I want to write a kernel driver for this device, but I don't know if I
> need to write it against lirc, or recently posted on LKML in-kernel IR
> framework.
> 
> Do you expect lirc to be merged any time? 

I am finally free, I will start working right away on my driver.
I would really like also to see lirc merged, since I always want all
linux drivers to be in tree, and :-) I want my future driver be there.
I have about 15 days of free time.

I have a question, since I don't yet know much about kernel development
(only basics) could you point me to areas of lirc that need cleanup?

Best regards,
	Maxim Levitsky