From: madhu.cr@ti.com (Madhusudhan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3
Date: Tue, 30 Mar 2010 18:35:19 -0500 [thread overview]
Message-ID: <005401cad061$a8db7440$544ff780@am.dhcp.ti.com> (raw)
In-Reply-To: <20100323152709.GD11448@atomide.com>
> -----Original Message-----
> From: linux-omap-owner at vger.kernel.org [mailto:linux-omap-
> owner at vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Tuesday, March 23, 2010 10:27 AM
> To: Pais, Allen
> Cc: linux-arm-kernel at lists.infradead.org; linux-omap at vger.kernel.org;
> Pandita, Vikram
> Subject: Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3
>
> * Pais, Allen <allen.pais@ti.com> [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 at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-30 23:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 0:36 [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 Tony Lindgren
2010-03-20 0:47 ` Tony Lindgren
2010-03-20 2:48 ` Tony Lindgren
2010-03-20 3:02 ` Tony Lindgren
2010-03-20 23:00 ` Pandita, Vikram
2010-03-23 0:09 ` Tony Lindgren
2010-03-22 7:18 ` Pais, Allen
2010-03-22 21:20 ` Tony Lindgren
2010-03-23 1:25 ` Tony Lindgren
2010-03-23 5:46 ` Pais, Allen
2010-03-23 15:27 ` Tony Lindgren
2010-03-23 22:49 ` mmc errors (was Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3) Nishanth Menon
2010-03-24 15:31 ` Madhusudhan
2010-03-24 15:32 ` Madhusudhan
2010-03-24 15:35 ` Madhusudhan
2010-03-24 15:52 ` Laurent Epinat
2010-03-30 23:35 ` Madhusudhan [this message]
2010-03-31 6:11 ` [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 G, Manjunath Kondaiah
2010-03-31 16:46 ` Madhusudhan
2010-04-06 16:51 ` Aguirre, Sergio
-- strict thread matches above, loose matches on Subject: below --
2010-03-20 0:18 Tony Lindgren
2010-03-20 0:18 Tony Lindgren
2010-03-20 0:18 Tony Lindgren
2010-03-20 0:18 Tony Lindgren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005401cad061$a8db7440$544ff780@am.dhcp.ti.com' \
--to=madhu.cr@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).