From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] nitrogen6x: Pass the correct CPU revision to the kernel
Date: Mon, 25 Mar 2013 12:14:23 -0700 [thread overview]
Message-ID: <5150A20F.3040903@boundarydevices.com> (raw)
In-Reply-To: <5144D5A1.2020302@boundarydevices.com>
Hi Fabio,
On 03/16/2013 01:27 PM, Eric Nelson wrote:
> Hi Fabio,
>
> <snip>
>
> That said, I don't think any of this can or should be done
> without identifying the down-stream code that might break.
>
> I've seen code that scrapes /proc/cpuinfo for the "Revision:"
> line and uses that.
>
> My memory is hazy, but I think it was in either or both the
> gstreamer plugins or an "FSL Power Monitor" applet in Android.
>
> I don't recall seeing it in any VPU-related code. Dirk, do you
> have a reference there?
>
> I'll try to do some tests of different userspaces with
> get_board_rev() returning zero and see what breaks.
>
The Gstreamer VPU plugin breaks on Solo and Quad if get_board_rev()
doesn't return 0x61xxx or 0x63xxx. Oddly, the code in vpu_lib.c
loads firmware based on the 61 or 63 reference and yet still
nominally works on a Solo with a hard-coded value of 0x63000.
The VPU seems fine. It runs Vivante demos on Solo and Quad
with a board rev of zero.
Regards,
Eric
next prev parent reply other threads:[~2013-03-25 19:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 21:06 [U-Boot] [PATCH 1/2] nitrogen6x: Pass the correct CPU revision to the kernel Fabio Estevam
2013-03-15 21:06 ` [U-Boot] [PATCH 2/2] mx6qsabrelite: Do not hardcode the CPU revision Fabio Estevam
2013-03-16 5:59 ` Dirk Behme
2013-03-16 8:19 ` Wolfgang Denk
2013-03-16 14:50 ` Fabio Estevam
2013-03-16 14:52 ` Otavio Salvador
2013-03-16 15:01 ` Fabio Estevam
2013-03-16 16:32 ` Otavio Salvador
2013-03-16 19:41 ` Fabio Estevam
2013-03-16 0:20 ` [U-Boot] [PATCH 1/2] nitrogen6x: Pass the correct CPU revision to the kernel Eric Nelson
2013-03-16 14:58 ` Fabio Estevam
2013-03-16 16:13 ` Eric Nelson
2013-03-16 16:55 ` Dirk Behme
2013-03-16 20:17 ` Wolfgang Denk
2013-03-16 19:48 ` Fabio Estevam
2013-03-16 20:27 ` Eric Nelson
2013-03-25 19:14 ` Eric Nelson [this message]
2013-03-26 2:25 ` Fabio Estevam
2013-03-26 3:27 ` Fabio Estevam
2013-03-16 20:29 ` Wolfgang Denk
2013-03-16 20:14 ` Wolfgang Denk
2013-03-26 15:24 ` Eric Nelson
2013-03-26 15:26 ` Eric Nelson
2013-03-26 18:06 ` Fabio Estevam
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=5150A20F.3040903@boundarydevices.com \
--to=eric.nelson@boundarydevices.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 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.