lkml.org 
[lkml]   [2009]   [Dec]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] What are the goals for the architecture of an in-kernel IR system?
    Jon Smirl wrote:
    > On Mon, Dec 7, 2009 at 1:41 PM, Dmitry Torokhov
    > <dmitry.torokhov@gmail.com> wrote:
    >> That is why I think we should go the other way around - introduce the
    >> core which receivers could plug into and decoder framework and once it
    >> is ready register lirc-dev as one of the available decoders.
    >
    > The core needs to allow for RF remotes too.
    >
    > -Bluetooth remotes are already in kernel somehow, I don't know how they work,
    > -RF4CE, the 802.15.4 stack has been recently merged, the remotes use a
    > protocol on top of that. These remotes will hit the consumer market
    > next year. Sony, Panasonic and other big names are behind this.
    > -Zwave, the Harmony remotes use Zwave. There is no Zwave support in
    > the kernel that I am aware of. Zwave is proprietary.
    >
    > After these protocols are decoded you end up with scancodes. The
    > scancodes need to get injected into input somehow and then flow
    > through the mapping process. Decoding down to the scancodes probably
    > happens over in the networking code.
    >
    > After an in-kernel IR decoder runs it needs to hand off the scancodes
    > into the input subsystem. This same API can be used by the networking
    > code to hand off RF scancodes.
    >

    Yes, the same core should be able to work with non infra red remotes, but, depending
    on how the device is implemented.

    Cheers,
    Mauro.


    \
     
     \ /
      Last update: 2009-12-08 12:25    [W:0.024 / U:0.748 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site