On 8 October 2013 05:17, Mian Yousaf Kaukab wrote:
> On Sun, Oct 6, 2013 at 2:10 PM, Peter Maydell
> wrote:
>> If we're updating, why would we update only to r0p1 and not to the most
>> recent rev/patchlevel?
>
> Does ARM provide physical vexpress platform with newer revisions of
> A9? If yes, t
Hi,
On Sun, Oct 6, 2013 at 2:10 PM, Peter Maydell wrote:
>> So what will it take to update the id of Cortex-A9 in qemu from r0p0 to r0p1?
>
> If we're updating, why would we update only to r0p1 and not to the most
> recent rev/patchlevel?
Does ARM provide physical vexpress platform with newer re
On 7 October 2013 02:26, Andreas Färber wrote:
> Am 06.10.2013 14:10, schrieb Peter Maydell:
>> The major thing we need is a mechanism for allowing at least the
>> board, and possibly also the user, to specify properties of the cpu
>> like "which rev/patchlevel is it"
>
> I believe I posted patche
Hi,
Default vexpress_defconfig does not boot on qemu vexpress-a9 target. In kernel,
vexpress uart detection for DEBUG_LL is done using Coretex-A9 id. Only r0p1 is
mapped to legacy map. All other variants are mapped to RS1/aseries map.
As qemu vexpress-a9 target reports Cortex-A9 version as r0p0,
Am 06.10.2013 14:10, schrieb Peter Maydell:
> The major thing we need is a mechanism for allowing at least the
> board, and possibly also the user, to specify properties of the cpu
> like "which rev/patchlevel is it"
I believe I posted patches for that long ago, to clean up the PXA mess a
little..
On 6 October 2013 20:12, Mian Yousaf Kaukab wrote:
> Default vexpress_defconfig does not boot on qemu vexpress-a9 target. In
> kernel,
> vexpress uart detection for DEBUG_LL is done using Coretex-A9 id. Only r0p1 is
> mapped to legacy map. All other variants are mapped to RS1/aseries map.
Detect
