[J-u-boot.git] / doc / README.ARM-SoC

[By Steven Scholz <[email protected]>, 16 Aug 2004]

Since the cpu/ directory gets clobbered with peripheral driver code I
started cleaning up 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

	cpu/$(CPU)/

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

	cpu/$(CPU)/$(SOC)/

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

	cpu/arm920t/imx/
	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
Commit	Line	Data
1d9f4105 WD	1	[By Steven Scholz <[email protected]>, 16 Aug 2004]
	2
	3	Since the cpu/ directory gets clobbered with peripheral driver code I
	4	started cleaning up cpu/arm920t.
	5
	6	I introduced the concept of Soc (system on a chip) into the ./cpu
	7	directory. That means that code that is cpu (i.e. core) specific
	8	resides in
	9
	10	cpu/$(CPU)/
	11
	12	and code that is specific to some SoC (i.e. vendor specific
	13	peripherals around the core) is moved into
	14
	15	cpu/$(CPU)/$(SOC)/
	16
	17	Thus a library/archive "cpu/$(CPU)/$(SOC)/lib$(SOC).a" will be build
	18	and linked. Examples will be
	19
	20	cpu/arm920t/imx/
	21	cpu/arm920t/s3c24x0
	22
	23	One can select an SoC by passing the name of it to ./mkconfig just
	24	like
	25
	26	@./mkconfig $(@:_config=) arm arm920t vcma9 mpl s3c24x0
	27
	28	If there's no VENDOR field (like "mpl" in the above line) one has to
	29	pass NULL instead:
	30
	31	@./mkconfig $(@:_config=) arm arm920t mx1ads NULL imx