[pvrusb2] My HVR-1950 IR Remote does work

Mike Isely isely at isely.net
Thu Jun 11 08:43:38 CDT 2009


On Thu, 11 Jun 2009, Roger wrote:

> On Wed, 2009-06-10 at 22:44 -0500, Mike Isely wrote: 
> > On Tue, 2 Jun 2009, Roger wrote:
> > 
> 

   [...]

> 
> > > (One other neat note, /dev/lirc0 & /dev/lirc1 exists and it would seem
> > > lirc picks-up the IR signals even with the /dev/lirc0 unplugged -- even
> > > though /etc/conf.d/lirc is defined to use /dev/lirc0.  However, I'm
> > > still initially going through all these configurations a little at a
> > > time.)
> > 
> > I suspect that there are some factors at work here that you are not 
> > following.  I recommend you review the LIRC documentation.
> 
> If I wrote this, then I'm not too worried about it as it seems like more
> of a feature rather then an issue.

????? That makes no sense whatsoever.


> 
> 
> I likely solved this problem of this user.
> 
> The kernel requires to be configured with CONFIG_VIDEO_V4L1_COMPAT (=y
> or =m) enabled in order for Lirc to work properly (using the
> Hauppauge_350 profile).  In other words, just screwing around now and
> noticed the HVR-1950 remote stopped working after disabling this kernel
> config.  Or, they could be still sol.  Brief clipping of my kernel
> config follows:
> 
> 
> #
> # Multimedia core support
> #
> CONFIG_VIDEO_DEV=y
> CONFIG_VIDEO_V4L2_COMMON=y
> # CONFIG_VIDEO_ALLOW_V4L1 is not set
> CONFIG_VIDEO_V4L1_COMPAT=y
> CONFIG_DVB_CORE=y
> CONFIG_VIDEO_MEDIA=y
> 

There is no aspect of the V4L API that has anything to do with LIRC.  
The pvrusb2 driver's support for IR reception does not involve any V4L 
API.  Therefore enabling / disabing a piece of the V4L API should not in 
any way affect the ability to receive IR.

  -Mike


-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8


More information about the pvrusb2 mailing list