From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc4xx: Sequoia: Add chip_config command
Date: Fri, 23 Oct 2009 16:05:50 +0200 [thread overview]
Message-ID: <200910231605.50384.sr@denx.de> (raw)
In-Reply-To: <1255962494-8381-1-git-send-email-sr@denx.de>
On Monday 19 October 2009 16:28:14 Stefan Roese wrote:
> This patch removes the Sequoia "bootstrap" command and replaces it
> with the now common command "chip_config".
>
> Please note that the patches with the dynamic PCI sync clock
> configuration have to be applied, before this one should go in.
> This is because Sequoia has 2 different bootstrap EEPROMs, and
> the old bootstrap command configured different values depending
> on the detected PCI async clock (33 vs. 66MHz). With the PCI sync
> clock patches, this is not necessary anymore. The PCI sync clock
> will be configured correctly on-the-fly now.
Applied to u-boot-ppc4xx/master. Thanks.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
prev parent reply other threads:[~2009-10-23 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 14:28 [U-Boot] [PATCH] ppc4xx: Sequoia: Add chip_config command Stefan Roese
2009-10-23 14:05 ` Stefan Roese [this message]
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=200910231605.50384.sr@denx.de \
--to=sr@denx.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