From: Dan Malek <dan@embeddededge.com>
To: acurtis@onz.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 8260/8xx Embedded Boot patch
Date: Wed, 28 Aug 2002 02:06:19 -0400 [thread overview]
Message-ID: <3D6C685B.2040403@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFAEEKDLAA.acurtis@onz.com
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Allen Curtis wrote:
> I am using a modified EST8260 configuration. However the EST8260 embedded
> stuff was broke.
So, if you have an EST configuration that passes a bd pointer from the
boot rom in r3, the attached patch should be all that is necessary, correct?
I'll just check it in right from my tree if it is what you need. The
part inside the '#if 0' to hardcode the values still needs to be fixed if
someone actually uses that. In fact, I'll just fix it and push out the
change since it will work on all boards depending upon what you want.
Thanks.
-- Dan
[-- Attachment #2: estembed.patch --]
[-- Type: text/plain, Size: 1229 bytes --]
diff -aru devel_old/arch/ppc/boot/simple/embed_config.c linuxppc_2_4_devel/arch/ppc/boot/simple/embed_config.c
--- devel_old/arch/ppc/boot/simple/embed_config.c Wed Aug 28 00:59:37 2002
+++ linuxppc_2_4_devel/arch/ppc/boot/simple/embed_config.c Wed Aug 28 01:01:04 2002
@@ -465,6 +465,8 @@
bd->bi_brgfreq *= 1000000;
#endif
+ clk_8260(bd);
+
cp = (u_char *)def_enet_addr;
for (i=0; i<6; i++) {
bd->bi_enetaddr[i] = *cp++;
diff -aru devel_old/arch/ppc/boot/simple/head.S linuxppc_2_4_devel/arch/ppc/boot/simple/head.S
--- devel_old/arch/ppc/boot/simple/head.S Wed Aug 28 00:59:37 2002
+++ linuxppc_2_4_devel/arch/ppc/boot/simple/head.S Wed Aug 28 01:00:12 2002
@@ -59,7 +59,7 @@
isync
#endif
-#if defined(CONFIG_MBX) || defined(CONFIG_RPX6)
+#if defined(CONFIG_MBX) || defined(CONFIG_RPX6) || defined(CONFIG_EST8260)
mr r29,r3 /* On the MBX860, r3 is the board info pointer.
* On the RPXSUPER, r3 points to the
* NVRAM configuration keys.
@@ -103,7 +103,7 @@
mr r3, r29
#endif
-#if defined(CONFIG_MBX) || defined(CONFIG_RPX6)
+#if defined(CONFIG_MBX) || defined(CONFIG_RPX6) || defined(CONFIG_EST8260)
mr r4,r29 /* put the board info pointer where the relocate
* routine will find it
*/
next prev parent reply other threads:[~2002-08-28 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 0:06 8260/8xx Embedded Boot patch Allen Curtis
2002-08-28 0:23 ` Tom Rini
2002-08-28 0:28 ` acurtis
2002-08-28 0:36 ` Tom Rini
2002-08-28 4:03 ` Dan Malek
2002-08-28 4:16 ` Allen Curtis
2002-08-28 6:06 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-28 17:08 Curtis, Allen
2002-08-28 18:44 ` Dan Malek
2002-08-28 19:03 Curtis, Allen
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=3D6C685B.2040403@embeddededge.com \
--to=dan@embeddededge.com \
--cc=acurtis@onz.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).