[mythtv-users] Slightly OT: ATI Remote Wonder with Fedora 15

[John Welch]

On Wed, Jun 29, 2011 at 11:52 PM, Jarod Wilson <jarod at wilsonet.com> wrote:
> On Jun 29, 2011, at 7:24 PM, John Welch wrote:
>
>> On Thu, Jun 2, 2011 at 5:19 PM, Jarod Wilson <jarod at wilsonet.com> wrote:
>>> On Jun 2, 2011, at 2:23 PM, John Welch wrote:
>>>
>>>> On Thu, Jun 2, 2011 at 1:18 PM, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>>>>> On 06/02/2011 12:24 PM, John Welch wrote:
>>>>>> On Thu, Jun 2, 2011 at 9:48 AM, Michael T. Dean wrote:
>>>>>>> On 06/02/2011 09:21 AM, John Welch wrote:
>>>>>>>> I'll check with Axel to see if the 'lirc_atiusb' module is something
>>>>>>>> that he has provided in the past and may be able to package for F15.
>>>>>>>> Failing that, I'll work on the 'ati_remote' method.
>>>>>>> FWIW, I like/use lirc_atiusb driver because it allows me to use the
>>>>>>> "mouse" device as regular remote buttons instead of as a (useless to
>>>>>>> MythTV) mouse.  If you don't care to change the mouse to regular remote
>>>>>>> buttons, using ati_remote with lirc's devinput driver to provide a
>>>>>>> custom mapping of buttons is likely the easiest approach.  (I'm pretty
>>>>>>> sure--though not positive--that the ati_remote/devinput approach cannot
>>>>>>> be used to treat remote mouse events as button events.)
>>>>>> Thanks Mike.  I'd like to continue to use the lirc_atiusb driver
>>>>>> simply because I have everything setup and working the way I want it.
>>>>>> I don't think I necessarily *need* the mouse buttons, but it is nice
>>>>>> to have the option to use them as remote buttons.
>>>>>
>>>>> Ooops.  Too many drivers--I copy/pasted the wrong name.  I meant I
>>>>> actually use the atilibusb driver.  It's much nicer than lirc_atiusb
>>>>> because it's a userspace driver (and, in the case of atilibusb, doesn't
>>>>> require /any/ kernel modules for the ATI remote--since it uses libusb to
>>>>> access the device directly).
>>>>>
>>>>> I'm a big fan of the LIRC drivers that don't require special/LIRC-only
>>>>> kernel modules, and I believe I've saved many times the amount of time
>>>>> it took me to switch drivers just in not having to deal with special
>>>>> kernel modules.
>>>>>
>>>>> Mike
>>>>
>>>> OK, thanks.  Looks like I have another option to look at :)
>>>
>>> Note, however, that for reasons I don't yet understand, some of the lirc
>>> userspace drivers aren't getting built into the F15 lirc userspace
>>> packages. I thought I'd fixed it in lirc-0.9.0-5.fc15, but apparently not.
>>> I'll get it sorted out as soon as I can though...
>>>
>>>
>> Just circling back to this almost a month after my last post.  I guess
>> this is a question mostly for Jarod.  Since my last post F15 has had a
>> "normal" update (from "updates" repo) of the 'lirc' package to
>> 0.9.0-6, and I just did an update enabling the "updates-testing" repo,
>> which got me to version 0.9.0-7.  Plus there has been a kernel update
>> (not sure if it would have any affect on this or not).  I still cannot
>> get my ATI Remote Wonder working using the 'atilibusb' driver.  It
>> appears that this driver still isn't getting built into the lirc
>> packages.  Am I missing something or is this still a known issue?  If
>> it is still an issue, is a fix likely to come soon or should I start
>> looking at other options?
>
> I committed the fix in upstream lirc and backported it to the 0.9.0-6.fc15
> package on June 6th, and the -7 build I just pulled down shows atilibusb
> in the lircd -H help output. What seems to be the problem, officer?
>
> --
> Jarod Wilson
> jarod at wilsonet.com
>
>
>

I am all set.  I had de-blacklisted the ati_remote module, which was
interfering with lirc.  Everything seems to be working now.  Sorry for
the false alarm.

Thanks,
John