And I **really** hope this gets merged into 2.6.18 since virtually
no OMAP board is very usable without it. I2C is one of the main
missing pieces(*) ... can whoever's managing I2C merges please
expedite this?
I just tried building an OSK config against RC3 and found at least
five will-not-build errors in the kernel.org tree. The reason for
this is basically that folk have no option except the linux-omap
tree, since there's no point in trying to use the kernel.org version
until the I2C driver finally gets merged ... so such bugs won't get
fixed. Needless to say, this is not the desired development process.
- Dave
(*) I submitted the then-current I2C driver over a year ago, but
after a few months of inaction I found that it was dropped
(or rejected?) by the I2C list software. Of course at that
point I no longer had time to resubmit the current code ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
