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

[<li...@ba...>]

Hi!

Jon Smirl "jon...@gm..." wrote:
[...]
> I came up with the state machine approach trying to make Sony remotes
> works. Sony remotes transmit multiple protocols. LIRC only supports a
> single protocol in a config file so Sony remotes need to be used in
> raw mode with LIRC.

Statements like this give me the impression that you actually never really  
looked into LIRC and what it does. Of course LIRC does support any number  
of protocols in a single config file.
LIRC is now in use for >10 years. It's very well tested and does its job.

Again: if your only concern is code size and responsiveness, then please  
create a hook in lirc_dev for your in-kernel decoder. You won't have to  
write a single device driver and can just use the LIRC code base and we  
can stop discussing and get some work done. Win-win.

[...]
> You are coming from a world that has four 3GHz CPU cores and 8GB of
> RAM.  Things are a lot different when you have a single 150Mhz CPU and
> 32MB RAM. lircd is 400KB

If you want to discuss on that level, please get your numbers right.
On my system lircd is 110kB. Of course if you compile in all user space  
drivers you will get a much bigger executable. But it's comparing apples  
with bananas anyway, as lircd does much more than just decoding the IR  
data.
BTW, I've started development on LIRC on a 486-DX 40MHz with 20MB of RAM  
and it was working fine...

Christoph