lkml.org 
[lkml]   [2009]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] Should we create a raw input interface for IR's ? - Was: Re: [PATCH 1/3 v2] lirc core device driver infrastructure
    Christoph Bartelmus wrote:
    > Hi Mauro,
    >
    > on 26 Nov 09 at 10:36, Mauro Carvalho Chehab wrote:
    > [...]
    >> lircd supports input layer interface. Yet, patch 3/3 exports both devices
    >> that support only pulse/space raw mode and devices that generate scan
    >> codes via the raw mode interface. It does it by generating artificial
    >> pulse codes.
    >
    > Nonsense! There's no generation of artificial pulse codes in the drivers.
    > The LIRC interface includes ways to pass decoded IR codes of arbitrary
    > length to userspace.

    I might have got wrong then a comment in the middle of the
    imon_incoming_packet() of the SoundGraph iMON IR patch:

    + /*
    + * Translate received data to pulse and space lengths.
    + * Received data is active low, i.e. pulses are 0 and
    + * spaces are 1.
    + *
    + * My original algorithm was essentially similar to
    + * Changwoo Ryu's with the exception that he switched
    + * the incoming bits to active high and also fed an
    + * initial space to LIRC at the start of a new sequence
    + * if the previous bit was a pulse.
    + *
    + * I've decided to adopt his algorithm.
    + */

    Cheers,
    Mauro.


    \
     
     \ /
      Last update: 2009-11-26 22:01    [W:0.029 / U:90.796 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site