public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Generic Support for Motorola i.MX architecture
Date: Tue, 03 Aug 2004 15:37:30 +0200	[thread overview]
Message-ID: <410F951A.6020804@imc-berlin.de> (raw)
In-Reply-To: <20040803132755.AED8CC109F@atlas.denx.de>

Wolfgang Denk wrote:
> In message <410F766F.2020106@imc-berlin.de> you wrote:
>>A while ago I suggested to create cpu/imx, cpu/s3c24x0 etc. and put all the 
>>cpu specific stuff in there.
> 
> 
> Agreed. Please submit a patch.
> ARM9 generic code should stay in cpu/arm920t/
> 
>>1.) cpu/at91rm9200/Makefile:
>>
>>     OBJS    = ../arm920t/interrupts.o ../arm920t/cpu.o \
>>               serial.o at91rm9200_ether.o at45.o
>>
>>     start.S has to be a link "start.S -> ../arm920t/start.S" since
> 
> 
> No.
> 
> 
>>2.) Or creating (by Makefile) links to the generic sources:
>>
>>     LINKS = start.S interrupts.c cpu.c
>>
>>     $(LINKS)
>>         ln -s ../arm920t/$@ $@    (oder s.?.)
> 
> 
> No.
> 
> 
>>Comments?
> 
> 
> Both methods don't look really attractive to me. If ther  eis  common
> code, it shall remain in the common directory.

But how else could we solve this?
If we leave the common arm920t code in cpu/arm920t and put the specific 
stuff in - let's say - cpu/s3c24x0...

The main makefile only takes one cpu type. How can we achieve that the code 
in cpu/arm920t _and_ in cpu/s3c24x0 is built?


-- 
Steven Scholz

  reply	other threads:[~2004-08-03 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 19:27 [U-Boot-Users] [PATCH] Generic Support for Motorola i.MX architecture Robert Schwebel
2004-06-27 19:57 ` Wolfgang Denk
2004-06-28 12:03   ` Sascha Hauer
2004-08-01 22:35     ` Wolfgang Denk
2004-08-03 11:26       ` Steven Scholz
2004-08-03 13:27         ` Wolfgang Denk
2004-08-03 13:37           ` Steven Scholz [this message]
2004-08-03 14:21             ` Wolfgang Denk
2004-08-03 14:30               ` Steven Scholz
2004-08-03 14:57               ` Steven Scholz

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=410F951A.6020804@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox