From 1d9f410500f32b04b18b176386e77afacda7acfb Mon Sep 17 00:00:00 2001
From: wdenk <wdenk>
Date: Sat, 9 Oct 2004 22:21:29 +0000
Subject: 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)/

---
 doc/README.ARM-SoC | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 doc/README.ARM-SoC

(limited to 'doc/README.ARM-SoC')

diff --git a/doc/README.ARM-SoC b/doc/README.ARM-SoC
new file mode 100644
index 0000000..0f2677f
--- /dev/null
+++ b/doc/README.ARM-SoC
@@ -0,0 +1,31 @@
+[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 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
-- 
cgit v1.1