mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Anand Gadiyar <gadiyar@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: [PATCH] Add support for OMAP4460 revision detection.
Date: Fri, 13 Apr 2012 15:24:37 +0530	[thread overview]
Message-ID: <CAO-mwNdrCAGs7qN2OHvWmC50s_gquMKk5TGcFbrSNu1=-Z=iqA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1202101752190.15811@oneiric>


[-- Attachment #1.1: Type: text/plain, Size: 835 bytes --]

On Sat, Feb 11, 2012 at 4:23 AM, Robert P. J. Day <rpjday@crashcourse.ca>wrote:

>
>
>  Without yet adding in the underlying code, extend the revision
> checking code to return additional values for PandaBoard ES boards.
> Much of the code was taken close to verbatim from U-Boot.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> --
>

 compile tested, and confirmed that this code behaves identically to
> the original panda configure and build for the three pandas i have:
>
>  * Rev A2 (boots)
>  * Rev EA3 (boots)
>  * Rev B1 ES (no output)
>
> so while there's still work to be done, this at least represents the
> necessary infrastructure to start *recognizing* panda ES boards.
>
>
For what it's worth,

Tested-by: Anand Gadiyar <gadiyar@ti.com>

On a Rev A3 (ES2.2) (boots) and on a REV B3 ES (no output again).

[-- Attachment #1.2: Type: text/html, Size: 1421 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

  reply	other threads:[~2012-04-13  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 22:53 Robert P. J. Day
2012-04-13  9:54 ` Anand Gadiyar [this message]
2012-04-13 10:05   ` Sascha Hauer

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='CAO-mwNdrCAGs7qN2OHvWmC50s_gquMKk5TGcFbrSNu1=-Z=iqA@mail.gmail.com' \
    --to=gadiyar@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=rpjday@crashcourse.ca \
    /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