[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m38wdxrobz.fsf@intrepid.localdomain>
Date: Mon, 23 Nov 2009 21:14:08 +0100
From: Krzysztof Halasa <khc@...waw.pl>
To: Mauro Carvalho Chehab <mchehab@...hat.com>
Cc: James Mastros <james@...tros.biz>,
Devin Heitmueller <dheitmueller@...nellabs.com>,
Jarod Wilson <jarod@...hat.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
linux-kernel@...r.kernel.org,
Mario Limonciello <superm1@...ntu.com>,
linux-input@...r.kernel.org, linux-media@...r.kernel.org,
Janne Grunau <j@...nau.net>,
Christoph Bartelmus <lirc@...telmus.de>
Subject: Re: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure
Mauro Carvalho Chehab <mchehab@...hat.com> writes:
> True, but this means that everyone with an IR will need to use lirc.
I think that if the input layer (instead of raw code) is used, a utility
which only sets the mapping(s) would suffice. I.e. no daemon.
> /me thinks that, whatever decided with those lirc drivers, this should
> be applied also to the existing V4L/DVB drivers.
Certainly.
> IMO, it would be better to load the tables at the boot time (or at the
> corresponding hotplug event, for USB devices).
Sure (unless the "raw code" interface is in use).
Though maybe the raw code interface should be done in a simple library
instead of requiring the daemon.
--
Krzysztof Halasa
--
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