[pvrusb2] Remote dies when upgrading to 2.6.38 from 2.6.36 on HVR-1900

Nicholas Robbins nickrobbins at yahoo.com
Sun Jul 10 13:10:05 CDT 2011


Thanks Mike! 


You were exactly right, looks like all of the modules are now in the tree, and lirc just provides the user-space daemon and applications. Also, my key codes have changes and such, as the remote is now handled with the event driver rather than and i2c driver from the user-space perspective. If anyone needs help getting the remote to work with a newer kernel let me know, as I've gotten it sorted out. (At least for 2.6.38.6 and lirc 0.9.0 on gentoo)

-Nick



----- Original Message -----
From: Mike Isely <isely at isely.net>
To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
Cc: 
Sent: Saturday, July 9, 2011 10:05 PM
Subject: Re: [pvrusb2] Remote dies when upgrading to 2.6.38 from 2.6.36 on HVR-1900

On Sat, 9 Jul 2011, Nicholas Robbins wrote:

> Hello, 
> 
> 
> I've had the remote working for some time, but today when I tried to 
> upgrade my kernel to 2.6.38 from 2.6.36, the remote stopped working. 
> Plugging the device in no longer produces a /dev/lirc0.Also there are 
> no comments from lirc in the system log when the device is plugged 
> in. 
> 
> The only thing I can find is that there is no longer a v4l1 compatibility option in the newer kernels. 
>  
> Could that be the problem?

LIRC doesn't depend on the V4L ioctl-based API.  It expects instead to 
install a kernel driver which ties into the I2C bus API exported by the 
bridge driver (e.g. pvrusb2).

However that I2C API has undergone some changes of late.  There have 
been some recent changes to the pvrusb2 driver within the kernel needed 
to stay in sync with these changes.  I'd be willing to bet that this is 
what has caused the problem.  This unfortunately creates issues for 
out-of-tree drivers when the kernel APIs they are using becomes a moving 
target.

Try looking for a later version of LIRC.  Odds are that a later release 
of the package already tracks this - or there very soon will be a 
release that will catch up.

  -Mike

-- 

Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
_______________________________________________
pvrusb2 mailing list
pvrusb2 at isely.net
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2



More information about the pvrusb2 mailing list