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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3aaafc130811051215v6a66e9f6n125ffd3727c5a6ed@mail.gmail.com>
Date:	Wed, 5 Nov 2008 15:15:05 -0500
From:	"J.R. Mauro" <jrm8005@...il.com>
To:	"Jon Smirl" <jonsmirl@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH V4 0/6] In-kernel IR remote control support

On Wed, Nov 5, 2008 at 3:07 PM, Jon Smirl <jonsmirl@...il.com> wrote:
> On Wed, Nov 5, 2008 at 2:59 PM, J.R. Mauro <jrm8005@...il.com> wrote:
>> On Wed, Nov 5, 2008 at 2:47 PM, Jon Smirl <jonsmirl@...il.com> wrote:
>>> New release of in-kernel IR support implementing evdev support. The goal of in-kernel IR is to integrate IR events into the evdev input event queue and maintain ordering of events from all input devices. Still looking for help with this project.
>>
>> (Forgive me if this has already been asked or dealt with)
>>
>> Have you contacted the LIRC developers? Is there any overlap between
>> your projects?
>
> The LIRC people know about this. Pieces of the code are coming from
> the LIRC source base and being reworked for kernel inclusion.

Great, it's nice to see there's cooperation.

>
> LIRC needs a daemon to run and apps have to be modified to use it.
> This code runs all in-kernel and looks like keyboard input to apps.
>
> LIRC developers and anyone else and encouraged to help with this code.

What's involved in converting an LIRC driver into something usable
with your framework?

>
> --
> Jon Smirl
> jonsmirl@...il.com
>
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