On 25/11/2015 19:14, Andrew Baumann wrote:
> How does this work out with object_property_add_alias? It can fail
> and returns an error, so it should be called from realize, but it
> adds a new property on the object, so the property won't be useful if
> it can only be set after realize has added
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Thursday, 26 November 2015 11:39
> So I am looking at some recent news, and there is the RPi Zero which reuses
> the bcm2835 as a different board. Can't find the schematic yet, but from
> what I can see, this is a raw SoC (no USB
On Wed, Nov 18, 2015 at 10:16 AM, Andrew Baumann
wrote:
> Hi Peter,
>
> Thanks for your feedback!
>
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Tuesday, 17 November 2015 23:51
>> I haven't looked beyond the diffstat yet, but a top level
>> architectural comment, I only se
> From: Peter Maydell [mailto:peter.mayd...@linaro.org]
> Sent: Wednesday, 25 November 2015 01:11
> On 25 November 2015 at 06:04, Peter Crosthwaite
> wrote:
> > On Tue, Nov 24, 2015 at 4:00 PM, Andrew Baumann
> > wrote:
> >>In general, what's the guidance on what belongs in object init vs. the
>
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Tuesday, 24 November 2015 22:04
> On Tue, Nov 24, 2015 at 4:00 PM, Andrew Baumann
> wrote:
> > I am working on refactoring the Pi support code as you suggested. I have
> split the Pi SOCs into separate objects (bcm2835 and bcm28
On 25 November 2015 at 06:04, Peter Crosthwaite
wrote:
> On Tue, Nov 24, 2015 at 4:00 PM, Andrew Baumann
> wrote:
>>In general, what's the guidance on what belongs in object init vs. the
>>realize method?
>
> If it doesn't depend on property values, it goes in init. If it does
> realize. Top lev
On Tue, Nov 24, 2015 at 4:00 PM, Andrew Baumann
wrote:
> Hi Peter (et al),
>
> I am working on refactoring the Pi support code as you suggested. I have
> split the Pi SOCs into separate objects (bcm2835 and bcm2836) which both
> instantiate a third common bcm2835_peripherals device that in turn
Hi Peter (et al),
I am working on refactoring the Pi support code as you suggested. I have split
the Pi SOCs into separate objects (bcm2835 and bcm2836) which both instantiate
a third common bcm2835_peripherals device that in turn contains all the common
devices. I have also switched the code t
On Wed, Nov 18, 2015 at 10:16 AM, Andrew Baumann
wrote:
> Hi Peter,
>
> Thanks for your feedback!
>
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Tuesday, 17 November 2015 23:51
>> I haven't looked beyond the diffstat yet, but a top level
>> architectural comment, I only se
Hi Peter,
Thanks for your feedback!
From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
Sent: Tuesday, 17 November 2015 23:51
> I haven't looked beyond the diffstat yet, but a top level
> architectural comment, I only see the one file in hw/arm. We are
> promoting the split of board and S
On Mon, Nov 16, 2015 at 2:22 PM, Andrew Baumann
wrote:
> Hi all,
>
> I have been working on Raspberry Pi 2 emulation, building on the previous
> work of Gregory Estrade, Stefan Weil and others on the original Raspberry Pi
> target. My current working tree (based off a recent master) is here:
>
Hi all,
I have been working on Raspberry Pi 2 emulation, building on the previous work
of Gregory Estrade, Stefan Weil and others on the original Raspberry Pi target.
My current working tree (based off a recent master) is here:
https://github.com/0xabu/qemu/tree/raspi
The present status is:
Am 16.11.2015 um 23:22 schrieb Andrew Baumann:
> Hi all,
>
> I have been working on Raspberry Pi 2 emulation, building on the previous
> work of Gregory Estrade, Stefan Weil and others on the original Raspberry Pi
> target. My current working tree (based off a recent master) is here:
> https
13 matches
Mail list logo
