Re: lirc_zilog with lirc-0.8.7 and kernel 2.6.33

[Jarod W. <ja...@wi...>]

On Dec 20, 2010, at 6:01 PM, Rick wrote:

> On 12/20/2010 05:37 PM, Jarod Wilson wrote:
>> On Dec 20, 2010, at 5:17 PM, Rick wrote:
>> 
>>> <stuff snipped>
>>>>>> Honestly, now that I think about it, junk that whole process you're
>>>>>> going through there. I haven't a clue what's present in Mandriva's
>>>>>> kernel or what exactly is present in that old snapshot you're poking
>>>>>> at. Just use the new v4l/dvb media_build infra:
>>>>>> 
>>>>>> http://git.linuxtv.org/media_build.git
>>>>>> 
>>>>>> Clone from one of the URL listed there, cd into media_build, then
>>>>>> run ./build.sh and it should take care of patching and building
>>>>>> everything. Then you can just grab the resulting lirc_dev.ko and
>>>>>> lirc_zilog.ko and drop them in your kernel module path.
>>>>>> 
>>>>> 
>>>>> That looked promising until this happened ...
>>>>> 
>>>>> /usr/src/lirc-git-jarod/v4l/bttv-input.c: In function 'init_bttv_i2c_ir':
>>>>> /usr/src/lirc-git-jarod/v4l/bttv-input.c:395: error: too many arguments to function 'i2c_new_probed_device'
>>>>> make[3]: *** [/usr/src/lirc-git-jarod/v4l/bttv-input.o] Error 1
>>>>> make[2]: *** [_module_/usr/src/lirc-git-jarod/v4l] Error 2
>>>>> make[2]: Leaving directory `/usr/src/linux-2.6.33.7-desktop-2mnb'
>>>>> make[1]: *** [default] Error 2
>>>>> make[1]: Leaving directory `/usr/src/lirc-git-jarod/v4l'
>>>>> make: *** [all] Error 2
>>>>> *** ERROR. Aborting ***
>>>> 
>>>> Hrm, something must have gone wrong with backport patch applications,
>>>> because there's definitely a patch in the build tree for the i2c
>>>> interface changes. Sigh. Take a look in backports/v2.6.33_series and
>>>> see what's applied and what isn't. Everything in there needs to be
>>>> applied to the source files under linux/.
>>>> 
>>> 
>>> I'm really not clear what to do with that information.  By now you've probably guessed how green I am.  In parallel, I went down a different path ... basically, I took the source from the Mandriva repo which had an experimental kernel which included lirc_dev.c and lirc_zilog.c (the version of the kernel was 2.6.34 I believe).  I was able to get both the compile.
>>> 
>>> Here's the rub... I have both modules loaded, but I don't see any /dev/lirc devices.  I'm kinda clueless what to do next.
>> 
>> I'd advise considering installing a distribution that supports your
>> hardware out of the box[*]. To my knowledge, that means either the
>> latest Ubuntu or any of the past several Fedora releases.
>> 
>> [*] well, not 100% out of the box, but the drivers are already built
>> and installed, you just have to get the firmware and config file in
>> place and load the driver
>> 
> 
> I wish it were that easy.  I've been running mandriva for years and have always managed to get the last bit working (ie the irblaster) with your gracious help.  Honestly, I don't know how to thank you.

Okay, we'll keep trying w/Mandriva, but you could always thank me by
switching to Fedora (or Red Hat Enterprise Linux 6). ;)

> For what it's worth, I tried something ... I did a modprobe lirc_i2c. Both devices showed up, however, the zilog driver couldn't see the blaster.  Is there some way to wake up the zilog driver to detect the pvr-150 blaster chips?
> 
> What is the proper order of drivers to load?  lirc_i2c, then lirc_dev, lirc_zilog?

You shouldn't be loading lirc_i2c. With a kernel of the vintage you're
running, it'll try binding to the very same bits lirc_zilog is supposed
to bind to, and it'll succeed if its loaded first. I'd bounce the box,
and try nothing but a 'modprobe lirc_zilog'.

-- 
Jarod Wilson
ja...@wi...