From: Steven Scholz <steven.scholz@imc-berlin.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot and MPC857T?
Date: Wed, 02 Jul 2003 13:36:07 +0200 [thread overview]
Message-ID: <3F02C3A7.9000405@imc-berlin.de> (raw)
In-Reply-To: 20030702112527.GE2988@softing.com
Hi Gunnar,
> ...
> I also thought to that, but it is not so easy, because of at least the
> following Macros showed below.
>
> We have our board with a MPC855T 50 MHz and two prototypes with a MPC857T 100
> MHz. The CPU-Clock cannot be detected automatically. We need at
> least the following differences:
>
> #elif defined(CONFIG_100MHz) /* for 100 MHz = "50 MHz" |= SCCR_EBDF01 */
> #define CFG_SCCR (SCCR_TBS | SCCR_EBDF01 | \
> SCCR_COM00 | SCCR_DFSYNC00 | SCCR_DFBRG00 | \
> SCCR_DFNL000 | SCCR_DFNH000 | SCCR_DFLCD000 | \
> SCCR_RTSEL | SCCR_DFALCD00)
> #define CFG_PLPRCR ( (4-1)<<PLPRCR_MF_SHIFT | PLPRCR_TEXPS | PLPRCR_TMIST )
> #define CONFIG_8xx_GCLK_FREQ 100000000
> #else /* up to 50 MHz we use a 1:1 clock (CLKOUT=GCLK2) */
> #define CFG_SCCR (SCCR_TBS | \
> SCCR_COM00 | SCCR_DFSYNC00 | SCCR_DFBRG00 | \
> SCCR_DFNL000 | SCCR_DFNH000 | SCCR_DFLCD000 | \
> SCCR_RTSEL | SCCR_DFALCD00)
> #define CFG_PLPRCR ( (2-1)<<PLPRCR_MF_SHIFT | PLPRCR_TEXPS | PLPRCR_TMIST )
> #define CONFIG_8xx_GCLK_FREQ 50000000
> #endif /* CONFIG_...MHz */
Ehm... I don't understand. The code above only depends on
CONFIG_100MHz and not some CONFIG_MPC855T!
Of course you have to compile for a specific clock frequency. But it
shouldn't matter if it's a 855T or a 857T!
That's why I thought the FW (compiled for one specific clock) should
be able to detect the processor typ...
Steven
next prev parent reply other threads:[~2003-07-02 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 8:52 [U-Boot-Users] U-Boot and MPC857T? Steven Scholz
2003-07-01 16:49 ` Wolfgang Denk
2003-07-02 6:36 ` Steven Scholz
2003-07-02 11:25 ` Gunnar Larisch
2003-07-02 11:36 ` Steven Scholz [this message]
2003-07-02 11:53 ` Gunnar Larisch
2003-07-02 11:32 ` nyet at mrv.com
2003-07-02 11:37 ` Steven Scholz
2003-07-02 22:39 ` Nye Liu
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=3F02C3A7.9000405@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.