summaryrefslogtreecommitdiffstats
path: root/include/asm-arm/arch-iop3xx
Commit message (Collapse)AuthorAgeFilesLines
* [ARM] Fix another use of // as a commentRussell King2005-11-061-1/+1
| | | | | | // disagrees with ld's script parsing ability. Don't use it. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
* [ARM] Fix another build error with IOP3xx platformsRussell King2005-11-031-1/+1
| | | | | | ld doesn't like comments starting with // in its scripts Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
* [ARM] 3060/1: allow constants found in asm/memory.h to be used in asm codeNicolas Pitre2005-10-291-2/+2
| | | | | | | | | | | | Patch from Nicolas Pitre This patch allows for assorted type of cleanups by letting assembly code use the same set of defines for constant values and avoid duplicated definitions that might not always be in sync, or that might simply be confusing due to the different names for the same thing. Signed-off-by: Nicolas Pitre <nico@cam.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
* [ARM] 1/4: Move include of asm/hardware.h to asm-arm/arch-*/io.hRussell King2005-10-281-0/+2
| | | | | | | Including asm/hardware.h into asm/io.h can cause #define clashes between platform specific definitions and driver local definitions. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
* [ARM] Remove PFN_TO_NID for !DISCONTIGMEMRussell King2005-09-151-2/+0
| | | | | | | Platform classes need not define PFN_TO_NID when DISCONTIGMEM is not selected. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
* [PATCH] ARM: cleanup vmalloc start/offset macrosRussell King2005-05-031-3/+0
| | | | | | | | VMALLOC_START and VMALLOC_OFFSET are common between all ARM machine classes. Move them into include/asm-arm/pgtable.h, but allow a machine class to override them if required. Signed-off-by: Russell King <rmk@arm.linux.org.uk>
* Linux-2.6.12-rc2v2.6.12-rc2Linus Torvalds2005-04-1620-0/+1432
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!