linux-kernel - Re: [PATCH v4 06/24] C6X: early boot code

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 04 Oct 2011 21:11:17 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Mark Salter <msalter@...hat.com>
Cc:	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	Aurelien Jacquiot <a-jacquiot@...com>
Subject: Re: [PATCH v4 06/24] C6X: early boot code

On Tuesday 04 October 2011 12:43:43 Mark Salter wrote:
> From: Aurelien Jacquiot <a-jacquiot@...com>
> 
> Original port to early 2.6 kernel using TI COFF toolchain.
> Brought up to date by Mark Salter <msalter@...hat.com>
> 
> This patch provides the early boot code for C6X architecture. There is a
> 16 entry vector table which is used to direct reset and interrupt events. The
> vector table entries contain a small amount of code (maximum of 8 opcodes)
> which simply branches to the actual event handling code.
> 
> The head.S code simply clears BSS, setups up a few control registers, and calls
> machine_init followed by start_kernel. The machine_init code in setup.c does
> the early flat tree parsing (memory, commandline, etc). At setup_arch time, the
> code does the usual memory setup and minimally scans the devicetree for any
> needed information.
> 
> Signed-off-by: Aurelien Jacquiot <a-jacquiot@...com>
> Signed-off-by: Mark Salter <msalter@...hat.com>
> CC: Arnd Bergmann <arnd@...db.de>

Acked-by: Arnd Bergmann <arnd@...db.de>
--
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/