Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964982AbZKYWwE (ORCPT ); Wed, 25 Nov 2009 17:52:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964962AbZKYWwD (ORCPT ); Wed, 25 Nov 2009 17:52:03 -0500 Received: from fg-out-1718.google.com ([72.14.220.152]:27243 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964951AbZKYWwB (ORCPT ); Wed, 25 Nov 2009 17:52:01 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=rCAzhNh9yaIMnBypuNvVZ8s62X2ioTl+EHcq1zcrgMbY9NEyYZYerCddejSOBvyzUJ yCZ7bWK6u8QaVS0CSvKP9br5W/KCPOO+ESSw+GCyd93vwCGuoee8Nq8uL2CfH0R7/w+c s8BTSFas52dkDiy8hZFgBOFvjTXdDYKlcmATI= Subject: Re: IR raw input is not sutable for input system From: Maxim Levitsky To: Krzysztof Halasa Cc: Sean Young , Trent Piepho , Jarod Wilson , Dmitry Torokhov , Mauro Carvalho Chehab , Jarod Wilson , linux-kernel@vger.kernel.org, Mario Limonciello , linux-input@vger.kernel.org, linux-media@vger.kernel.org, Janne Grunau , Christoph Bartelmus In-Reply-To: References: <200910200956.33391.jarod@redhat.com> <200910200958.50574.jarod@redhat.com> <4B0A765F.7010204@redhat.com> <4B0A81BF.4090203@redhat.com> <20091123173726.GE17813@core.coreip.homeip.net> <4B0B6321.3050001@wilsonet.com> <1259105571.28219.20.camel@maxim-laptop> <1259155734.4875.23.camel@maxim-laptop> <20091125213246.GA44831@atlantis.8hz.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 26 Nov 2009 00:52:02 +0200 Message-ID: <1259189522.15916.1.camel@maxim-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 854 Lines: 25 On Wed, 2009-11-25 at 23:30 +0100, Krzysztof Halasa wrote: > Sean Young writes: > > > Absolutely. There are a number of use cases when you want access to the > > space-pulse (i.e. IR) information. > > I think nobody proposes otherwise (except for devices which can't pass > this info). I think we were taking about such devices. I have no objection that devices that *do* decode the protocol, they should be handled inside kernel. But devices that send raw pulse/space data should be handled in lirc that will feed the data back to the kernel via uinput. Best regards, Maxim Levitsky -- 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/