<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/arm/boot/compressed/head.S, branch linux-3.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2013-06-19T01:16:56Z</updated>
<entry>
<title>ARM: 7743/1: compressed/head.S: work around new binutils warning</title>
<updated>2013-06-19T01:16:56Z</updated>
<author>
<name>Arnd Bergmann</name>
</author>
<published>2013-05-31T21:50:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5b9ca6b68cfa7fffcf9db83dbca90bbcad57d040'/>
<id>urn:sha1:5b9ca6b68cfa7fffcf9db83dbca90bbcad57d040</id>
<content type='text'>
commit da94a829305f1c217cfdf6771cb1faca0917e3b9 upstream.

In August 2012, Matthew Gretton-Dann checked a change into binutils
labelled "Error on obsolete &amp; warn on deprecated registers", apparently as
part of ARMv8 support. Apparently, this was supposed to emit the message
"Warning: This coprocessor register access is deprecated in ARMv8" when
using certain mcr/mrc instructions and building for ARMv8. Unfortunately,
the message that is actually emitted appears to be '(null)', which is
less helpful in comparison.

Even more unfortunately, this is biting us on every single kernel
build with a new gas, because arch/arm/boot/compressed/head.S and some
other files in that directory are built with -march=all since kernel
commit 80cec14a8 "[ARM] Add -march=all to assembly file build in
arch/arm/boot/compressed" back in v2.6.28.

This patch reverts Russell's nice solution and instead marks the head.S
file to be built for armv7-a, which fortunately lets us build all
instructions in that file without warnings even on the broken binutils.

Without this patch, building anything results in:

arch/arm/boot/compressed/head.S: Assembler messages:
arch/arm/boot/compressed/head.S:565: Warning: (null)
arch/arm/boot/compressed/head.S:676: Warning: (null)
arch/arm/boot/compressed/head.S:698: Warning: (null)
arch/arm/boot/compressed/head.S:722: Warning: (null)
arch/arm/boot/compressed/head.S:726: Warning: (null)
arch/arm/boot/compressed/head.S:957: Warning: (null)
arch/arm/boot/compressed/head.S:996: Warning: (null)
arch/arm/boot/compressed/head.S:997: Warning: (null)
arch/arm/boot/compressed/head.S:1027: Warning: (null)
arch/arm/boot/compressed/head.S:1035: Warning: (null)
arch/arm/boot/compressed/head.S:1046: Warning: (null)
arch/arm/boot/compressed/head.S:1060: Warning: (null)
arch/arm/boot/compressed/head.S:1092: Warning: (null)
arch/arm/boot/compressed/head.S:1094: Warning: (null)
arch/arm/boot/compressed/head.S:1095: Warning: (null)
arch/arm/boot/compressed/head.S:1102: Warning: (null)
arch/arm/boot/compressed/head.S:1134: Warning: (null)

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Cc: Matthew Gretton-Dann &lt;matthew.gretton-dann@arm.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
[bwh: Backported to 3.2:
 - Adjust context
 - Remove definition of asflags-y as it is now empty]
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>ARM: 7532/1: decompressor: reset SCTLR.TRE for VMSA ARMv7 cores</title>
<updated>2012-10-10T02:30:53Z</updated>
<author>
<name>Matthew Leach</name>
</author>
<published>2012-09-11T16:56:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=622bba6d5a6210572325c89a7deb61175a2330a5'/>
<id>urn:sha1:622bba6d5a6210572325c89a7deb61175a2330a5</id>
<content type='text'>
commit e1e5b7e4251c7538ca08c2c5545b0c2fbd8a6635 upstream.

This patch zeroes the SCTLR.TRE bit prior to setting the mapping as
cacheable for ARMv7 cores in the decompressor, ensuring that the
memory region attributes are obtained from the C and B bits, not from
the page tables.

Cc: Nicolas Pitre &lt;nico@fluxnic.net&gt;
Reviewed-by: Will Deacon &lt;will.deacon@arm.com&gt;
Signed-off-by: Matthew Leach &lt;matthew.leach@arm.com&gt;
Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
Signed-off-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
</content>
</entry>
<entry>
<title>ARM: 7379/1: DT: fix atags_to_fdt() second call site</title>
<updated>2012-04-22T22:30:58Z</updated>
<author>
<name>Marc Zyngier</name>
</author>
<published>2012-04-11T13:52:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9188e08805ad8d39618a5be21733af98bd43e63e'/>
<id>urn:sha1:9188e08805ad8d39618a5be21733af98bd43e63e</id>
<content type='text'>
commit 9c5fd9e85f574d9d0361b2b878f55732290afe5b upstream.

atags_to_fdt() returns 1 when it fails to find a valid FDT signature.
The CONFIG_ARM_ATAG_DTB_COMPAT code is supposed to retry with another
location, but only does so when the initial call doesn't fail.

Fix this by using the correct condition in the assembly code.

Acked-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ARM: 7139/1: fix compilation with CONFIG_ARM_ATAG_DTB_COMPAT and large TEXT_OFFSET</title>
<updated>2011-10-24T19:53:50Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2011-10-24T12:30:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=531a6a941745e1e045dd2a6bd09e1dc01247a5f3'/>
<id>urn:sha1:531a6a941745e1e045dd2a6bd09e1dc01247a5f3</id>
<content type='text'>
If TEXT_OFFSET is too large (e.g. like on MSM) the resulting immediate
argument gets wider than 8 bits.

Noticed by David Brown &lt;davidb@codeaurora.org&gt;

Signed-off-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>ARM: zImage: allow supplementing appended DTB with traditional ATAG data</title>
<updated>2011-09-14T17:51:59Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2011-09-14T02:37:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b90b9a38251e9c89c34179eccde57411ceb5f1aa'/>
<id>urn:sha1:b90b9a38251e9c89c34179eccde57411ceb5f1aa</id>
<content type='text'>
Some old bootloaders can't be updated to a device tree capable one,
yet they provide ATAGs with memory configuration, the ramdisk address,
the kernel cmdline string, etc.  To allow a device tree enabled
kernel to be used with such bootloaders, it is necessary to convert those
ATAGs into FDT properties and fold them into the DTB appended to zImage.

Currently the following ATAGs are converted:

	ATAG_CMDLINE
	ATAG_MEM
	ATAG_INITRD2

If the corresponding information already exists in the appended DTB, it
is replaced, otherwise the required node is created to hold it.

The code looks for ATAGs at the location pointed by the value of r2 upon
entry into the zImage code.  If no ATAGs are found there, an attempt at
finding ATAGs at the typical 0x100 offset from start of RAM is made.
Otherwise the DTB is left unchanged.

Thisstarted from an older patch from John Bonesio &lt;bones@secretlab.ca&gt;,
with contributions from David Brown &lt;davidb@codeaurora.org&gt;.

Signed-off-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Tested-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Tested-by: Dave Martin &lt;dave.martin@linaro.org&gt;
Tested-by: Thomas Abraham &lt;thomas.abraham@linaro.org&gt;
</content>
</entry>
<entry>
<title>ARM: zImage: make sure appended DTB doesn't get overwritten by kernel .bss</title>
<updated>2011-09-14T17:51:57Z</updated>
<author>
<name>Nicolas Pitre</name>
</author>
<published>2011-06-12T05:07:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5ffb04f6690d71fab241b3562ebf52b893ac4ff1'/>
<id>urn:sha1:5ffb04f6690d71fab241b3562ebf52b893ac4ff1</id>
<content type='text'>
The appended DTB gets relocated with the decompressor code to get out
of the way of the decompressed kernel.  However the kernel's .bss section
may be larger than the relocated code and data, and then the DTB gets
overwritten.  Let's make sure the relocation takes care of moving zImage
far enough so no such conflict with .bss occurs.

Thanks to Tony Lindgren &lt;tony@atomide.com&gt; for figuring out this issue.

While at it, let's clean up the code a bit so that the wont_overwrite
symbol is used while determining if a conflict exists, making the above
change more precise as well as eliminating some ARM/THUMB alternates.

