From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] ARM: ixp4xx: move fixed mapping of internal devices into vmalloc region
Date: Fri, 7 Sep 2012 12:23:29 +0000 [thread overview]
Message-ID: <201209071223.30275.arnd@arndb.de> (raw)
In-Reply-To: <1346996400-5824-1-git-send-email-gerg@snapgear.com>
On Friday 07 September 2012, gerg at snapgear.com wrote:
>
> From: Greg Ungerer <gerg@uclinux•org>
>
> The current fixed physical/virtual mappings for the internal peripherals
> of the ixp4xx SoC devices is using a virtual address outside of the vmalloc
> region. This results in kernel warnings like this on the boot console:
>
> BUG: mapping for 0xc8000000 at 0xffbeb000 out of vmalloc space
> BUG: mapping for 0xc4000000 at 0xffbfe000 out of vmalloc space
> BUG: mapping for 0xc0000000 at 0xffbff000 out of vmalloc space
>
> The virtual kernel memory layout lists this for the vmalloc region:
>
> ...
> vmalloc : 0xc2800000 - 0xff000000 ( 968 MB)
> ...
>
> With a little adjustment to the virtual address used we can map these
> internal devices in the vmalloc region.
>
> Signed-off-by: Greg Ungerer <gerg@uclinux•org>
Acked-by: Arnd Bergmann <arnd@arndb•de>
Imre, Krzysztof: do you prefer to take this patch into a branch of yours
and send a pull request, or should we just apply it directly into arm-soc.
In the former case, can you provide an Ack?
Arnd
next prev parent reply other threads:[~2012-09-07 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 5:40 [PATCH] ARM: ixp4xx: move fixed mapping of internal devices into vmalloc region gerg at snapgear.com
2012-09-07 12:23 ` Arnd Bergmann [this message]
2012-09-07 13:13 ` Krzysztof Halasa
2012-09-07 13:23 ` Arnd Bergmann
2012-09-07 14:15 ` Greg Ungerer
-- strict thread matches above, loose matches on Subject: below --
2012-08-14 5:48 gerg at snapgear.com
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=201209071223.30275.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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