From: Ben Dooks <ben.dooks@codethink.co.uk>
To: linux-sh@vger.kernel.org
Subject: Re: lager - non-booting latest horms' devel branch
Date: Thu, 09 Jan 2014 16:01:45 +0000 [thread overview]
Message-ID: <52CEC7E9.4050402@codethink.co.uk> (raw)
In-Reply-To: <52CE8BC0.7060306@codethink.co.uk>
On 09/01/14 11:45, Ben Dooks wrote:
> I am using the devel branch from Simon Horms' git tree, SHA1
> 3da593ea7d797d9f59bd6ed1ee629fab681d7a23 and not seeing a
> boot when using the multi arch defconfig and device-tree.
>
> The board does not produce any console output so I am not
> sure what is going on. Has anyone else had issues with using
> the fdt-only boot?
>
> The arch setup is:
>
> CONFIG_ARCH_SHMOBILE=y
> CONFIG_ARCH_SHMOBILE_MULTI=y
> CONFIG_MACH_LAGER=y
I've finally sorted this out, my install scripts where copying the
old reference dtb instead of the new non-reference version.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
prev parent reply other threads:[~2014-01-09 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 11:45 lager - non-booting latest horms' devel branch Ben Dooks
2014-01-09 12:21 ` Geert Uytterhoeven
2014-01-09 12:30 ` Ben Dooks
2014-01-09 14:42 ` Ben Dooks
2014-01-09 16:01 ` Ben Dooks [this message]
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=52CEC7E9.4050402@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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 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.