From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH cpu/at91rm9200/start.S
Date: Mon, 13 Dec 2004 10:52:45 +0100 [thread overview]
Message-ID: <41BD666D.7060207@imc-berlin.de> (raw)
In-Reply-To: <20041213091431.CB0E5C1430@atlas.denx.de>
Wolfgang Denk wrote:
> In message <41BD53FA.1010002@imc-berlin.de> you wrote:
>
>>since enabling the "main oscillator" of Atmel's AT91RM9200 is very board
>>specific and must not be done on some boards (which use external clock
>>oscilators instead of crystals) I suggest
>>
>>* Patch by Steven Scholz, 13 Dec 2004:
>> Move code for AT91 "main oscillator" into board specific
>> memsetup.S files
>
>
> I reject this patch as it causes a duplication of the same code into
> several files. My understanding is that this code is poretty generic
> for all boards that use it; #undef'fing it for boards which don;t use
> it seems to be the better choice here.
I did not start the duplication! memsetup.S for at91rm9200dk and cmc_pu2 look
pretty much the same already! The clock setup for both boards is done in memsetup.S.
I thought about a CFG_USE_MAIN_OSCILLATOR. But since we want to move
cpu/at91rm9200 to cpu/arm920t/at91rm9200 someday we realy should not put such
board and SoC specific code into start.S.
I aggree that duplicating code is bad and a generic cpu/at91rm9200/clocks.S
would be better. But why did you accept the other patch
* Update for AT91RM9200DK and CMC_PU2 boards:
- Enable booting directly from flash
in the first place???
--
Steven Scholz
next prev parent reply other threads:[~2004-12-13 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 8:34 [U-Boot-Users] PATCH cpu/at91rm9200/start.S Steven Scholz
2004-12-13 9:14 ` Wolfgang Denk
2004-12-13 9:52 ` Steven Scholz [this message]
2004-12-13 10:05 ` Wolfgang Denk
2004-12-13 10:13 ` Steven Scholz
2004-12-13 10:30 ` Wolfgang Denk
2004-12-13 12:41 ` Steven Scholz
2005-03-31 23:45 ` Wolfgang Denk
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=41BD666D.7060207@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