From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>,
afzal mohammed <afzal.mohd.ma@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/3] ARM: !MMU: v7-A support, dynamic vectors base handling
Date: Wed, 1 Feb 2017 10:33:17 +0000 [thread overview]
Message-ID: <0ffdd659-9c6d-900b-44d6-646c50730110@arm.com> (raw)
In-Reply-To: <20170131192438.GB27312@n2100.armlinux.org.uk>
On 31/01/17 19:24, Russell King - ARM Linux wrote:
> On Tue, Jan 31, 2017 at 06:34:46PM +0530, afzal mohammed wrote:
>> Hi,
>>
>> ARM core changes to support !MMU Kernel on v7-A MMU processors.
>>
>> Based on the feedback from Russell, it was decided to handle vector
>> base dynamically in C for no-MMU & work towards the the goal of
>> removing VECTORS_BASE from Kconfig.
>
> Looks good from my perspective. If Vladimir can reply about patch 2,
> then I think we'll be good to go with these. Thanks.
>
My R-class and M-class setups continue to work with this series applied on
top of next-20170201 plus following fixup for PATCH 2/3
-#define VECTORS_BASE UL(0xffff0000)
-
- /*
- * We fix the TCM memories max 32 KiB ITCM resp DTCM at these
- * locations
+ #ifdef CONFIG_XIP_KERNEL
+ #define KERNEL_START _sdata
+ #else
FWIW: Tested-by: Vladimir Murzin <vladimir.murzin@arm.com>
Thanks!
Vladimir
next prev parent reply other threads:[~2017-02-01 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 13:04 afzal mohammed
2017-01-31 13:06 ` [PATCH v3 1/3] ARM: nommu: dynamic exception base address setting afzal mohammed
2017-01-31 13:06 ` [PATCH v3 2/3] ARM: nommu: display vectors base afzal mohammed
2017-01-31 13:07 ` [PATCH v3 3/3] ARM: nommu: remove Hivecs configuration is asm afzal mohammed
2017-01-31 19:24 ` [PATCH v3 0/3] ARM: !MMU: v7-A support, dynamic vectors base handling Russell King - ARM Linux
2017-02-01 10:33 ` Vladimir Murzin [this message]
2017-02-01 13:10 ` Afzal Mohammed
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=0ffdd659-9c6d-900b-44d6-646c50730110@arm.com \
--to=vladimir.murzin@arm.com \
--cc=afzal.mohd.ma@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®