Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753113AbZK1Rhk (ORCPT ); Sat, 28 Nov 2009 12:37:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753061AbZK1Rhj (ORCPT ); Sat, 28 Nov 2009 12:37:39 -0500 Received: from qw-out-2122.google.com ([74.125.92.26]:45524 "EHLO qw-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752878AbZK1Rhi convert rfc822-to-8bit (ORCPT ); Sat, 28 Nov 2009 12:37:38 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oUEa7THaGYpyh3pAww3S6WiVlifJjSgUUi1+NqVi0v51ynLKaReujfInrXWZYq8zIA y4heW/lFPbddBIpeFnCrWb1SnURKHJloWsheJFeg/rEjNhD47ejBRVbGTb3YR0M+dDyk ZY3VI6xGkttBMwWOZU5Ow4QS+jm2lYzBXfsMw= MIME-Version: 1.0 In-Reply-To: References: <9e4733910911280906if1191a1jd3d055e8b781e45c@mail.gmail.com> Date: Sat, 28 Nov 2009 12:37:40 -0500 Message-ID: <9e4733910911280937k37551b38g90f4a60b73665853@mail.gmail.com> Subject: Re: [RFC] What are the goals for the architecture of an in-kernel IR system? From: Jon Smirl To: Krzysztof Halasa Cc: Christoph Bartelmus , awalls@radix.net, dmitry.torokhov@gmail.com, j@jannau.net, jarod@redhat.com, jarod@wilsonet.com, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, maximlevitsky@gmail.com, mchehab@redhat.com, stefanr@s5r6.in-berlin.de, superm1@ubuntu.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1041 Lines: 32 On Sat, Nov 28, 2009 at 12:35 PM, Krzysztof Halasa wrote: > Jon Smirl writes: > >> There are two very basic things that we need to reach consensus on first. >> >> 1) Unification with mouse/keyboard in evdev - put IR on equal footing. >> 2) Specific tools (xmodmap, setkeycodes, etc or the LIRC ones) or >> generic tools (ls, mkdir, echo) for configuration > > I think we can do this gradually: > 1. Merging the lirc drivers. The only stable thing needed is lirc > ? interface. Doing that locks in a user space API that needs to be supported forever. We need to think this API through before locking it in. > 2. Changing IR input layer interface ("media" drivers and adding to lirc > ? drivers). > -- > Krzysztof Halasa > -- Jon Smirl jonsmirl@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/