Re: Seperation of LIRC user space decoding framework and kernel driver

[jeff123 <jef...@ho...>]

Many thanks for the reply.

Jeff



Jarod Wilson wrote:
> 
> On Nov 24, 2010, at 5:15 AM, Daniel Klaffenbach wrote:
> 
>> Hi,
>> 
>> On Wednesday 24 November 2010 07:35:19 jeff123 wrote:
>>> As LIRC kernel driver has been merged in the latested kernel, may I know
>>> if
>>> a seperate user space decoding framework will be released, with /daemon
>>> and
>>> /tools folder etc only?
>> LIRC can still be used with the in-kernel drivers.
> 
> Yeah, it should work with both the in-kernel and out of tree
> lirc drivers. At some point, once most of the major/relevant
> distros have moved to 2.6.36+, I think we'll start dropping
> the lirc kernel driver bits from the lirc.org tree.
> 
> 
>>> In this case, how would the daemon lircd know which kernel space driver
>>> is
>>> used?
>> I've done this a while ago. To accomplish this I had to configure LIRC
>> with "--
>> with-major=250 --with-driver=userspace"
> 
> Using --with-driver=userspace is definitely correct, that's how
> the Fedora lirc userspace-only packages have been getting built
> for years now (as Fedora carried the kernel drivers in its kernel
> by way of patches). The --with-major=250 part is not so correct.
> We use dynamic device minors, so one system (or even one boot),
> you may get 250, but another you'll get 248 or 252 or whatever.
> It shouldn't be necessary to specify a major to the userspace
> build -- I've never done so in the Fedora builds, and they've
> always worked just fine with the dynamic major.
> 
> 
>> I also adjusted the LIRC source files so they pick up the in-kernel LIRC 
>> headers - I don't know if this is still necessary.
> 
> Its supposed to work for 2.6.36+, but I've not actually tried it
> anytime lately, and have at least one report where it didn't seem
> to have worked. (Investigating that is on the TODO list).
> 
> -- 
> Jarod Wilson
> ja...@wi...
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
> Tap into the largest installed PC base & get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> 
> 

-- 
View this message in context: http://old.nabble.com/Seperation-of-LIRC-user-space-decoding-framework-and-kernel-driver-tp30285890p30328537.html
Sent from the LIRC mailing list archive at Nabble.com.