On Wed, 2011-02-16 at 11:13 +0100, Loïc Minier wrote:
> On Tue, Feb 15, 2011, Bahadir Balban wrote:
> > We have added support for versatile express for some time. Here is our
> > public repo in case you may want to use it as a starting point:
> > https://github.com/bbalban/qemu.git
> > We added su
On Wed, 2011-02-16 at 13:17 +0200, Bahadir Balban wrote:
> On Wed, 2011-02-16 at 10:18 +, Peter Maydell wrote:
> > On 16 February 2011 10:13, Loïc Minier wrote:
> > > BTW are these patches being sent upstream?
> >
> > I think for upstreaming it would be cleaner to have a
> > hw/vexpress.c ra
On Wed, 2011-02-16 at 10:18 +, Peter Maydell wrote:
> On 16 February 2011 10:13, Loïc Minier wrote:
> > BTW are these patches being sent upstream?
>
> I think for upstreaming it would be cleaner to have a
> hw/vexpress.c rather than trying to wedge it into
> hw/realview.c -- the two boards a
"Will Deacon" wrote on 02/16/2011 01:07:09 PM:
> > I've now built a kernel with CONFIG_ARM_ERRATA_720789 enabled, and the
> > symptoms indeed seem to have disappeared completely ...
>
> Yup - that's because without it, invalidating a TLB entry for a
particular
> process isn't broadcast correctly,
Hi Ulrich,
> I've now built a kernel with CONFIG_ARM_ERRATA_720789 enabled, and the
> symptoms indeed seem to have disappeared completely ...
Yup - that's because without it, invalidating a TLB entry for a particular
process isn't broadcast correctly, so you can end up using the old (pre-COW)
map
On 16 February 2011 10:13, Loïc Minier wrote:
> On Tue, Feb 15, 2011, Bahadir Balban wrote:
>> We have added support for versatile express for some time. Here is our
>> public repo in case you may want to use it as a starting point:
>> https://github.com/bbalban/qemu.git
>> We added support for me
On Tue, Feb 15, 2011, Bahadir Balban wrote:
> We have added support for versatile express for some time. Here is our
> public repo in case you may want to use it as a starting point:
> https://github.com/bbalban/qemu.git
> We added support for memory layout, CTxA9 timer, interrupts, few other
> fix
> I mentioned in the toolchain standup call that I'd done a quick
> estimate of the work required to support vexpress, so I thought I
> might as well clean it up a little and post it.
>
> This is a quick summary and time estimate for adding Versatile
> Express support to qemu. The general idea is
