> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Tony Lindgren > Sent: Tuesday, March 23, 2010 10:27 AM > To: Pais, Allen > Cc: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux-omap@xxxxxxxxxxxxxxx; > Pandita, Vikram > Subject: Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 > > * Pais, Allen <allen.pais@xxxxxx> [100322 22:42]: > > > > > > > > With this patch[DEBUG_LL + earlyprintk], > > > > I still haven't been able to boot the kernel. > > > > Is it working on your side. > > > > > > > > The commit am using is : a842b5f9ce70e1b738eabb4d719860070180ed1c > > > > > > I think you will also need the 3630 serial fixes series posted > > > recently. > > > > > > I just merged those into omap-fixes-for-linus (and master) > > > branch(es). Maybe give it a try with at commit > > > b3c7740a120c8a7775cb63b4d094466da5c01692 + this patch? > > > > Thanks, I'll pull in those fixes. > > I believe the mux errors are fixed. Have a look at > > http://dev.omapzoom.org/?p=manju/kernel-omap3- > dev.git;a=commit;h=3499f5023ee90dc6ee3868a3147b87fe22a1d9b7 > > > > Patch must have been missed some how. > > OK, we really should get fixes like that to mainline kernel ASAP > to avoid duplicating the effort. > > Then at least one issue remains for zoom3 to be usable.. > I'm getting tons of MMC errors trying to mount root on it: > > mmcblk1: error -110 transferring data, sector 2097024, nr 8, card status > 0x900 > end_request: I/O error, dev mmcblk1, sector 2097024 > ... > > Any ideas if that's fixed somewhere also? > Tony, What is the branch on which the kernel is built? I tried the master branch and the omap-fixes-for-linus both does not seem to boot Zoom3. Regards, Madhu > Regards, > > Tony > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
