[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150520212224.GB3244@piout.net>
Date: Wed, 20 May 2015 23:22:24 +0200
From: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
To: Robert Nelson <robertcnelson@...il.com>
Cc: Kevin Hilman <khilman@...nel.org>,
Nicolas Ferre <nicolas.ferre@...el.com>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Boris BREZILLON <boris.brezillon@...e-electrons.com>,
lkml <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: Add Atmel SAMA5 family
Hi,
On 20/05/2015 at 10:18:16 -0500, Robert Nelson wrote :
> On Wed, May 20, 2015 at 9:08 AM, Alexandre Belloni
> <alexandre.belloni@...e-electrons.com> wrote:
> > 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,
>
> considering all the old boot-loaders, have you thought about adding a
> compatibility config similar to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=00648d0282dcca1da453c0b20d27e24bf901a854
>
We are not there yet. sama5_defconfig and at91_dt_defconfig will still
produce kernels using ttyS and not ttyAT. The switch will not happen
until you set CONFIG_SERIAL_ATMEL_TTYAT which has been present since
2.6.19. The issue is that it is mandatory to use it in a multi_v7
configuration because the 8250 driver is compiled in and is conflicting.
Kevin and Tyler jumped on the introduction of sama5 in multi_v7 and got
the issue. As long as you stick to the at91 only configurations, you
will be fine ;)
I hope this clarifies the thing :)
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists