| View previous topic :: View next topic |
| Author |
Message |
graysky
Tux's lil' helper
Joined: 25 Nov 2006
Posts: 118
Location: above the flames and the ashes
|
 Posted: Fri Apr 01, 2011 7:21 pm Post subject: missing kernel modules in 2.6.35.12 |
 |
|
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:
| Code: | #
# 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! |
|
| Back to top |
|
 |
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23062
|
| Posted: Sat Apr 02, 2011 4:29 am Post subject: |
|
|
| As I read the kernel history, these modules are not present until some time in the v2.6.36 merge window. If you had them in a v2.6.35 kernel, it is likely that someone backported them for you. The Kconfig items you mention were added in V4L/DVB: staging/lirc: wire up Kconfig and Makefile bits. |
|
| Back to top |
|
|
graysky
Tux's lil' helper
Joined: 25 Nov 2006
Posts: 118
Location: above the flames and the ashes
|
| Posted: Sat Apr 02, 2011 9:52 am Post subject: |
|
|
| Hu wrote: | | As I read the kernel history, these modules are not present until some time in the v2.6.36 merge window. If you had them in a v2.6.35 kernel, it is likely that someone backported them for you. The Kconfig items you mention were added in V4L/DVB: staging/lirc: wire up Kconfig and Makefile bits. |
Thank you for this information! The next logical question for me is how would one go about back-porting the git commit you posted into the current 2.6.35.12 source tree? Is this a major undertaking? |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 23062
|
| Posted: Sat Apr 02, 2011 6:00 pm Post subject: |
|
|
It depends. In the simple case, it might be as easy as tracking down every commit which touched those files and applying it to your base v2.6.35.12 tree, in order. However, this may fail if the resulting lirc code depends on some general purpose feature added after v2.6.35 was released. Such a failure will usually, but not always, manifest as a failure to compile. If you are very unlucky, lirc will depend on changed semantics of some other kernel component and will fail at runtime if the old semantics are used instead.
Depending on the time and effort you want to spend on this, it may be easier to pick a newer kernel where the lirc modules are naturally included. |
|
| Back to top |
|
|
|
Kernel & Hardware
