From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: Armada XP doesn't boot in v3.12-rc3
Date: Wed, 2 Oct 2013 17:25:48 -0300 [thread overview]
Message-ID: <20131002202547.GA10645@localhost> (raw)
In-Reply-To: <CAFJTrDsTmSzFEX7XVqnw4=vYiBdqNeLDQuWFotSEZqGsFxT9sA@mail.gmail.com>
Hi Matthew:
On Wed, Oct 02, 2013 at 04:55:25PM +0100, Matthew Minter wrote:
[...]
>
> I have tried a number of configurations including the defaults for the
> mach and various settings including turning CONFIG_HAVE_ARM_ARCH_TIMER
> on and off.
>
> Some configurations result in no output after uBoot's booting kernel
> line, but some reach theline "calibrating timer loop" then hang
> indefinitely.
>
Yup, that's the two different bugs the patches should fix.
> I am now trying the fixes branch at
> git://git.infradead.org/linux-mvebu.git (thanks Ezequiel) to see if
> that contains a solution. Once I have tried that I shall see what
> changes it made and mail back any results. (I am talking to the board
> down a serial over USB connection so can get a fair amount of
> diagnostics from the early printk system).
>
Please test git://git.infradead.org/linux-mvebu.git or some recent
linux-next. You should be able to boot with/without CONFIG_HAVE_ARM_ARCH_TIMER.
I expect all the fixes land in -rc4, which means mainline should be
fixed by next week.
Let me know any problems!
Thanks a lot for reporting!
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-02 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 10:39 Armada XP doesn't boot in v3.12-rc3 Matthew Minter
2013-10-02 12:43 ` Jason Cooper
2013-10-02 13:51 ` Ezequiel Garcia
2013-10-02 15:55 ` Matthew Minter
2013-10-02 16:07 ` Thomas Petazzoni
2013-10-02 16:42 ` Ezequiel Garcia
2013-10-02 20:25 ` Ezequiel Garcia [this message]
2013-10-03 9:41 ` Matthew Minter
2013-10-03 10:28 ` Thomas Petazzoni
2013-10-03 11:45 ` Jason Cooper
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=20131002202547.GA10645@localhost \
--to=ezequiel.garcia@free-electrons.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 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.