linux-kernel - Re: [RFC] What are the goals for the architecture of an in-kernel IR system?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Dec 2009 12:18:15 -0200
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Gerd Hoffmann <kraxel@...hat.com>
CC:	Andy Walls <awalls@...ix.net>, Krzysztof Halasa <khc@...waw.pl>,
	Jon Smirl <jonsmirl@...il.com>,
	Christoph Bartelmus <lirc@...telmus.de>,
	dmitry.torokhov@...il.com, j@...nau.net, jarod@...hat.com,
	jarod@...sonet.com, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
	maximlevitsky@...il.com, stefanr@...6.in-berlin.de,
	superm1@...ntu.com
Subject: Re: [RFC] What are the goals for the architecture of an in-kernel
 IR  system?

Gerd Hoffmann wrote:
> On 12/01/09 12:49, Andy Walls wrote:
>> On Tue, 2009-12-01 at 11:46 +0100, Gerd Hoffmann wrote:
>>> Once lirc_dev is merged you can easily fix this:  You'll have *one*
>>> driver which supports *both* evdev and lirc interfaces.  If lircd opens
>>> the lirc interface raw data will be sent there, keystrokes come in via
>>> uinput.  Otherwise keystrokes are send directly via evdev.  Problem
>>> solved.
>>
>> This will be kind of strange for lirc_zilog (aka lirc_pvr150).  It
>> supports IR transmit on the PVR-150, HVR-1600, and HD-PVR.  I don't know
>> if transmit is raw pulse timings, but I'm sure the unit provides codes
>> on receive.  Occasionally blocks of "boot data" need to be programmed
>> into the transmitter side.  I suspect lirc_zilog will likely need
>> rework....
> 
> Well, for IR *output* it doesn't make sense to disable evdev.  One more
> reason which indicates it probaably is better to introduce a ioctl to
> disable evdev reporting.  lircd will probably turn it off, especially
> when sending data to uevent.  debug tools might not, likewise apps
> sending IR.
> 
>>>   so killing the in-kernel IR limits to make ir-kbd-i2c
>>                    ^^^^^^^^^^^^^^^^^^^
>>>        being on par with lirc_i2c might be more useful in this case.
>>
>> I didn't quite understand that.  Can you provide a little more info?
> 
> Such as throwing away the address part of rc5 codes ...

This limit were already removed from the subsystem core by the patches
I committed recently (still only at the devel tree - I should be adding
those patches to my linux-next tree likely today). 

The remaining issue is that we'll need to re-scan the IR tables for 
every supported remote to be sure that we're getting the full RC5 code.
It is not complex, but requires lots of work from people that actually have
those IR's.

Cheers,
Mauro.

--
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/