From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC440 and CONFIG_BOOKE
Date: Mon, 25 Sep 2006 07:46:52 +0200 [thread overview]
Message-ID: <200609250746.53187.sr@denx.de> (raw)
In-Reply-To: <4516B378.40409@mock.com>
Hi Jeff,
On Sunday 24 September 2006 18:34, Jeff Mock wrote:
> I'm porting u-boot to a new piece of hardware using a 440GX processor.
> My hardware looks a little bit like an Ocotea board so I'm using this as
> my starting point.
OK.
> The Ocotea configuration (and the other PPC4xx boards) doesn't define
> CONFIG_BOOKE in the config file. The 440GX is a Book-E processor, this
> appears to define some of the SPRNs incorrectly.
>
> Is this done intentionally?
The first 440 U-Boot ports (including Ocotea) where done, long before the
CONFIG_BOOKE define was added to U-Boot. All needed SPRN's should be defined
in include/ppc440.h.
Please let me know, if you spot a problem with any PPC4xx register
definitions.
Best regards,
Stefan
prev parent reply other threads:[~2006-09-25 5:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 16:34 [U-Boot-Users] PPC440 and CONFIG_BOOKE Jeff Mock
2006-09-25 5:46 ` 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=200609250746.53187.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