Bug 514580

Summary:	atilibusb lirc userspace driver doesn't support ati remote wonder II
Product:	[Fedora] Fedora	Reporter:	Jarod Wilson <jarod>
Component:	lirc	Assignee:	Jarod Wilson <jarod>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12	CC:	bnocera, jarod, yves-redhat
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	462212	Environment:
Last Closed:	2010-01-11 16:18:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jarod Wilson 2009-07-29 17:43:10 UTC

+++ This bug was initially created as a clone of Bug #462212 +++
[...]
--- Additional comment from yves-redhat on 2009-07-27 19:51:31 EDT ---

Unfortunately, atilibusb only supports a small subset of the ATI remotes (only USB vendor id: 0bc7) and thus isn't a valid substitute for lirc_atiusb. My remote is shown by lsusb as:

Bus 002 Device 004: ID 0471:0602 Philips ATI Remote Wonder II Input Device

Vendor ID 0471 is supported by lirc_atiusb and was working just fine with the standard Fedora kernels until it was removed. lirc's atilibusb driver doesn't find the remote, which makes perfect sense when looking at the source for atilibusb given that it only supports vendor id 0bc7 (an older generation of the remote).

Can you please re-enable the compilation of lirc_atiusb as a result.

I personally simply put ati_remote2 in my blacklist and everything works fine, letting lirc_atiusb take control.

--- Additional comment from jwilson on 2009-07-29 13:32:45 EDT ---

Yeah, support for the RWII should probably be added to atilibusb, but you might also be able to use the devinput lirc userspace driver with the RWII.

Re-enabling lirc_atiusb is not the right fix though. Two different device drivers for the same hardware only leads to more problems than it solves, and ati_remote2 is already in the upstream kernel.

FWIW, I actually have an RWII of my own, and getting it working with lirc again, one way or another, is on my TODO list, I just haven't got there yet...

Comment 1 Bug Zapper 2009-11-16 11:10:44 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Jarod Wilson 2010-01-11 16:18:44 UTC

Current lirc can use the RWII via the userspace devinput driver, the atilibusb driver isn't really needed either. Using the devinput driver has the added benefit of not having to screw around with blacklisting the ati_remote2 driver too. Closing as WORKSFORME.