public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot 2012.10 - pxa270 CPU Unknown / no turbo
Date: Wed, 14 Nov 2012 15:45:01 +0100	[thread overview]
Message-ID: <201211141545.01799.marex@denx.de> (raw)
In-Reply-To: <20121114135506.139660@gmx.net>

Dear Andreas Puls,

> Dear Marek Vasut,
> 
> > Dear Andreas Puls,
> > 
> > > Hi together,
> > > 
> > > i've got another problem with latest stable U-Boot-2012.10 and a
> > > Toradex Colibri PXA270 V2.4
> > > 
> > > Uboot dosen't regonized the CPU Revision
> > > u-boot summary screen:
> > > 
> > > U-Boot 2012.10 (Nov 12 2012 - 14:22:12)
> > > CPU: Marvell PXA27x rev. Unknown
> > 
> > See arch/arm/cpu/pxa/cpuinfo.c , patch is welcome ... they probably
> > rolled out
> > some new CPU version.
> 
> Yes, its a PXA270 M. There is a spec. update pdf from Marvel.
> http://www.marvell.com/application-processors/pxa-family/assets/pxa_27x_spe
> c_update.pdf - Table 2-3.
> 
> They changed the Stepping from A0...C5 to "PXA270M -- A1"
> A colleague would support me to change this becouse i have no cloue about
> writing C Files. So we would like ask you first if the right CPU Name
> should be shown in the summary screen which would be a rewrite of your
> function or only the right stepping with the old CPU Name would be enough
> ? (Damn it - hope you understand my Denglish)

Can the CPUs be distinguished in some deterministic way? If so, rewrite it, no 
problem.

[...]

Best regards,
Marek Vasut

  reply	other threads:[~2012-11-14 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  8:10 [U-Boot] U-Boot 2012.10 - pxa270 CPU Unknown / no turbo Andreas Puls
2012-11-13 13:52 ` Marek Vasut
2012-11-14 13:55   ` Andreas Puls
2012-11-14 14:45     ` Marek Vasut [this message]
2012-11-15  6:27       ` Andreas Puls
2012-11-15 13:28         ` 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=201211141545.01799.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