From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] MX28: extend print_cpuinfo() to use chip information
Date: Sun, 29 Jul 2012 12:17:33 +0200 [thread overview]
Message-ID: <50150DBD.7020107@denx.de> (raw)
In-Reply-To: <1343511827-30650-1-git-send-email-otavio@ossystems.com.br>
On 28/07/2012 23:43, Otavio Salvador wrote:
> The information now is gathered from HW_DIGCTL_CHIPID register and
> includes the chip modem and revision on the output.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> Changes in v2:
> - use ?? for unidentified revision and cpu type
> - use numeric revisions
>
> Changes in v3:
> - drop mx23 data as it will be posted in a later patch
> - fix info order (first rev, then clock)
>
> Changes in v4:
> - change short-description prefix to MX28
>
Hi Otavio,
I was convinced I had already applied your patch, but I forgot to push
my local -next tree to the server to make it public. Sorry for delay. I
took in any case your V4, even if V3 was already ok :-)
Applied to u-boot-imx, next branch, thanks.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2012-07-29 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 21:43 [U-Boot] [PATCH v4] MX28: extend print_cpuinfo() to use chip information Otavio Salvador
2012-07-29 7:33 ` Stefano Babic
2012-07-29 10:17 ` Stefano Babic [this message]
2012-07-29 12:38 ` Otavio Salvador
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=50150DBD.7020107@denx.de \
--to=sbabic@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.