Re: [Qemu-devel] [PATCH 3/4] bcm2835_fb: add framebuffer device for Raspberry Pi

2016-03-02 Thread Peter Maydell
On 2 March 2016 at 00:19, Andrew Baumann wrote: >> From: Peter Maydell [mailto:peter.mayd...@linaro.org] >> More interestingly, why can't you just read from the source >> pointer you're passed in here? The framebuffer_update_display() >> code should have obtained it by looking up the location of t

Re: [Qemu-devel] [PATCH 3/4] bcm2835_fb: add framebuffer device for Raspberry Pi

2016-03-01 Thread Andrew Baumann
> From: Peter Maydell [mailto:peter.mayd...@linaro.org] > Sent: Tuesday, 1 March 2016 11:23 AM > > On 27 February 2016 at 00:16, Andrew Baumann > wrote: > > The framebuffer occupies the upper portion of memory (64MiB by > > default), but it can only be controlled/configured via a system > > mailb

Re: [Qemu-devel] [PATCH 3/4] bcm2835_fb: add framebuffer device for Raspberry Pi

2016-03-01 Thread Peter Maydell
On 27 February 2016 at 00:16, Andrew Baumann wrote: > The framebuffer occupies the upper portion of memory (64MiB by > default), but it can only be controlled/configured via a system > mailbox or property channel (to be added by a subsequent patch). > > Signed-off-by: Andrew Baumann Mostly looks

[Qemu-devel] [PATCH 3/4] bcm2835_fb: add framebuffer device for Raspberry Pi

2016-02-26 Thread Andrew Baumann
The framebuffer occupies the upper portion of memory (64MiB by default), but it can only be controlled/configured via a system mailbox or property channel (to be added by a subsequent patch). Signed-off-by: Andrew Baumann --- hw/arm/bcm2835_peripherals.c | 38 +++- hw/arm/bcm2836.c