Re: lirc_atiusb (X10 remote) Kernel driver
Bengt Martensson <[email protected]>
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <[email protected]> |
On 08/26/17 09:58, Michael Markstaller via LIRC-list wrote:
> I'm still confused where to start.
>
> Am 26.08.2017 um 09:17 schrieb Alec Leamas:
>>
>>
>> On 25/08/17 21:19, Michael Markstaller via LIRC-list wrote:
>>
>>> I basically think (whatever driver it takes) this *is* rather a job for
>>> lirc, not a mainline kernel-mode driver?!
>> That's really not the situation. As for ir kernel drivers all
>> development is done in the kernel community these days.
>
> Ok, got it. Maybe I asked the wrong question: How to get it working with
> either the kernel-mode driver ati_remote and/or lirc (atilibusb) again.
This is much better!!
....
> So I see two options:
> a) (help) to implement channels into lirc/atilibusb which I'd prefer
I just had a look at atilibusb.c. It appears that it just nukes the
"channel number" (which I suspect is what in X10 terminology is called
house code
https://en.wikipedia.org/wiki/X10_(industry_standard)#Protocol ). Line 365:
buf[bytes_r - 1] &= 0x0F;
So, I suspect that just removing that line and adjusting the lirc.conf
should do the job. Use 16 bit data, and I suspect that the "channel"
will show up in pre_data, one pre data per "channel".
Greetz,
Bengt
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot