From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] OMAP3: Beagle: Update revision detection
Date: Thu, 17 Dec 2009 09:38:19 -0600 [thread overview]
Message-ID: <4B2A506B.4000804@windriver.com> (raw)
In-Reply-To: <1260982381-17042-1-git-send-email-dirk.behme@googlemail.com>
Dirk Behme wrote:
> New BeagleBoard revision C4 uses a new ID. Update revision detection.
>
> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
> ---
>
> Tested on C1/2 and C4 (prototype).
>
> Patch against v2009.11
>
> Known C4 changes:
>
> - Use OMAP3 720MHz devices.
> - Change in the way the USB Host PHY is powered.
>
> (to be added later based on this patch)
>
> board/ti/beagle/beagle.c | 68 ++++++++++++++++++++++++++++++-----------------
> board/ti/beagle/beagle.h | 9 ++++--
> 2 files changed, 51 insertions(+), 26 deletions(-)
>
Patch looks fine.
I tested this on B7 and C3.
B7 reported ok
C3 reported as C1/C2 which is not.
Is there another way to test C3 vs C1/C2 ?
Tom
prev parent reply other threads:[~2009-12-17 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 16:53 [U-Boot] [PATCH] OMAP3: Beagle: Update revision detection Dirk Behme
2009-12-17 15:38 ` Tom [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=4B2A506B.4000804@windriver.com \
--to=tom.rix@windriver.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