public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/13 v5] ARM: OMAP3: Add support for some of	TIs ARM-Cortex A8 OMAP3 boards
Date: Sun, 2 Nov 2008 22:50:51 +0100	[thread overview]
Message-ID: <20081102215051.GA10086@game.jcrosoft.org> (raw)
In-Reply-To: <490df2ba.1438560a.2e1f.41ee@mx.google.com>

On 19:34 Sun 02 Nov     , dirk.behme at googlemail.com wrote:
> Subject: [PATCH 00/13 v5] ARM: OMAP3: Add support for some of TIs ARM-Cortex A8 OMAP3 boards
> 
> This patch series adds U-Boot v1 support for some of TI's ARM-Cortex A8 based OMAP3 boards. These are BeagleBoard [1][2], EVM [3] and Overo [4].
> 
> The patch series is based on U-Boot tar ball [5] for BeagleBoard and EVM done by several TI employees.
> 
> To be able to easily add new boards, most of the code is common for all boards. After the header files (patches 1-2) and the common code for ARM Cortex A8 (patch 3) and OMAP3 SoC (patches 4-6), support and drivers for NAND, MMC and I2C is added (patches 7-9). Patches 10-12 introduce the individual board support for Beagle, EVM and Overo, and last patch 13 the config files for these boards. 
> 
> As discussed earlier on this list, we compile for armv5 to be compatible with existing toolchains.
> 
> This patch adds ~300k of new code.
> 
> Thanks to
> 
> Steve Sakoman <sakoman@gmail.com>
> Pillai, Manikandan <mani.pillai@ti.com>
> Syed Mohammed, Khasim <khasim@ti.com>
> Nishanth Menon <nm@ti.com>
> 
> and all others who helped with this.

As planned patch set applied to omap3 branch

Best Regards,
J.

  reply	other threads:[~2008-11-02 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-02 18:34 [U-Boot] [PATCH 00/13 v5] ARM: OMAP3: Add support for some of TIs ARM-Cortex A8 OMAP3 boards dirk.behme at googlemail.com
2008-11-02 21:50 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-11-03 20:22   ` Dirk Behme

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=20081102215051.GA10086@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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