From: Tiejun Chen <tiejun.chen@windriver.com>
To: jwboyer@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: v1 powerpc/405ex: Support cuImage for PPC405EX
Date: Sun, 23 Aug 2009 10:03:42 +0800	[thread overview]
Message-ID: <1250993024-29527-1-git-send-email-tiejun.chen@windriver.com> (raw)
Summary: powerpc/405ex: Support cuImage for PPC405EX
Reviewers: Josh and linux-ppc
----------------------------------------------------
V1 patches are generated based on V0 as Josh's comments:
===
1. Remove duplicate #defines to merge 405EX with 440GX.
2. To prefix with ibm405ex_ for the related function.
3. Remove redundant comment for sysclk.
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 = 1541019 (17839b hex)
=> bootm
## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-2.6.31-rc5-57857-g2969260-
   Created:      2009-08-23   1:46:31 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1540955 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: [...]
Finalizing device tree... flat tree at 0x747300
Using PowerPC 40x Platform machine description
Linux version 2.6.31-rc5-57857-g2969260-dirty ...
Best Regards
Tiejun
next             reply	other threads:[~2009-08-23  2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23  2:03 Tiejun Chen [this message]
2009-08-23  2:03 ` [v1 PATCH 1/2] powerpc/405ex: provide necessary fixup function to support cuImage Tiejun Chen
2009-08-23  2:03 ` [v2 PATCH 2/2] powerpc/405ex: support cuImage via included dtb Tiejun Chen
2009-08-23  2:07   ` tiejun.chen
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=1250993024-29527-1-git-send-email-tiejun.chen@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.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).