From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL V5 0/7] ARM: kirkwood/dove/mvebu changes for v3.7
Date: Mon, 24 Sep 2012 07:23:01 +0200 [thread overview]
Message-ID: <20120924052301.GE14266@lunn.ch> (raw)
In-Reply-To: <20120922171554.GE5469@titan.lakedaemon.net>
Hi Arnd, Olof, Jason.
I tested arm-soc/late/kirkwood on an orion5x board. There is an
unrelated problem, which i should of really seen earlier....
ERROR: 256 KiB atomic DMA coherent pool is too small!
Please increase it with coherent_pool= kernel parameter!
We had the same problem with kirkwood. I will submit a patch against
3.6-rc7. Is there still time for that? Otherwise it would be good to
have in 3.7 and cc: stable so 3.6.1 gets the fix.
When i increase the coherent pool size on the command line, it boots
O.K. I don't have any PCI devices on this board, but the two root
controllers are listed by lspci.
Tested-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2012-09-24 5:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 17:15 [GIT PULL V5 0/7] ARM: kirkwood/dove/mvebu changes for v3.7 Jason Cooper
2012-09-22 17:20 ` [GIT PULL V5 1/7] ARM: kirkwood: board " Jason Cooper
2012-09-22 17:22 ` [GIT PULL V5 2/7] ARM: kirkwood defconfig " Jason Cooper
2012-09-22 17:24 ` [GIT PULL V5 3/7] ARM: kirkwood dt " Jason Cooper
2012-09-22 17:27 ` [GIT PULL V5 4/7] ARM: kirkwood cleanup " Jason Cooper
2012-09-22 17:31 ` [GIT PULL V5 5/7] ARM: kirkwood platform_data " Jason Cooper
2012-09-22 21:37 ` Olof Johansson
2012-09-22 22:32 ` Jason Cooper
2012-09-22 17:33 ` [GIT PULL V5 6/7] ARM: kirkwood addr_decode " Jason Cooper
2012-09-22 17:36 ` [GIT PULL V5 7/7] ARM: kirkwood drivers " Jason Cooper
2012-09-22 21:36 ` [GIT PULL V5 0/7] ARM: kirkwood/dove/mvebu " Olof Johansson
2012-09-22 22:29 ` Jason Cooper
2012-09-24 5:23 ` Andrew Lunn [this message]
2012-09-24 5:37 ` Olof Johansson
2012-09-24 5:58 ` Andrew Lunn
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=20120924052301.GE14266@lunn.ch \
--to=andrew@lunn.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).