From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: pxa: introducing cpuinfo display for marvell pxa270m
Date: Thu, 5 Mar 2015 14:53:41 +0100 [thread overview]
Message-ID: <201503051453.41703.marex@denx.de> (raw)
In-Reply-To: <09f12ae990d9f23ca8feb1370b3d0adb9537ab1c.1425477263.git.marcel@ziswiler.com>
On Wednesday, March 04, 2015 at 02:57:31 PM, Marcel Ziswiler wrote:
> According to table 2-3 on page 87 of Marvell's latest PXA270
> Specification Update Rev. I from 2010.04.19 [1] there exists a breed of
> chips with a new CPU ID for PXA270M A1 stepping which our latest
> Colibri PXA270 V2.4A modules actually have assembled. This patch helps
> in correctly identifying those chips upon boot as well which then looks
> as follows:
>
> CPU: Marvell PXA27xM rev. A1
Acked-by: Marek Vasut <marex@denx.de>
Tom, can you please pick this directly for current ? Or do you want me to
cook you a PXA PR with one patch?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-03-05 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 13:57 [U-Boot] [PATCH] arm: pxa: introducing cpuinfo display for marvell pxa270m Marcel Ziswiler
2015-03-05 13:53 ` Marek Vasut [this message]
2015-03-05 14:43 ` Tom Rini
2015-03-05 14:48 ` Marek Vasut
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=201503051453.41703.marex@denx.de \
--to=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox