linux.git/include/asm-arm/assembler.h, branch master Linux kernel source tree [ARM] move include/asm-arm to arch/arm/include/asm 2008-08-02T20:32:35+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2008-08-02T09:55:55+00:00 4baa9922430662431231ac637adedddbb0cfb2d7 Move platform independent header files to arch/arm/include/asm, leaving those in asm/arch* and asm/plat* alone. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Move platform independent header files to arch/arm/include/asm, leaving
those in asm/arch* and asm/plat* alone.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] cache align destination pointer when copying memory for some processors 2008-06-22T20:44:38+00:00 Nicolas Pitre nico@cam.org 2008-03-31T16:38:31+00:00 2239aff6ab2b95af1f628eee7a809f21c41605b3 The implementation for memory copy functions on ARM had a (disabled) provision for aligning the source pointer before loading registers with data. Turns out that aligning the _destination_ pointer is much more useful, as the read side is already sufficiently helped with the use of preload. So this changes the definition of the CALGN() macro to target the destination pointer instead, and turns it on for Feroceon processors where the gain is very noticeable. Signed-off-by: Nicolas Pitre <nico@marvell.com> Signed-off-by: Lennert Buytenhek <buytenh@marvell.com> 
The implementation for memory copy functions on ARM had a (disabled)
provision for aligning the source pointer before loading registers with
data.  Turns out that aligning the _destination_ pointer is much more
useful, as the read side is already sufficiently helped with the use of
preload.

So this changes the definition of the CALGN() macro to target the
destination pointer instead, and turns it on for Feroceon processors
where the gain is very noticeable.

Signed-off-by: Nicolas Pitre <nico@marvell.com>
Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
[ARM] Remove MODE_(SVC|IRQ|FIQ|USR) and DEFAULT_FIQ 2006-06-25T11:01:48+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-06-25T11:01:48+00:00 801194e3bcf7cde163b23c6279c559e69cb4ca57 DEFAULT_FIQ was entirely unused. MODE_* are just redefinitions of *_MODE. Use *_MODE instead. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
DEFAULT_FIQ was entirely unused.  MODE_* are just redefinitions
of *_MODE.  Use *_MODE instead.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] Remove save_lr/restore_pc macros 2006-06-25T10:37:09+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-06-25T10:37:09+00:00 405040a78b33e39edf4180fc993b9608f07d3c41 As for RETINSTR/LOADREGS macros, these were for compatibility with 26-bit ARMs. No longer required, so remove them. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
As for RETINSTR/LOADREGS macros, these were for compatibility
with 26-bit ARMs.  No longer required, so remove them.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] Remove LOADREGS macro 2006-06-25T10:23:45+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-06-25T10:23:45+00:00 1b93a71755f2b15450b3e3045dab58a633e37b18 As for RETINSTR, LOADREGS is a left-over from the 26-bit days. Remove it. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
As for RETINSTR, LOADREGS is a left-over from the 26-bit days.
Remove it.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] Remove RETINSTR macro 2006-06-25T10:17:23+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-06-25T10:17:23+00:00 7999d8d7a611bee902446939952859caf1367c25 RETINSTR is a left-over from the days when we had 26-bit and 32-bit CPU support integrated into the same tree. Since this is no longer the case, we can now remove RETINSTR. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
RETINSTR is a left-over from the days when we had 26-bit and
32-bit CPU support integrated into the same tree.  Since this
is no longer the case, we can now remove RETINSTR.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] Move enable_irq and disable_irq to assembler.h 2006-03-23T16:59:37+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2006-03-23T16:59:37+00:00 9c42954dfd50d02963cd453fb84bfef3967af2f0 5d25ac038a317d454a4321cba955f756400835a5 broke VFP builds due to enable_irq not being defined as an assembly macro. Move it to assembler.h so everyone can use it. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
5d25ac038a317d454a4321cba955f756400835a5 broke VFP builds due to
enable_irq not being defined as an assembly macro.  Move it to
assembler.h so everyone can use it.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] Clean up save_and_disable_irqs macro and allow use of ARMv6 CPSID 2005-11-09T15:04:22+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-11-09T15:04:22+00:00 59d1ff3bfb56d9b8cf3ec864857e6a4dfd9d2dba save_and_disable_irqs does not need to use mov + msr (which was introduced to work around a documentation bug which was propagated into binutils.) Use msr with an immediate constant, and if we're building for ARMv6 or later, use the new CPSID instruction. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
save_and_disable_irqs does not need to use mov + msr (which was
introduced to work around a documentation bug which was propagated
into binutils.)  Use msr with an immediate constant, and if we're
building for ARMv6 or later, use the new CPSID instruction.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Linux-2.6.12-rc2 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!