mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "menon.nishanth@gmail.com" <menon.nishanth@gmail.com>
To: Uladzimir Bely <u.bely@sam-solutions.com>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: OMAP5 processors support
Date: Thu, 25 Apr 2013 08:31:09 -0500	[thread overview]
Message-ID: <CAGo_u6q1q=pPfWNOcCrgB0xxS+jL2axEyHEC-0EsOr9gUbznVA@mail.gmail.com> (raw)
In-Reply-To: <1366880959-25765-1-git-send-email-u.bely@sam-solutions.com>

Hi,
On Thu, Apr 25, 2013 at 4:09 AM, Uladzimir Bely
<u.bely@sam-solutions.com> wrote:
> Since commit
>         8bafdc1 ARM i.MX28: make chip reset via reset pin work again
>
> Patch adds basic OMAP5 support to barebox.
>
> Tested on SD card with 2 partitions: vfat (MLO, barebox.bin, zImage)
> and ext3 (rootfs). Barebox successfully starts kernel
> from commandline with "bootm /boot/zImage" command.
>
> Building MLO: make omap5_sevm_xload_defconfig; make.
> Building barebox.bin: make omap5_sevm_defconfig; make.
>
> It's an optimized and cleaned up version of previous patch.

Our upstream kernel support will be DT-only :). Further, OMAP5 ES2.0
SEVM does not exist. ES1.0 is few initial samples for development
purposes - there are drastic differences in base addresses etc for
OMAP5 ES2.0.

If providing support for ES2.0, please use uEVM as reference platform.
ES1.0 was meant to be in-development processor - no longer produced
and definitely meant to be replaced with ES2.0.
<snip>
Regards,
Nishanth Menon

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2013-04-25 13:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <014261>
2013-04-24 10:33 ` Uladzimir Bely
2013-04-24 10:51   ` Uladzimir Bely
2013-04-24 20:11   ` Sascha Hauer
2013-04-25  9:09     ` Uladzimir Bely
2013-04-25 11:05       ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-25 11:58       ` Jan Lübbe
2013-04-25 12:42         ` Uladzimir Bely
2013-04-25 20:47           ` Sascha Hauer
2013-04-26  8:31           ` Jan Lübbe
     [not found]         ` <517A57F8.8020805@sam-solutions.net>
2013-04-26 10:54           ` Jan Lübbe
2013-04-26 10:59             ` Uladzimir Bely
2013-04-26 21:58               ` Sascha Hauer
2013-04-25 13:31       ` menon.nishanth [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='CAGo_u6q1q=pPfWNOcCrgB0xxS+jL2axEyHEC-0EsOr9gUbznVA@mail.gmail.com' \
    --to=menon.nishanth@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=u.bely@sam-solutions.com \
    /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