Re: drop lircd!

[Gerd K. <kr...@by...>]

> this would be a good way to do IR keyboards but for an actual remote
> this might be a very bad thing, i've got some remotes with keys that
> just couldn't be mapped to any keyboard keys that would make sense,

That isn't a problem, grep for "#define KEY_" in linux/input.h and see
what is in there :)

> and like its been said this would require keyboard focus.

That I'm a bit more worried about because it is very different from how
lirc works today.

> the best idea would be to make it so that you can choose which way it
> does this, the keyboard queue, or do it the way LIRC does right now,
> because in alot of cases the way LIRC does this makes more sense to me
> (though the config files are a bit odd sometimes)

Reading events directly works through /dev/input/event<n>, so both ways
should be doable.  I don't know (yet) how input layer and linux console
play together and whenever it is possible to tell the linux console from
which input device(s) it should accept keys.  Anyone can comment on
this?

  Gerd

PS: remember, I'm not on the lirc list, so Cc: me please.