[i2c] Problem with restricted I2C algorithms in kernel 2.6.26!
khali at linux-fr.org
Thu Aug 7 20:49:00 CEST 2008
On Thu, 7 Aug 2008 20:39:44 +0200, Sam Ravnborg wrote:
> > Alternatively, I am curious if our build system couldn't allow 3rd
> > party drivers to select in-tree modules. Obviously this would require
> > the complete kernel source tree to be available, instead of just the
> > header and config files as is usually the case. Sam, is this possible
> > to do that at this time? If not, is this something that could be
> > implemented, or is this too much work for the thin benefit?
> In general I recommnd to have the full kernel source available
> simply because we have no in-kernel solution to create the required
> set of files to build external modules.
> And today there is no way to hook into the kernel configuration
> for an external module. First of we cannot allow changes in
> the build kernel module as this would destroy module versioning
> for instance.
> And in this case you ask because you would change the kernel
> And I fail to see why this stuff cannot be done inside the
> kernel source tree. Merging new kernel updates should be absolutely
> trivial and then the drivers are better prepared for upstream anyway.
OK, thanks for the clarification.
Maybe one way would be for the external module build system to copy (or
link to) the missing driver source from the kernel tree and build it
locally with the rest of the external drivers, if it wasn't enabled in
the original kernel configuration and they need it. That's probably
just a couple lines of shell script, should be pretty easy. Obviously
this only works for kernel options which only select a given driver and
have no side effect on the rest of the kernel. And this is more
user-friendly than having the user check its kernel configuration and
rebuild his/her kernel.
Just a thought anyway...
More information about the i2c