[i2c] Problem with restricted I2C algorithms in kernel 2.6.26!
khali at linux-fr.org
Thu Aug 7 18:14:16 CEST 2008
On Thu, 7 Aug 2008 09:01:35 -0700 (PDT), Trent Piepho wrote:
> On Thu, 7 Aug 2008, Jean Delvare wrote:
> > > One of the biggest reasons people choose to compile things from
> > > cvs/svn/mercurial/etc. is because it gives them access to newer bug
> > > fixes and support for things not yet present in the kernel source. A
> > > perfect example, the multiproto dvb driver tree. Users wanting
> > > support for dvb-s2 devices have to compile drivers outside of the
> > > kernel because it's simply not available in the kernel and won't be
> > > for some time.
> > So basically you are telling that "thanks" to drivers being maintainers
> > in external repositories, bugs are not fixed in the upstream kernel in
> > a timely manner, and new features take more time to go there too? That
> > must be the reason why kernel developers and users alike don't like
> > external repositories in the first place.
> Code needs to get testing before it's put in the kernel. How's that
> supposed to happen if it's not made available outside the kernel tree
> Why does the kernel build system support building out of tree modules if no
> one should do it?
I guess it can be convenient at times. But people doing that shouldn't
dare to complain that everything isn't perfect for them.
> Maybe an option to turn i2c algorithms on could do into the Library
> Routines menu. There are already options for things like the crc routines
> here so they can be turned on if an out of tree driver needs them but
> nothing in the kernel does.
Having I2C-specific options selectable under the Library menu would
probably be even more confusing. However, it would be possible to do
something similar under the I2C menu. Much like
CONFIG_VIDEO_HELPER_CHIPS_AUTO does for the V4L subsystem:
CONFIG_I2C_ALGOS_AUTO would default to Y and would hide I2C algo driver
selection (as is the case in 2.6.26), changing it to N would present
the old menu for users to select the aldo drivers manually (as was the
case in 2.6.25.)
Which doesn't change my point that most people complaining about the
change would rather merge their drivers in the upstream kernel.
More information about the i2c