From: Tiejun Chen <tiejun.chen@windriver.com>
To: benh@kernel.crashing.org, linuxppc-dev@ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: powerpc/405ex: Support cuImage for PPC405EX
Date: Tue, 18 Aug 2009 10:28:02 +0800 [thread overview]
Message-ID: <1250562484-16415-1-git-send-email-tiejun.chen@windriver.com> (raw)
Summary: powerpc/405ex: Support cuImage for PPC405EX
Reviewers: Benjmain and linux-ppc
----------------------------------------------------
These patch series are used to support cuImage on the kilauea board based on PPC405ex.
Tested on the amcc kilauea board:
===
...
=> tftp 1000000 cuImage.kilauea
Waiting for PHY auto negotiation to complete.. done
ENET Speed is 100 Mbps - FULL duplex connection (EMAC0)
Using ppc_4xx_eth0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.103
Filename 'cuImage.kilauea'.
Load address: 0x1000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#########################################
done
Bytes transferred = 1540945 (178351 hex)
=> bootm
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-2.6.31-rc5-57857-g8df7f47-
Created: 2009-08-17 6:31:13 UTC
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1540881 Bytes = 1.5 MB
Load Address: 00400000
Entry Point: 00400468
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
CPU clock-frequency <- 0x23c345fa (600MHz)
CPU timebase-frequency <- 0x23c345fa (600MHz)
/plb: clock-frequency <- bebc1fe (200MHz)
/plb/opb: clock-frequency <- 5f5e0ff (100MHz)
/plb/opb/ebc: clock-frequency <- 5f5e0ff (100MHz)
/plb/opb/serial@ef600200: clock-frequency <- a8c000 (11MHz)
/plb/opb/serial@ef600300: clock-frequency <- a8c000 (11MHz)
Memory <- <0x0 0x10000000> (256MB)
ethernet0: local-mac-address <- 00:06:4b:10:22:6c
ethernet1: local-mac-address <- 00:06:4b:10:22:6d
zImage starting: loaded at 0x00400000 (sp: 0x0fe9ec08)
Allocating 0x330c70 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040f000:0x0073a03c)...done 0x31425c bytes
Linux/PowerPC load: root=/dev/nfs rw nfsroot=192.168.1.2:/home/vividfe/rootfsf
Finalizing device tree... flat tree at 0x747300
Using PowerPC 40x Platform machine description
...
Best Regards
Tiejun
next reply other threads:[~2009-08-18 3:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 2:28 Tiejun Chen [this message]
2009-08-18 2:28 ` [PATCH 1/2] powerpc/405ex: provide necessary fixup function to support cuImage Tiejun Chen
2009-08-20 13:26 ` Josh Boyer
2009-08-21 6:00 ` tiejun.chen
2009-08-21 11:49 ` Josh Boyer
2009-08-18 2:28 ` [PATCH 2/2] powerpc/405ex: support cuImage via included dtb Tiejun Chen
2009-08-20 13:31 ` Josh Boyer
2009-08-21 5:41 ` tiejun.chen
2009-08-21 6:35 ` Stefan Roese
2009-08-21 6:39 ` tiejun.chen
2009-08-21 11:49 ` Josh Boyer
2009-08-18 3:30 ` Mailing lists (Was: Re: powerpc/405ex: Support cuImage for PPC405EX) Stephen Rothwell
2009-08-18 4:38 ` tiejun.chen
2009-08-18 3:39 ` powerpc/405ex: Support cuImage for PPC405EX Benjamin Herrenschmidt
2009-08-18 13:28 ` Josh Boyer
2009-08-19 1:45 ` tiejun.chen
2009-08-19 11:45 ` Josh Boyer
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=1250562484-16415-1-git-send-email-tiejun.chen@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppc-dev@ozlabs.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).