From: viresh.kumar@st.com (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 5/7] ARM: SPEAr3xx: Add device-tree support to SPEAr3xx architecture
Date: Thu, 29 Mar 2012 16:14:46 +0530 [thread overview]
Message-ID: <4F743D1E.9030209@st.com> (raw)
In-Reply-To: <201203290753.04758.arnd@arndb.de>
On 3/29/2012 1:23 PM, Arnd Bergmann wrote:
> That should not really be a concern, you only waste a little bit of
> the vmalloc space that you gained recently when ioremap was changed.
> Nothing should ever be able to get to those pointers other than by
> calling ioremap, so it doesn't hurt to have them mapped, except for
> the very unlikely scenario that you get a wild pointer dereference
> in the kernel that would otherwise result in an oops.
Ok. I will create two 16M mappings for now:
PHYSICAL VIRTUAL
0xD0000000 - 0xD1000000 0xFD000000
0xFC000000 - 0xFD000000 0xFC000000
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar-qxv4g6HH51o@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: "devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org"
<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>,
spear-devel <spear-devel-nkJGhpqTU55BDgjK7y7TUQ@public.gmane.org>,
"viresh.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<viresh.linux-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"sr-ynQEQJNshbs@public.gmane.org"
<sr-ynQEQJNshbs@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH V2 5/7] ARM: SPEAr3xx: Add device-tree support to SPEAr3xx architecture
Date: Thu, 29 Mar 2012 16:14:46 +0530 [thread overview]
Message-ID: <4F743D1E.9030209@st.com> (raw)
In-Reply-To: <201203290753.04758.arnd-r2nGTMty4D4@public.gmane.org>
On 3/29/2012 1:23 PM, Arnd Bergmann wrote:
> That should not really be a concern, you only waste a little bit of
> the vmalloc space that you gained recently when ioremap was changed.
> Nothing should ever be able to get to those pointers other than by
> calling ioremap, so it doesn't hurt to have them mapped, except for
> the very unlikely scenario that you get a wild pointer dereference
> in the kernel that would otherwise result in an oops.
Ok. I will create two 16M mappings for now:
PHYSICAL VIRTUAL
0xD0000000 - 0xD1000000 0xFD000000
0xFC000000 - 0xFD000000 0xFC000000
--
viresh
next prev parent reply other threads:[~2012-03-29 10:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 9:30 [PATCH V2 0/7] SPEAr DT support updates Viresh Kumar
2012-03-28 9:30 ` Viresh Kumar
2012-03-28 9:30 ` [PATCH V2 1/7] SPEAr: Use CLKDEV_INIT for defining clk_lookups Viresh Kumar
2012-03-28 9:30 ` Viresh Kumar
2012-03-28 9:30 ` [PATCH V2 2/7] SPEAr3xx: Add clock instance of usb hosts - ehci and ohci 0 and 1 Viresh Kumar
2012-03-28 9:30 ` Viresh Kumar
2012-03-28 9:30 ` [PATCH V2 3/7] SPEAr6xx: Add compilation support for dtbs using 'make dtbs' Viresh Kumar
2012-03-28 9:30 ` Viresh Kumar
2012-03-28 9:41 ` [PATCH V2 4/7] SPEAr3xx: Replace printk() with pr_*() Viresh Kumar
2012-03-28 9:41 ` Viresh Kumar
2012-03-28 9:41 ` [PATCH V2 5/7] ARM: SPEAr3xx: Add device-tree support to SPEAr3xx architecture Viresh Kumar
2012-03-28 9:41 ` Viresh Kumar
2012-03-28 12:27 ` Arnd Bergmann
2012-03-28 12:27 ` Arnd Bergmann
2012-03-29 6:39 ` Viresh Kumar
2012-03-29 6:39 ` Viresh Kumar
2012-03-29 7:53 ` Arnd Bergmann
2012-03-29 7:53 ` Arnd Bergmann
2012-03-29 10:44 ` Viresh Kumar [this message]
2012-03-29 10:44 ` Viresh Kumar
2012-03-28 9:41 ` [PATCH V2 6/7] SPEAr: Add PL080 DMA support for 3xx and 6xx Viresh Kumar
2012-03-28 9:41 ` Viresh Kumar
2012-03-28 9:41 ` [PATCH V2 7/7] SPEAr: Update defconfigs Viresh Kumar
2012-03-28 9:41 ` Viresh Kumar
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=4F743D1E.9030209@st.com \
--to=viresh.kumar@st.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.