linux/arch/microblaze
Michal Simek ee68f1745e microblaze: Support systems without lmb bram
When the system has no lmb bram, main memory should be start from
zero because of microblaze vectors.

DTS fragment could look like:
	DDR2_SDRAM: memory@0 {
		device_type = "memory";
		reg = < 0x0 0x10000000 >;
	} ;

Then you have to setup CONFIG_KERNEL_BASE_ADDR=0 which caused
that kernel physical start address will be zero. On reset vector place
will be jump to 0x100 and on 0x100 starts kernel text.

You have to solve how to load the kernel before cpu starts.
Tested with XMD.

Signed-off-by: Michal Simek <monstr@monstr.eu>
2010-04-01 08:38:23 +02:00
..
boot microblaze: Makefile cleanups 2010-04-01 08:38:19 +02:00
configs microblaze: Defconfig update 2010-02-03 10:18:20 +01:00
include/asm microblaze: uaccess: Sync strlen, strnlen, copy_to/from_user 2010-04-01 08:38:23 +02:00
kernel microblaze: Support systems without lmb bram 2010-04-01 08:38:23 +02:00
lib microblaze: uaccess: Unify __copy_tofrom_user 2010-04-01 08:38:22 +02:00
mm microblaze: move noMMU __range_ok function to uaccess.h 2010-04-01 08:38:20 +02:00
oprofile microblaze: Core oprofile configs and hooks 2009-12-14 08:45:07 +01:00
pci microblaze: PCI early support for noMMU system 2010-03-11 14:16:17 +01:00
platform microblaze: Use lowest-common-denominator default CPU settings 2009-12-14 08:45:02 +01:00
Kconfig microblaze: Add consistent code 2010-03-11 14:14:43 +01:00
Kconfig.debug microblaze: Add TRACE_IRQFLAGS_SUPPORT 2009-12-14 08:40:09 +01:00
Makefile microblaze: Fix Makefile to delete build generated files 2010-04-01 08:38:19 +02:00