Re: [i2c] Problem with restricted I2C algorithms in kernel 2.6.26!

[Trent Piepho <xyzzy@speakeasy.org>]

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
first?

Why does the kernel build system support building out of tree modules if no
one should do it?

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.