public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Patch 00/17] U-Boot-V2: Support for OMAP3 and SDP3430
Date: Sat, 24 May 2008 08:55:00 +0200	[thread overview]
Message-ID: <4837BBC4.8030507@googlemail.com> (raw)
In-Reply-To: <8E8BB316C604E94AA019A54D0A5A82A201AF0278@dlee13.ent.ti.com>

Menon, Nishanth wrote:
> Greetings,
> 
> This patch series introduces support required for OMAP Boards and an example of OMAP3430 based SDP3430 platform is introduced for U-Boot V2. This series of patches provide a very basic SRAM boot support. The u-boot.bin file generated is around 28K in size and may be delivered as part of Peripheral boot process as described in OMAP3430 TRM[1] page 3728 section 26.4.5. I have used SRAM for this configuration and heap and stack are in SDRAM in this example.
> 
> SDP3430 details can be seen in [2].  Please note that there is further work required for this to be completely useful. Probably requires M18 CFI support, NAND 16/8 bit support, MMC(and FAT), OneNAND support and USBTTY support to be fully functional and useful.
> 
> Other platforms that may possibly leverage out of these are:
> a) OMAP3430 based Zoom MDK [3]
> b) OMAP3530 based beagle board [4]
> c) OMAP353x based EVM [5]
> d) Pandora [6]
> And others that I don't know of :). Please feel free to add.. And ofcourse, we could move all old OMAPs based platforms across also..
> 
> I thank Dirk for guiding me on creation of patches, Laurent for pointing out the dcache issue in my first rev and lots of folks for writing the initial code.

The complete series (all 17 patches):

Acked-by: Dirk Behme <dirk.behme@gmail.com>

Dirk

      reply	other threads:[~2008-05-24  6:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 16:23 [U-Boot-Users] [Patch 00/17] U-Boot-V2: Support for OMAP3 and SDP3430 Menon, Nishanth
2008-05-24  6:55 ` Dirk Behme [this message]

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=4837BBC4.8030507@googlemail.com \
    --to=dirk.behme@googlemail.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