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