linux-kernel - Re: [PATCH defconfig v8] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 20 May 2015 23:25:44 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-arm-kernel@...ts.infradead.org
Cc:	Stefan Agner <stefan@...er.ch>, mcoquelin.stm32@...il.com,
	linux@....linux.org.uk, jason@...edaemon.net, marc.zyngier@....com,
	linux-kernel@...r.kernel.org, kernel@...gutronix.de,
	u.kleine-koenig@...gutronix.de, olof@...om.net,
	shawn.guo@...aro.org
Subject: Re: [PATCH defconfig v8] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4

On Wednesday 20 May 2015 00:06:22 Stefan Agner wrote:
> Add defconfig for Linux on Vybrid (vf610) on the secondary Cortex-
> M4 CPU. The use of a XIP image has been tested which needs to be
> loaded (e.g. using the custom m4boot loader) to the end of the
> available RAM at address 0x8f000000. The Cortex-M4 has a code-alias
> which makes sure that the instructions get fetched through the code
> bus (alias starts at 0x00800000 => 0x80800000 in system address).
> Hence, to get optimal performance, use 0x0f000000 as XIP_PHYS_ADDR.
> This address is additionally shifted by the length of the minimal
> loader which is inserted by m4boot. Currently, this offset is 0x80.
> 
> The standard DRAM base address is configured to 0x8C000000, which
> gives the Cortex-M4 48MiB of RAM.
> 
> Signed-off-by: Stefan Agner <stefan@...er.ch>
> 

Applied to next/defconfig, thanks!

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/