All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Cleanup cpu/arm920t using SoC
Date: Mon, 16 Aug 2004 17:59:42 +0200	[thread overview]
Message-ID: <4120D9EE.5080501@imc-berlin.de> (raw)

Hi there,

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

=========================================================================
CHANGELOG

* 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)/
=========================================================================

Since the patch is quite big I'll send it to Wolfgang directly. If it gets
applied I'd like to do the same with cpu/at91rm9200. That is introducing 
"SOC = at91rm9200" and moving all at91rm9200 code ./cpu/arm920t/at91rm9200.

The patch does not break the build process for ARM9.
I tested "./MAKEALL ARM9"

Thanks.

-- 
Steven Scholz

                 reply	other threads:[~2004-08-16 15:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4120D9EE.5080501@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.