On Wed, Mar 27, 2019 at 01:36:59PM +0100, Greg Kurz wrote:
> On Wed, 27 Mar 2019 23:06:42 +1100
> David Gibson wrote:
>
> > On Wed, Mar 27, 2019 at 10:44:03AM +0100, Greg Kurz wrote:
> > > On Wed, 27 Mar 2019 19:38:27 +1100
> > > David Gibson wrote:
> > >
> > > > On Wed, Mar 27, 2019 at 08:09
On Wed, 27 Mar 2019 23:06:42 +1100
David Gibson wrote:
> On Wed, Mar 27, 2019 at 10:44:03AM +0100, Greg Kurz wrote:
> > On Wed, 27 Mar 2019 19:38:27 +1100
> > David Gibson wrote:
> >
> > > On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> > > > On Wed, 27 Mar 2019 11:56:10 +1100
On Wed, Mar 27, 2019 at 10:44:03AM +0100, Greg Kurz wrote:
> On Wed, 27 Mar 2019 19:38:27 +1100
> David Gibson wrote:
>
> > On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> > > On Wed, 27 Mar 2019 11:56:10 +1100
> > > David Gibson wrote:
> > >
> > > > On Tue, Mar 26, 2019 at 08:09
On Wed, 27 Mar 2019 19:38:27 +1100
David Gibson wrote:
> On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> > On Wed, 27 Mar 2019 11:56:10 +1100
> > David Gibson wrote:
> >
> > > On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> > > > On Tue, 26 Mar 2019 10:47:15 +1100
On Wed, Mar 27, 2019 at 08:09:26AM +0100, Greg Kurz wrote:
> On Wed, 27 Mar 2019 11:56:10 +1100
> David Gibson wrote:
>
> > On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> > > On Tue, 26 Mar 2019 10:47:15 +1100
> > > David Gibson wrote:
> > >
> > > > On Mon, Mar 25, 2019 at 05:33
On Wed, 27 Mar 2019 11:56:10 +1100
David Gibson wrote:
> On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> > On Tue, 26 Mar 2019 10:47:15 +1100
> > David Gibson wrote:
> >
> > > On Mon, Mar 25, 2019 at 05:33:21PM +0100, Greg Kurz wrote:
> > > > On Mon, 25 Mar 2019 11:53:47 +1100
On Tue, Mar 26, 2019 at 08:09:53AM +0100, Greg Kurz wrote:
> On Tue, 26 Mar 2019 10:47:15 +1100
> David Gibson wrote:
>
> > On Mon, Mar 25, 2019 at 05:33:21PM +0100, Greg Kurz wrote:
> > > On Mon, 25 Mar 2019 11:53:47 +1100
> > > David Gibson wrote:
> > >
> > > > On Sun, Mar 24, 2019 at 12:03
On Tue, 26 Mar 2019 10:47:15 +1100
David Gibson wrote:
> On Mon, Mar 25, 2019 at 05:33:21PM +0100, Greg Kurz wrote:
> > On Mon, 25 Mar 2019 11:53:47 +1100
> > David Gibson wrote:
> >
> > > On Sun, Mar 24, 2019 at 12:03:54AM -0400, Brad Smith wrote:
> > > > Now that I am checking out 4.0.0 r
On Mon, Mar 25, 2019 at 05:33:21PM +0100, Greg Kurz wrote:
> On Mon, 25 Mar 2019 11:53:47 +1100
> David Gibson wrote:
>
> > On Sun, Mar 24, 2019 at 12:03:54AM -0400, Brad Smith wrote:
> > > Now that I am checking out 4.0.0 rc's I see this diff is broken and
> > > depends on a function libfdt does
On Mon, 25 Mar 2019 11:53:47 +1100
David Gibson wrote:
> On Sun, Mar 24, 2019 at 12:03:54AM -0400, Brad Smith wrote:
> > Now that I am checking out 4.0.0 rc's I see this diff is broken and
> > depends on a function libfdt does not expose. The breakage is
> > hidden by the fallback check in the co
On Mon, 25 Mar 2019 11:53:47 +1100
David Gibson wrote:
> On Sun, Mar 24, 2019 at 12:03:54AM -0400, Brad Smith wrote:
> > Now that I am checking out 4.0.0 rc's I see this diff is broken and
> > depends on a function libfdt does not expose. The breakage is
> > hidden by the fallback check in the co
On Sun, Mar 24, 2019 at 12:03:54AM -0400, Brad Smith wrote:
> Now that I am checking out 4.0.0 rc's I see this diff is broken and
> depends on a function libfdt does not expose. The breakage is
> hidden by the fallback check in the configure script.
Ah, bother. That keeps happening, unfortunately
I filed a bug report for libfdt..
https://github.com/dgibson/dtc/issues/27
On 3/24/2019 12:03 AM, Brad Smith wrote:
Now that I am checking out 4.0.0 rc's I see this diff is broken and
depends on a function libfdt does not expose. The breakage is
hidden by the fallback check in the configure scr
Now that I am checking out 4.0.0 rc's I see this diff is broken and
depends on a function libfdt does not expose. The breakage is
hidden by the fallback check in the configure script.
On 1/8/2019 5:45 PM, David Gibson wrote:
From: Alexey Kardashevskiy
SLOF receives a device tree and updates it
From: Alexey Kardashevskiy
SLOF receives a device tree and updates it with various properties
before switching to the guest kernel and QEMU is not aware of any changes
made by SLOF. Since there is no real RTAS (QEMU implements it), it makes
sense to pass the SLOF final device tree to QEMU to let
15 matches
Mail list logo