[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B0F7E21.3020703@s5r6.in-berlin.de>
Date: Fri, 27 Nov 2009 08:22:09 +0100
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Jarod Wilson <jarod@...sonet.com>
CC: Jon Smirl <jonsmirl@...il.com>, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: [IR-RFC PATCH v4 0/6] In-kernel IR support using evdev
Jarod Wilson wrote:
> On 11/26/2009 08:34 PM, Jon Smirl wrote:
>> Raw mode. There are three sysfs attributes - ir_raw, ir_carrier,
>> ir_xmitter. Read from ir_raw to get the raw timing data from the IR
>> device. Set carrier and active xmitters and then copy raw data to
>> ir_raw to send. These attributes may be better on a debug switch. You
>> would use raw mode when decoding a new protocol. After you figure out
>> the new protocol, write an in-kernel encoder/decoder for it.
>
> Also neglected to recall there was raw IR data access too. However, a
> few things... One, this is, in some sense, cheating, as its not an input
> layer interface being used. :) Granted though, it *is* an existing
> kernel interface being used, instead of adding a new one. Two, there's
> no userspace to do anything with it at this time.
No; it is a new interface, just using an existing mechanism (sysfs). Not
all of sysfs in itself is an interface really; rather there is a number
of interfaces which are implemented by means of sysfs.
sysfs is primarily meant for simple textual attributes though, not for
I/O streams.
--
Stefan Richter
-=====-==--= =-== ==-==
http://arcgraph.de/sr/
--
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