SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: Ecovec (SH7724) board doesn't work on latest linus tree
Date: Tue, 04 Oct 2011 23:16:10 +0000	[thread overview]
Message-ID: <20111004231607.GA28029@verge.net.au> (raw)
In-Reply-To: <w3pvcwf5xuu.wl%kuninori.morimoto.gx@renesas.com>

On Mon, Sep 19, 2011 at 07:08:18PM -0700, Kuninori Morimoto wrote:
> 
> Hi Paul, Iwamatsu-san
> 
> > On Thu, Sep 08, 2011 at 05:52:11PM +0900, Nobuhiro Iwamatsu wrote:
> > > Your patch does not seem to have a meaning.
> > > In the case of 29bit, CAC/UNCAC_ADDR may not return a right address.
> > > I think that it is to use P1SEGADDR, and P2SEGADDR in CAC/UNCAC_ADDR
> > > to easily revise this.
> > > I attached my patch.
> > > 
> > Morimoto-san, does this fix your issue? If you can provide your Tested-by
> > for this then I'll queue it up and get it off to Linus.
> 
> Thank you.
> 
> I tested this patch on linus/master.
> And this patch solved Ecovec board boot issue.
> 
> # I tested it on mackerel (SH7372) board too.
> # It works well
>  
> Tested-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>

FWIW, this resolved a failure to boot on Ecovec for me too.

Tested-by: Simon Horman <horms@verge.net.au>

  parent reply	other threads:[~2011-10-04 23:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09  6:21 Ecovec (SH7724) board doesn't work on latest linus tree Kuninori Morimoto
2011-06-09  6:31 ` Paul Mundt
2011-06-09  6:42 ` Kuninori Morimoto
2011-07-05  7:52 ` kuninori.morimoto.gx
2011-08-31 15:07 ` Yutaro Ebihara
2011-09-01  1:28 ` Kuninori Morimoto
2011-09-01  1:45 ` Kuninori Morimoto
2011-09-08  8:52 ` Nobuhiro Iwamatsu
2011-09-20  0:54 ` Paul Mundt
2011-09-20  2:08 ` Kuninori Morimoto
2011-09-20  3:10 ` Paul Mundt
2011-10-04 23:16 ` Simon Horman [this message]
2011-11-04 13:23 ` Paul Mundt

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=20111004231607.GA28029@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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