Signed-off-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Acked-by: Tony Lindgren &lt;tony@atomide.com&gt;
Tested-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Tested-by: Dave Martin &lt;dave.martin@linaro.org&gt;
Tested-by: Thomas Abraham &lt;thomas.abraham@linaro.org&gt;
</content>
</entry>
<entry>
<title>ARM: zImage: Allow the appending of a device tree binary</title>
<updated>2011-09-14T17:50:45Z</updated>
<author>
<name>John Bonesio</name>
</author>
<published>2011-05-27T22:45:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e2a6a3aafa9862c4a4b59f2a59b8f923d64a680e'/>
<id>urn:sha1:e2a6a3aafa9862c4a4b59f2a59b8f923d64a680e</id>
<content type='text'>
This patch provides the ability to boot using a device tree that is appended
to the raw binary zImage (e.g. cat zImage &lt;filename&gt;.dtb &gt; zImage_w_dtb).

Signed-off-by: John Bonesio &lt;bones@secretlab.ca&gt;
[nico: ported to latest zImage changes plus additional cleanups/improvements]
Signed-off-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Acked-by: Grant Likely &lt;grant.likely@secretlab.ca&gt;
Acked-by: Tony Lindgren &lt;tony@atomide.com&gt;
Tested-by: Shawn Guo &lt;shawn.guo@linaro.org&gt;
Tested-by: Dave Martin &lt;dave.martin@linaro.org&gt;
Tested-by: Thomas Abraham &lt;thomas.abraham@linaro.org&gt;
</content>
</entry>
<entry>
<title>Merge branches 'btc', 'dma', 'entry', 'fixes', 'linker-layout', 'misc', 'mmci', 'suspend' and 'vfp' into for-next</title>
<updated>2011-07-22T22:08:48Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2011-07-22T22:08:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=06f365acef5ca54fd5708a0d853c4a89609536f1'/>
<id>urn:sha1:06f365acef5ca54fd5708a0d853c4a89609536f1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ARM: 6999/1: head, zImage: Always Enter the kernel in ARM state</title>
<updated>2011-07-19T11:00:53Z</updated>
<author>
<name>Dave Martin</name>
</author>
<published>2011-07-13T14:53:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=540b573875bd26dfe39aa18d22dc195f275fc0df'/>
<id>urn:sha1:540b573875bd26dfe39aa18d22dc195f275fc0df</id>
<content type='text'>
Currently, the documented kernel entry requirements are not
explicit about whether the kernel should be entered in ARM or
Thumb, leading to an ambiguitity about how to enter Thumb-2
kernels.  As a result, the kernel is reliant on the zImage
decompressor to enter the kernel proper in the correct instruction
set state.

This patch changes the boot entry protocol for head.S and Image to
be the same as for zImage: in all cases, the kernel is now entered
in ARM.

Documentation/arm/Booting is updated to reflect this new policy.

A different rule will be needed for Cortex-M class CPUs as and when
support for those lands in mainline, since these CPUs don't support
the ARM instruction set at all: a note is added to the effect that
the kernel must be entered in Thumb on such systems.

Signed-off-by: Dave Martin &lt;dave.martin@linaro.org&gt;
Acked-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>ARM: 6961/1: zImage: Add build-time check for correctly-sized proc_type entries</title>
<updated>2011-06-21T10:33:20Z</updated>
<author>
<name>Dave Martin</name>
</author>
<published>2011-06-14T13:20:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=946a105e16651c35e9cc670bff23812761f1ad35'/>
<id>urn:sha1:946a105e16651c35e9cc670bff23812761f1ad35</id>
<content type='text'>
It is easy to mis-maintain the proc_types table such that the
entries become wrongly-sized and misaligned when the kernel is
built in Thumb-2.

This patch adds an assembly-time check which will turn most common
size/alignment mistakes in this table into build failures, to avoid
having to debug the boot-time kernel hang which would happen if the
resulting kernel were actually booted.

Signed-off-by: Dave Martin &lt;dave.martin@linaro.org&gt;
Acked-by: Nicolas Pitre &lt;nicolas.pitre@linaro.org&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
</feed>
