* David Brownell [EMAIL PROTECTED] [080808 02:51]:
On Thursday 07 August 2008, Tony Lindgren wrote:
Two problems on the OSK5912:
- cpufreq oopses on boot
- continuous i2c overflow errors
ISTR both of these bugs are in mainline too. I'd say the
I2C regression is higher
* David Brownell [EMAIL PROTECTED] [080807 02:30]:
On Tuesday 05 August 2008, Tony Lindgren wrote:
Also please check that things work for your board,
let's try to tag v2.6.26-omap1 within next few days so we can
move on again.
Two problems on the OSK5912:
- cpufreq oopses on boot
-
On Thursday 07 August 2008, Tony Lindgren wrote:
Two problems on the OSK5912:
- cpufreq oopses on boot
- continuous i2c overflow errors
ISTR both of these bugs are in mainline too. I'd say the
I2C regression is higher priority.
Hmm, I wonder what has broken I2C?
Seems
On Tue, Aug 5, 2008 at 11:41 PM, Dirk Behme [EMAIL PROTECTED] wrote:
Gadiyar, Anand wrote:
Hi all,
I've pushed all the patches I have in my omap inbox, except for
the omap serial driver that I want to look more.
I've tried to comment on the ones that did not get pushed, then
erased
On an omap3evm with the defconfig, the kernel is failing to identify a
jffs2 filesystem. It's booting from NFS just fine.
I had built the latest code checked into linux-omap last week - file
system booting had been working, IIRC. Loading TI reference 2.6.22
kernel finds the file system
Hi all,
I've pushed all the patches I have in my omap inbox, except for
the omap serial driver that I want to look more.
I've tried to comment on the ones that did not get pushed, then
erased everything from my omap inbox. Some drivers should get
integrated via other mailing lists, and
Gadiyar, Anand wrote:
Hi all,
I've pushed all the patches I have in my omap inbox, except for
the omap serial driver that I want to look more.
I've tried to comment on the ones that did not get pushed, then
erased everything from my omap inbox. Some drivers should get
integrated via other
