<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux.git/arch/c6x/kernel/head.S, branch v3.10</title>
<subtitle>Linux kernel source tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/'/>
<entry>
<title>C6X: early boot code</title>
<updated>2011-10-06T23:47:28+00:00</updated>
<author>
<name>Aurelien Jacquiot</name>
<email>a-jacquiot@ti.com</email>
</author>
<published>2011-10-04T15:00:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.tavy.me/linux.git/commit/?id=c1a144d77a6ca3a14ba3c0fec30bc4fd20b3d817'/>
<id>c1a144d77a6ca3a14ba3c0fec30bc4fd20b3d817</id>
<content type='text'>
Original port to early 2.6 kernel using TI COFF toolchain.
Brought up to date by Mark Salter &lt;msalter@redhat.com&gt;

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 &lt;a-jacquiot@ti.com&gt;
Signed-off-by: Mark Salter &lt;msalter@redhat.com&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Original port to early 2.6 kernel using TI COFF toolchain.
Brought up to date by Mark Salter &lt;msalter@redhat.com&gt;

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 &lt;a-jacquiot@ti.com&gt;
Signed-off-by: Mark Salter &lt;msalter@redhat.com&gt;
Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
</pre>
</div>
</content>
</entry>
</feed>
