u-boot/doc/README.ARM-SoC

[By Steven Scholz <steven.scholz@imc-berlin.de>, 16 Aug 2004]

Since the cpu/ directory gets clobbered with peripheral driver code I
started cleaning up arch/arm/cpu/arm920t.

I introduced the concept of Soc (system on a chip) into the ./cpu
directory. That means that code that is cpu (i.e. core) specific
resides in

	$(CPUDIR)/

and code that is specific to some SoC (i.e. vendor specific
peripherals around the core) is moved into

	$(CPUDIR)/$(SOC)/

Thus a library/archive "$(CPUDIR)/$(SOC)/lib$(SOC).a" will be build
and linked. Examples will be

	arch/arm/cpu/arm920t/imx/
	arch/arm/cpu/arm920t/s3c24x0

One can select an SoC by passing the name of it to ./mkconfig just
like

	@./mkconfig $(@:_config=) arm arm920t vcma9 mpl s3c24x0

If there's no VENDOR field (like "mpl" in the above line) one has to
pass NULL instead:

	@./mkconfig $(@:_config=) arm arm920t mx1ads NULL imx
Patch by Steven Scholz, 16 Aug 2004: - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ into cpu/arm920t/$(SOC)/ 2004-10-09 22:21:29 +00:00			`[By Steven Scholz <steven.scholz@imc-berlin.de>, 16 Aug 2004]`

			`Since the cpu/ directory gets clobbered with peripheral driver code I`
arm: Move cpu/$CPU to arch/arm/cpu/$CPU Signed-off-by: Peter Tyser <ptyser@xes-inc.com> 2010-04-13 03:28:11 +00:00			`started cleaning up arch/arm/cpu/arm920t.`
Patch by Steven Scholz, 16 Aug 2004: - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ into cpu/arm920t/$(SOC)/ 2004-10-09 22:21:29 +00:00
			`I introduced the concept of Soc (system on a chip) into the ./cpu`
			`directory. That means that code that is cpu (i.e. core) specific`
			`resides in`

Create CPUDIR variable The CPUDIR variable points to the location of a target's CPU directory. Currently, it is set to cpu/$CPU. However, using $CPUDIR will allow for more flexibility in the future. It lays the groundwork for reorganizing U-Boot's directory structure to support a layout such as: arch/$ARCH/cpu/$CPU/* (architecture with multiple CPU types) arch/$ARCH/cpu/* (architecture with one CPU type) Signed-off-by: Peter Tyser <ptyser@xes-inc.com> 2010-04-13 03:28:02 +00:00			`$(CPUDIR)/`
Patch by Steven Scholz, 16 Aug 2004: - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ into cpu/arm920t/$(SOC)/ 2004-10-09 22:21:29 +00:00
			`and code that is specific to some SoC (i.e. vendor specific`
			`peripherals around the core) is moved into`

Create CPUDIR variable The CPUDIR variable points to the location of a target's CPU directory. Currently, it is set to cpu/$CPU. However, using $CPUDIR will allow for more flexibility in the future. It lays the groundwork for reorganizing U-Boot's directory structure to support a layout such as: arch/$ARCH/cpu/$CPU/* (architecture with multiple CPU types) arch/$ARCH/cpu/* (architecture with one CPU type) Signed-off-by: Peter Tyser <ptyser@xes-inc.com> 2010-04-13 03:28:02 +00:00			`$(CPUDIR)/$(SOC)/`
Patch by Steven Scholz, 16 Aug 2004: - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ into cpu/arm920t/$(SOC)/ 2004-10-09 22:21:29 +00:00
Create CPUDIR variable The CPUDIR variable points to the location of a target's CPU directory. Currently, it is set to cpu/$CPU. However, using $CPUDIR will allow for more flexibility in the future. It lays the groundwork for reorganizing U-Boot's directory structure to support a layout such as: arch/$ARCH/cpu/$CPU/* (architecture with multiple CPU types) arch/$ARCH/cpu/* (architecture with one CPU type) Signed-off-by: Peter Tyser <ptyser@xes-inc.com> 2010-04-13 03:28:02 +00:00			`Thus a library/archive "$(CPUDIR)/$(SOC)/lib$(SOC).a" will be build`
Patch by Steven Scholz, 16 Aug 2004: - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ into cpu/arm920t/$(SOC)/ 2004-10-09 22:21:29 +00:00			`and linked. Examples will be`

arm: Move cpu/$CPU to arch/arm/cpu/$CPU Signed-off-by: Peter Tyser <ptyser@xes-inc.com> 2010-04-13 03:28:11 +00:00			`arch/arm/cpu/arm920t/imx/`
			`arch/arm/cpu/arm920t/s3c24x0`
Patch by Steven Scholz, 16 Aug 2004: - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ into cpu/arm920t/$(SOC)/ 2004-10-09 22:21:29 +00:00
			`One can select an SoC by passing the name of it to ./mkconfig just`
			`like`

			`@./mkconfig $(@:_config=) arm arm920t vcma9 mpl s3c24x0`

			`If there's no VENDOR field (like "mpl" in the above line) one has to`
			`pass NULL instead:`

			`@./mkconfig $(@:_config=) arm arm920t mx1ads NULL imx`