Re: lirc_atiusb (X10 remote) Kernel driver

Michael Markstaller via LIRC-list <[email protected]> Sat, 26 Aug 2017 10:57:42 +0200

Newsgroups	gmane.comp.hardware.lirc
Message-ID	<[email protected]>


Am 26.08.2017 um 10:23 schrieb Bengt Martensson:
> 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".

Also digged code a little, it seems even easier, all codes besides Ch1
are just different in atilibusb vs lirc_atiusb somehow; still searching
for the right pattern in the matrix or - at worst - will use irrecord to
generate a new lircd.conf for Ch2-16 (which is really 0-15) and send it in.

It's anyway *much better*, as a small patch/config for lircd is much
easier than fuddling around with kernel-drivers in
Ubuntu,OE1.6,OE2.0,OpenWRT,LEDE :)

Will report back..

Michael

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

signature.asc (application/pgp-signature, 819 B)