<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>LIRC - Linux Infrared Remote Control</TITLE>
<LINK REL="stylesheet" TYPE="text/css" HREF="lirc.css">
<LINK REL="shortcut icon" HREF="../images/favicon.ico">
<META NAME="description" CONTENT="LIRC - Linux Infrared Remote Control">
<META NAME="keywords" CONTENT="linux remote control, multimedia">
<META charset="UTF-8">
</HEAD>
<body>
<TABLE CLASS="menu"><TR>
<TD CLASS="menu"><IMG class="menuimg" SRC="../images/diode.gif" ALT="LIRC icon" ALIGN="LEFT"></TD>
<TD><IMG class="menuimg" SRC="../images/lirc.gif" ALT="LIRC logo" ALIGN="RIGHT"></TD>
</TR></TABLE>
<a name="overview"></a><hr>
<center><h1>atilibusb</h1></center>
<p>
The atilibusb driver offers support for many RF devices sporting
usb receivers with the X10 chip, Some of these are X10 branded, other sold
under names such as ATI or Medion.</p>
<p>
Typical dmesg output for hotplugging such a device:
</p>
<pre>
usb 3-1: new low-speed USB device number 23 using xhci_hcd
usb 3-1: New USB device found, idVendor=0bc7, idProduct=0006
usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-1: Product: RF receiver
usb 3-1: Manufacturer: X10 WTI
</pre>
The driver conflicts with the linux atiusb kernel module. Thus, to use
atilibusb the kernel module must be blacklisted. This can be done with a
file named e. g., /etc/modprobe.d/lirc-blacklist with the following
content
<pre>
# blacklist drivers which conflict with lirc userspace drivers.
blacklist ati_remote
blacklist lirc_atiusb
</pre>
<p>
The module autodetects available devices and a --device argument is normally
not required. However, if given an existing device as argument this will be
used. It has support for enumerating available devices e. g., using
<i>mode2 -l </i>. </p>
<p class="footer">
[<A HREF="http://www.lirc.org/">LIRC homepage</A>]
</p>
</body>
</html>
