From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: Nicolas Ferre <nicolas.ferre@atmel.com>,
Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
lkml <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family
Date: Wed, 20 May 2015 16:08:56 +0200 [thread overview]
Message-ID: <20150520140856.GE3907@piout.net> (raw)
In-Reply-To: <CAMAWPa95VTM+VgNpcs1oZwX9NqzrL1JeNy=MqL0Zo3JP=svyUQ@mail.gmail.com>
Hi,
On 20/05/2015 at 06:53:50 -0700, Kevin Hilman wrote :
> FYI... This patch is now in linux-next, and boot tests for all the
> sama5d[34] boards in kernelci.org have failed to boot.
>
> http://kernelci.org/boot/all/job/next/kernel/next-20150520/
>
Hum, I'm pretty sure you see the heartbeat led blinking ;)
I think I told you a while ago on IRC and this is part of the commit
message. You have to use ttyAT0 instead of ttyS0 in your bootargs. I'm
not sure how I can make that more obvious, I'm open to any idea.
I'm planning to send a series adding stdout-path to the atmel boards
when I'm back next week. Hopefully this will solve that issue.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-05-20 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 9:01 [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family Alexandre Belloni
2015-05-19 9:15 ` Nicolas Ferre
2015-05-19 11:04 ` Arnd Bergmann
2015-05-19 12:33 ` Alexandre Belloni
2015-05-19 13:02 ` Nicolas Ferre
2015-05-19 13:28 ` Nicolas Ferre
2015-05-19 13:53 ` Nicolas Ferre
2015-05-20 13:53 ` Kevin Hilman
2015-05-20 14:08 ` Alexandre Belloni [this message]
2015-05-20 14:59 ` Kevin Hilman
2015-05-20 21:29 ` Alexandre Belloni
2015-05-20 15:18 ` Robert Nelson
2015-05-20 21:22 ` Alexandre Belloni
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=20150520140856.GE3907@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=arnd@arndb.de \
--cc=boris.brezillon@free-electrons.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
/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