public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Geir Thomassen <chaos@in.fer.no>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [ANNOUNCE] u-boot-ptx-20030213-1
Date: Thu, 13 Feb 2003 21:42:51 +0100	[thread overview]
Message-ID: <3E4C034B.9090002@in.fer.no> (raw)
In-Reply-To: <20030213081716.GL10342@pengutronix.de>

Robert Schwebel wrote:
> 
> Comments are welcome...  
> 

in cpu/xscale/start.S you do:

/* test if we run from flash or RAM - RAM/BDI: don't set cpuspeed   */
/* FIXME: is the criterium used here only valid for PXA25X?         */
    mov     r0, pc
    and     r0, r0, #0xF0000000 /* RAM is at 0xa0000000-0xafffffff */
    subs    r0, r0, #0xa0000000
    beq     setspeed_done

    mov     r0, #2
    mcr     p14, 0, r0, c6, c0, 0
setspeed_done:


Why? I can trace trough the CPU speed setting code without any trouble 
with a BDI, and I don't understand why there should be any problems 
doing so. Disabeling the CPU speed setting code without skipping the 
SDRAM init code at the same time might actually get you into other 
problems since the refresh periode of the SDRAM might be too long. 
Jumping over the SDRAM init is a very good idea, since the code is 
running from the SDRAM that the code is initializing. One important step 
of the init sequence is to disable the SDRAM.

-- 
Geir

  parent reply	other threads:[~2003-02-13 20:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  8:17 [U-Boot-Users] [ANNOUNCE] u-boot-ptx-20030213-1 Robert Schwebel
2003-02-13  9:20 ` Geir Thomassen
2003-02-13  9:48   ` Robert Schwebel
2003-02-13 12:23   ` Wolfgang Denk
2003-02-13  9:28 ` Geir Thomassen
2003-02-13  9:53   ` Robert Schwebel
2003-02-13 20:42 ` Geir Thomassen [this message]
2003-02-13 21:28   ` Robert Schwebel

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=3E4C034B.9090002@in.fer.no \
    --to=chaos@in.fer.no \
    --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