From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 11/11] mpc85xx: introduce the kmp204x reference design support
Date: Fri, 6 Sep 2013 13:08:22 -0700 [thread overview]
Message-ID: <522A3636.9040503@freescale.com> (raw)
In-Reply-To: <1377698669-6149-12-git-send-email-valentin.longchamp@keymile.com>
On 08/28/2013 07:04 AM, Valentin Longchamp wrote:
> This patch introduces the support for Keymile's kmp204x reference
> design. This design is based on Freescale's P2040/P2041 SoC.
>
> The peripherals used by this design are:
> - DDR3 RAM with SPD support
> - SPI NOR Flash as boot medium
> - NAND Flash
> - 2 PCIe busses (hosts 1 and 3)
> - 3 FMAN Ethernet devices (FMAN1 DTSEC1/2/5)
> - 3 Local Bus windows, with one dedicated to the QRIO reset/power mgmt
> FPGA
> - 2 HW I2C busses
> - last but not least, the mandatory serial port
>
> The board/keymile/kmp204x code is mostly based on Freescale's P2041rdb
> support and was changed according to our design (that means essentially
> removing what is not present on the designs and a few adaptations).
>
> There is currently only one prototype board that is based on this design
> and this patch also introduces it. The board is called kmlion1.
>
> Signed-off-by: Stefan Bigler <stefan.bigler@keymile.com>
> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
> ---
> Changes in v2:
> - Remove patch "5/8 fsl: do not define FSL_SRIO_PCIE_BOOT_MASTER for all
> P2041 systems" from the series as it is not needed with current u-boot.
> - fix the defines used in kmp204x/law.c for the lbus local address
> windows.
> - fix the header files to include Freescale's copyrights
> - integrate Scott's feedback
>
>
Please use the new license header string.
York
next prev parent reply other threads:[~2013-09-06 20:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 14:04 [U-Boot] [PATCH v2 0/11] Support for the kmp204x reference design Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 01/11] km-powerpc: move SYS_MALLOC_LEN out of keymile-common.h Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 02/11] km-powerpc: move CONFIG_FLASH_CFI_MTD to km83xx-common.h Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 03/11] KM: fix typo in default environment Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 04/11] KM: add CONFIG_KM_I2C_ABORT option Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 05/11] km: add CONFIG_KM_COMMON_ETH_INIT for km common eth init Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 06/11] mpc8xxx: set x2 DDR3 refresh rate if SPD config requires it Valentin Longchamp
2013-09-06 20:05 ` York Sun
2013-08-28 14:04 ` [U-Boot] [PATCH v2 07/11] net/fman: add a fm_enable_port function Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 08/11] mtd/fsl_elbc: take NAND_ECC_SOFT_BCH config option into account Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 09/11] fsl/mpc85xx: introduce fsl_print_rcw function Valentin Longchamp
2013-09-06 20:04 ` York Sun
2013-08-28 14:04 ` [U-Boot] [PATCH v2 10/11] fsl/mpc85xx: define common serdes_clock_to_string function Valentin Longchamp
2013-08-28 14:04 ` [U-Boot] [PATCH v2 11/11] mpc85xx: introduce the kmp204x reference design support Valentin Longchamp
2013-09-06 20:08 ` York Sun [this message]
2013-10-15 18:21 ` York Sun
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=522A3636.9040503@freescale.com \
--to=yorksun@freescale.com \
--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