On 11/13/2014 05:02 AM, David Gibson wrote:
> On Fri, Oct 24, 2014 at 02:38:39PM +0200, David Gibson wrote:
>> On Thu, Oct 23, 2014 at 01:26:08PM +0200, Alexander Graf wrote:
>>>
>>>
>>> On 23.10.14 13:24, Peter Maydell wrote:
On 23 October 2014 12:23, Alexander Graf wrote:
> On 23.10.14
On Fri, Oct 24, 2014 at 02:38:39PM +0200, David Gibson wrote:
> On Thu, Oct 23, 2014 at 01:26:08PM +0200, Alexander Graf wrote:
> >
> >
> > On 23.10.14 13:24, Peter Maydell wrote:
> > > On 23 October 2014 12:23, Alexander Graf wrote:
> > >> On 23.10.14 12:19, Ard Biesheuvel wrote:
> > >>> The re
On Thu, Oct 23, 2014 at 01:26:08PM +0200, Alexander Graf wrote:
>
>
> On 23.10.14 13:24, Peter Maydell wrote:
> > On 23 October 2014 12:23, Alexander Graf wrote:
> >> On 23.10.14 12:19, Ard Biesheuvel wrote:
> >>> The reason for this change was that, before, the DTB would only be
> >>> generated
On 10/23/2014 01:41 PM, Eric Auger wrote:
> Hi,
>
> Thanks everyone for entering the thread & reading my long email.
>
> Alex, I indeed can register the notifier in the machine file after
s/after/before
Eric
the
> platform bus instantiation. This indeed guarantees the notifiers are
> called in t
Hi,
Thanks everyone for entering the thread & reading my long email.
Alex, I indeed can register the notifier in the machine file after the
platform bus instantiation. This indeed guarantees the notifiers are
called in the right order ...
Thanks
Best Regards
Eric
On 10/23/2014 01:26 PM, Alexa
On 23.10.14 13:24, Peter Maydell wrote:
> On 23 October 2014 12:23, Alexander Graf wrote:
>> On 23.10.14 12:19, Ard Biesheuvel wrote:
>>> The reason for this change was that, before, the DTB would only be
>>> generated once, and after a reset, the machine would go through the
>>> kernel boot pro
On 23 October 2014 12:23, Alexander Graf wrote:
> On 23.10.14 12:19, Ard Biesheuvel wrote:
>> The reason for this change was that, before, the DTB would only be
>> generated once, and after a reset, the machine would go through the
>> kernel boot protocol as before but the DTB pointer would point
On 23.10.14 12:19, Ard Biesheuvel wrote:
>> Dear all,
>>
>> The goal of this mail is to summarize how dynamic sysbus device tree
>> nodes were created on ARM with "machvirt dynamic sysbus device
>> instantiation",
>> https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg01626.html
>> and reque
> Dear all,
>
> The goal of this mail is to summarize how dynamic sysbus device tree
> nodes were created on ARM with "machvirt dynamic sysbus device
> instantiation",
> https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg01626.html
> and request some advises after commit "hw/arm/boot: load DT
On 23.10.14 12:10, Eric Auger wrote:
> Dear all,
>
> The goal of this mail is to summarize how dynamic sysbus device tree
> nodes were created on ARM with "machvirt dynamic sysbus device
> instantiation",
> https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg01626.html
> and request some ad
Dear all,
The goal of this mail is to summarize how dynamic sysbus device tree
nodes were created on ARM with "machvirt dynamic sysbus device
instantiation",
https://lists.gnu.org/archive/html/qemu-devel/2014-09/msg01626.html
and request some advises after commit "hw/arm/boot: load DTB as a ROM
im
11 matches
Mail list logo
