All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Pais, Allen" <allen.pais@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Pandita, Vikram" <vikram.pandita@ti.com>
Subject: Re: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3
Date: Mon, 22 Mar 2010 14:20:25 -0700	[thread overview]
Message-ID: <20100322212025.GW11448@atomide.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E94026F126B9C@dbde02.ent.ti.com>

* Pais, Allen <allen.pais@ti.com> [100322 00:14]:
>  
> > > > Hi all,
> > > > 
> > > > Got a zoom3 finally! This is needed to boot with DEBUG_LL 
> > + earlyprintk.
> > > 
> > > And of course it won't compile because of a missing #.
> > > Here's the working version.
> > 
> > One more time. Looks like what I posted is not enough, we
> > also need to make sure the mapping does not overlap with
> > other regions. So basically we can't use 0xfb000000 like
> > we currently have, let's use 0xf7000000 instead unless
> > somebody has better ideas.
> 
>  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?

BTW, I'm still seeing mux errors on zoom3, have not yet
looked into those.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: Fix DEBUG_LL for omap zoom2/3
Date: Mon, 22 Mar 2010 14:20:25 -0700	[thread overview]
Message-ID: <20100322212025.GW11448@atomide.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E94026F126B9C@dbde02.ent.ti.com>

* Pais, Allen <allen.pais@ti.com> [100322 00:14]:
>  
> > > > Hi all,
> > > > 
> > > > Got a zoom3 finally! This is needed to boot with DEBUG_LL 
> > + earlyprintk.
> > > 
> > > And of course it won't compile because of a missing #.
> > > Here's the working version.
> > 
> > One more time. Looks like what I posted is not enough, we
> > also need to make sure the mapping does not overlap with
> > other regions. So basically we can't use 0xfb000000 like
> > we currently have, let's use 0xf7000000 instead unless
> > somebody has better ideas.
> 
>  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?

BTW, I'm still seeing mux errors on zoom3, have not yet
looked into those.

Regards,

Tony

  reply	other threads:[~2010-03-22 21:18 UTC|newest]

Thread overview: 44+ 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:36 ` Tony Lindgren
2010-03-20  0:47 ` Tony Lindgren
2010-03-20  0:47   ` Tony Lindgren
2010-03-20  2:48   ` Tony Lindgren
2010-03-20  2:48     ` Tony Lindgren
2010-03-20  3:02     ` Tony Lindgren
2010-03-20  3:02       ` Tony Lindgren
2010-03-20 23:00       ` Pandita, Vikram
2010-03-20 23:00         ` Pandita, Vikram
2010-03-23  0:09         ` Tony Lindgren
2010-03-23  0:09           ` Tony Lindgren
2010-03-22  7:18     ` Pais, Allen
2010-03-22  7:18       ` Pais, Allen
2010-03-22 21:20       ` Tony Lindgren [this message]
2010-03-22 21:20         ` Tony Lindgren
2010-03-23  1:25         ` Tony Lindgren
2010-03-23  1:25           ` Tony Lindgren
2010-03-23  5:46         ` Pais, Allen
2010-03-23  5:46           ` Pais, Allen
2010-03-23 15:27           ` Tony Lindgren
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-23 22:49               ` Nishanth Menon
2010-03-24 15:31               ` Madhusudhan
2010-03-24 15:31                 ` Madhusudhan
2010-03-24 15:32               ` Madhusudhan
2010-03-24 15:32                 ` Madhusudhan
2010-03-24 15:35               ` Madhusudhan
2010-03-24 15:35                 ` Madhusudhan
2010-03-24 15:52                 ` Laurent Epinat
2010-03-24 15:52                   ` Laurent Epinat
2010-03-30 23:35             ` [PATCH] arm: Fix DEBUG_LL for omap zoom2/3 Madhusudhan
2010-03-30 23:35               ` Madhusudhan
2010-03-31  6:11               ` G, Manjunath Kondaiah
2010-03-31  6:11                 ` G, Manjunath Kondaiah
2010-03-31 16:46                 ` Madhusudhan
2010-03-31 16:46                   ` Madhusudhan
2010-04-06 16:51             ` Aguirre, Sergio
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=20100322212025.GW11448@atomide.com \
    --to=tony@atomide.com \
    --cc=allen.pais@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=vikram.pandita@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.