From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] arm/km: add support for km_kirkwood_128m16 board
Date: Wed, 25 Sep 2013 09:19:41 +0200 [thread overview]
Message-ID: <52428E8D.40708@keymile.com> (raw)
In-Reply-To: <1372944549-19794-1-git-send-email-holger.brunck@keymile.com>
Hi Prafulla, hi Albert,
we are not so far away from v2013.10 I guess, so could one of you please pick of
these small patch series? Thanks!
Note for this patch there is already a v2 posted which applies cleanly again.
So there were:
http://patchwork.ozlabs.org/patch/275613/
http://patchwork.ozlabs.org/patch/256901/
http://patchwork.ozlabs.org/patch/256900/
Regards
Holger
On 07/04/2013 03:29 PM, Holger Brunck wrote:
> From: Karlheinz Jerg <karlheinz.jerg@keymile.com>
>
> The board is similar to the standard km_kirkwood board. From a
> u-boot point of view, the only difference is an increased
> 256 MiB DRAM (128M16). A board based on this design is for
> example the SUP12.
>
> Signed-off-by: Karlheinz Jerg <karlheinz.jerg@keymile.com>
> Signed-off-by: Holger Brunck <holger.brunck@keymile.com>
> ---
> boards.cfg | 1 +
> include/configs/km_kirkwood.h | 10 ++++++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/boards.cfg b/boards.cfg
> index c0c4282..2bb493f 100644
> --- a/boards.cfg
> +++ b/boards.cfg
> @@ -165,6 +165,7 @@ lschlv2 arm arm926ejs lsxl buffalo
> lsxhl arm arm926ejs lsxl buffalo kirkwood lsxl:LSXHL
> km_kirkwood arm arm926ejs km_arm keymile kirkwood km_kirkwood:KM_KIRKWOOD
> km_kirkwood_pci arm arm926ejs km_arm keymile kirkwood km_kirkwood:KM_KIRKWOOD_PCI
> +km_kirkwood_128m16 arm arm926ejs km_arm keymile kirkwood km_kirkwood:KM_KIRKWOOD_128M16
> kmnusa arm arm926ejs km_arm keymile kirkwood km_kirkwood:KM_NUSA
> kmsuv31 arm arm926ejs km_arm keymile kirkwood km_kirkwood:KM_SUV31
> mgcoge3un arm arm926ejs km_arm keymile kirkwood km_kirkwood:KM_MGCOGE3UN
> diff --git a/include/configs/km_kirkwood.h b/include/configs/km_kirkwood.h
> index 83bb7aa..2b5f389 100644
> --- a/include/configs/km_kirkwood.h
> +++ b/include/configs/km_kirkwood.h
> @@ -51,6 +51,16 @@
> #define KM_IVM_BUS "pca9544a:70:9" /* I2C2 (Mux-Port 1)*/
> #define CONFIG_KM_FPGA_CONFIG
>
> +/* KM_KIRKWOOD_128M16 */
> +#elif defined(CONFIG_KM_KIRKWOOD_128M16)
> +#define CONFIG_IDENT_STRING "\nKeymile Kirkwood 128M16"
> +#define CONFIG_HOSTNAME km_kirkwood_128m16
> +#undef CONFIG_SYS_KWD_CONFIG
> +#define CONFIG_SYS_KWD_CONFIG \
> + $(SRCTREE)/$(CONFIG_BOARDDIR)/kwbimage_128M16_1.cfg
> +#define CONFIG_KM_DISABLE_PCIE
> +#define KM_IVM_BUS "pca9544a:70:9" /* I2C2 (Mux-Port 1)*/
> +
> /* KM_NUSA */
> #elif defined(CONFIG_KM_NUSA)
> #define KM_IVM_BUS "pca9547:70:9" /* I2C2 (Mux-Port 1)*/
>
next prev parent reply other threads:[~2013-09-25 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 13:29 [U-Boot] [PATCH 1/3] arm/km: add support for km_kirkwood_128m16 board Holger Brunck
2013-07-04 13:29 ` [U-Boot] [PATCH 2/3] arm/km: drop unneeded define Holger Brunck
2013-07-04 13:29 ` [U-Boot] [PATCH 3/3] arm/km: make local function startup_allowed static Holger Brunck
2013-09-18 7:32 ` [U-Boot] [PATCH v2 1/3] arm/km: add support for km_kirkwood_128m16 board Holger Brunck
2013-10-02 20:31 ` Albert ARIBAUD
2013-09-25 7:19 ` Holger Brunck [this message]
2013-09-25 11:18 ` [U-Boot] [PATCH " Prafulla Wadaskar
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=52428E8D.40708@keymile.com \
--to=holger.brunck@keymile.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