Missing kernel modules in 2.6.35.12

Question

I'm building the LTS kernel 2.6.35.12 and have noticed several key modules are completely missing: lirc_i2c and lirc_dev.  If I compare the confg from ARCH 2.6.35 to that of ARCH 2.6.37, I see that the entire section within the config that builds these is missing.  I know for a fact that there are supported under 2.6.35 because I have been using this same setup since 2.6.26 just fine.
Here is a bit from 2.6.37's config that shows where these are:
# Texas Instruments shared transport line discipline
CONFIG_ST_BT=m
CONFIG_ADIS16255=m
CONFIG_FB_XGI=m
CONFIG_LIRC_STAGING=y
CONFIG_LIRC_BT829=m
CONFIG_LIRC_I2C=m
CONFIG_LIRC_IGORPLUGUSB=m
CONFIG_LIRC_IMON=m
CONFIG_LIRC_IT87=m
This section for 2.6.37 is found:
-> Device Drivers
-> Staging drivers (STAGING [=y])
-> Exclude Staging drivers from being built (STAGING_EXCLUDE_BUILD [=n])     
-> Linux Infrared Remote Control IR receiver/transmitter drivers (LIRC_STAGING [=y])
Again, under 2.6.35 there is no corresponding entry for the "Linux Infrared Remote Control IR receiver/transmitter drivers" but again, I know that my remote worked back when Arch had 2.6.35.x in [core].
Thoughts as to how to enable building them under the LTS 2.6.35.x is appreciated!

Answer 1

iphitus wrote:Kernel modules for 2.6 have a .ko NOT .o filename.
The included makefile is written for a 2.6 kernel and produces a .o, and Gentoo used to mix the two, although Gentoo is hardly the golden standard.
Please ensure that you use the included makefiles and installation options included with the driver and run depmod -a after installing.
Both the vanilla kernel and the pkgbuild include the source and makefile unchanged in the correct place. Both are patched correctly as per the included readme.
If the driver is precompiled and has no make options, then it will *not* work under any circumstances.
I don't think I can precompile it, since it depends on about a dozen headers from include/scsi, which all have compile-time macros set by the kernel's makefiles. Even if I could track down every #ifdef and set the macro by hand, I wouldn't want to.
What driver is it? It would help us identify your problem much more easily.
Areca ARC1210 Source driver. Before you spend any time on this particular module, I should reiterate that I don't think there's anything wrong with the module itself, I was just looking for a minimum effort method to install the module, preferably without a custom kernel. I don't see this as a very likely option anymore, so more than likely I will use the pkgbuild I wrote for the purpose.