From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 6/6] ARM: Add mvebu_defconfig
Date: Tue, 23 Sep 2014 07:58:04 +0200 [thread overview]
Message-ID: <20140923055804.GQ4992@pengutronix.de> (raw)
In-Reply-To: <541DB84C.2020805@gmail.com>
On Sat, Sep 20, 2014 at 07:24:28PM +0200, Sebastian Hesselbarth wrote:
> On 09/17/2014 10:22 PM, Sebastian Hesselbarth wrote:
> > From: Sascha Hauer <s.hauer@pengutronix.de>
> >
> > This adds a mvebu_defconfig which enables all mvebu based boards.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> > ---
> ...
> > ---
> > arch/arm/configs/mvebu_defconfig | 123 +++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 123 insertions(+)
> > create mode 100644 arch/arm/configs/mvebu_defconfig
> >
> > diff --git a/arch/arm/configs/mvebu_defconfig b/arch/arm/configs/mvebu_defconfig
> > new file mode 100644
> > index 000000000000..26be4ecfe022
> > --- /dev/null
> > +++ b/arch/arm/configs/mvebu_defconfig
> > @@ -0,0 +1,123 @@
> [...]
> > +CONFIG_MMU=y
>
> Sascha,
>
> can you please drop CONFIG_MMU for mvebu_defconfig for now? I did some
> more testing today and realized that Armada 370 and XP are CPU_V7 but
> have a different cache controller. We currently have no support for
> Marvell Aurora and therefore flush/inv ranges will not work and break
> any driver using dma_flush/inv_range.
Ok, just did that.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-09-23 5:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 20:22 [PATCH v2 0/6] mvebu multi SoC support Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 1/6] ARM: mvebu: Add common reset_cpu function Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 2/6] ARM: mvebu: Add machine compatible to mbus ranges Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 3/6] ARM: mvebu: Simplify memory init order Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 4/6] ARM: mvebu: Check for correct SoC in of_fixup callback Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 5/6] ARM: mvebu: Allow multiple SoCs Sebastian Hesselbarth
2014-09-17 20:22 ` [PATCH v2 6/6] ARM: Add mvebu_defconfig Sebastian Hesselbarth
2014-09-20 17:24 ` Sebastian Hesselbarth
2014-09-23 5:58 ` Sascha Hauer [this message]
2014-09-19 5:47 ` [PATCH v2 0/6] mvebu multi SoC support Sascha Hauer
2014-09-19 6:44 ` Sebastian Hesselbarth
2014-09-19 7:55 ` Sascha Hauer
2014-09-19 8:25 ` Sebastian Hesselbarth
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=20140923055804.GQ4992@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=sebastian.hesselbarth@gmail.com \
/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