Re: CIR chipset Winbond WPC876xL

[Juan J. G. de S. L. <ska...@gm...>]

Hi, Léo.

2009/1/17 Léo <leo...@ya...>:
> I read subsequent e-mails about my issue and I disassembled my BIOS' ACPI DSDT table. For my surprise, there is no reference for the chip in there, but a reference for some CIR hardware (see attach.). I tried to physically disassemble my Acer 5920, but is very hard and I couldn't see the chip. So, I don't know if it is a WPC876xL really. I guessed it from http://ubuntu-virginia.ubuntuforums.org/showthread.php?p=6426246.

Nice! I think your receiver may be the same one. The DSL code seems to
define the riht I/O resources.

You could confirm it with this test:

---- start test ----
skandalfo@rimmer:~/install/dsdt$ hal-device | grep WEC
66: udi = '/org/freedesktop/Hal/devices/pnp_WEC1020'
  info.product = 'PnP Device (WEC1020)'  (string)
  info.udi = '/org/freedesktop/Hal/devices/pnp_WEC1020'  (string)
  pnp.id = 'WEC1020'  (string)
---- end test ----

The important thing is the device code (WEC1020).

> I just downloaded the code for the chip in the CVS rep and compiled it under 2.6.24-23 for x86_64. Config and complie worked fine but lircd service is not configured with right module  (it is inserting lirc_sir instead lirc_wpc8769l). Not a big problem.

[...]

> Dmesg output for this was
>
> [  857.595833] lirc_wpc8769l: Unknown symbol lirc_unregister_driver
> [  857.596047] lirc_wpc8769l: Unknown symbol lirc_register_driver

lirc_wpc8769l, as well as lirc_sir, I think, both depend on a common
lirc module called lirc_dev. Recently lirc_dev was changed in CVS so
that the functions *_plugin were renamed to *_driver, and that's the
cause of your problems. You have some lirc_dev leftover module from a
previous installation, and it's the one that was loaded into memory
when you inserted lirc_wpc8769l.

Please remove all previously existing lirc modules from
/lib/modules/<kernel_version>/ and make sure no one remains loaded
(either rmmod'ing them or rebooting). Afterwards recompile and
reinstall the CVS lirc and test again. It should load the module and
print more cheerful messages in dmesg :-)

Best regards,

   JJ.

-- 
Dream small if success is enough for you; dream big if you need to
change the world.