On Mon, 2006-09-18 at 11:17 -0400, Dmitry Torokhov wrote: > On 9/18/06, Richard Hughes <hughsient@xxxxxxxxx> wrote: > > On Wed, 2006-08-30 at 23:07 -0400, Dmitry Torokhov wrote: > > > On Wednesday 30 August 2006 23:03, Len Brown wrote: > > > > On Wednesday 30 August 2006 22:53, Dmitry Torokhov wrote: > > > > > > > > > So... do you want me to make it work with !CONFIG_INPUT or shoudl I just > > > > > add a dependency on INPUT in Kconfig for button driver? > > > > > > > > If virtually everybody uses INPUT, then I'm fine with the ACPI button driver simply depending > > > > on CONFIG_INPUT. > > > > > > > > If nobody uses ACPI on a system without INPUT, then I don't see why we should > > > > muck up the code to suport a case that nobody will test or use. > > > > > > > > > > INPUT is not used on s390 but I suppose that's ok ;) You need to work > > > really hard to disable input (embedded, no VTs or anything, etc). > > > > Is there any feedback on this solution? Also, what's the timescale for > > conversion to the input layer - are we talking blue sky or a few months? > > I want to make sure userspace is in a position for this change. > > > > I sent the updated patch to Yu Luming, the copy is in the list archives: > > http://marc.theaimsgroup.com/?l=linux-acpi&m=115751976924048&w=2 > > so unless there are objections to the thing I'd like to have it > applied to ACPI tree. Brilliant, thanks Dmitry. Richard. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
