From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Balbir Singh <bsingharora@gmail.com>, Greg Kurz <groug@kaod.org>,
slof@lists.ozlabs.org,
Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH qemu v3] RFC: ppc/spapr: Receive and store device tree blob from SLOF
Date: Wed, 3 Jan 2018 11:09:47 +1100 [thread overview]
Message-ID: <20180103000947.GE24581@umbus.fritz.box> (raw)
In-Reply-To: <9fabc6c4-9a95-d44e-dc4c-33d91c00fb0c@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 1938 bytes --]
On Tue, Jan 02, 2018 at 05:13:09PM +1100, Alexey Kardashevskiy wrote:
> On 11/12/17 17:20, Alexey Kardashevskiy wrote:
> > On 09/11/17 17:38, David Gibson wrote:
> >> On Tue, Nov 07, 2017 at 06:14:04PM +1100, Alexey Kardashevskiy wrote:
> >>> On 20/10/17 11:46, Alexey Kardashevskiy wrote:
> >>>> On 19/10/17 17:24, David Gibson wrote:
> >>>>> On Tue, Oct 17, 2017 at 04:55:03PM +1100, Alexey Kardashevskiy wrote:
> >>>>>> On 16/10/17 20:36, David Gibson wrote:
> >>>>>>> On Mon, Oct 16, 2017 at 04:20:04PM +1100, Alexey Kardashevskiy
> >>>>>> wrote:
> >>>>> [snip]
> >>>>>>> ||
> >>>>>>>
> >>>>>>> Yeah.. this is all a bit complicated, I'm really thinking about a
> >>>>>>> fdt_fsck() function for libfdt.
> >>>>>>
> >>>>>>
> >>>>>> Oh. So what now? Do as below or wait for libdtc update?
> >>>>>
> >>>>> So I started hacking on this. It's a bit fiddlier to get right than I
> >>>>> anticipated. How about you make a placeholder function to "test" the
> >>>>> tree for now, with a comment that it will be updated once the libfdt
> >>>>> extensions are there.
> >>>>
> >>>> What would the placeholder do? Nothing or my proposed "FDT_CHK" thingy?
> >>>>
> >>>> Are we in a hurry with this one at all, or I can wait till libfdt gets this
> >>>> fsck()?
> >>>
> >>>
> >>> Ping?
> >>>
> >>> This is not v2.11 material, is it?
> >>
> >> Not at this stage, no.
> >>
> >> I've started looking at writing the fdt_fsck() thing, but got
> >> sidetracked by a bunch of related fixes to safety of handling
> >> corrupted blobs in libfdt.
> >
> > Please let me know when I can repost the "
> > ppc/spapr: Receive and store device tree blob from SLOF" again. Thanks.
>
>
> Still to early to repost?
No.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-03 0:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 5:20 [Qemu-devel] [PATCH qemu v3] RFC: ppc/spapr: Receive and store device tree blob from SLOF Alexey Kardashevskiy
2017-10-16 9:36 ` David Gibson
2017-10-17 5:55 ` Alexey Kardashevskiy
2017-10-19 6:24 ` David Gibson
2017-10-20 0:46 ` Alexey Kardashevskiy
2017-11-07 7:14 ` Alexey Kardashevskiy
2017-11-09 6:38 ` David Gibson
2017-12-11 6:20 ` Alexey Kardashevskiy
2018-01-02 6:13 ` Alexey Kardashevskiy
2018-01-03 0:09 ` David Gibson [this message]
2018-01-08 8:35 ` Alexey Kardashevskiy
2018-01-10 8:59 ` David Gibson
2018-02-15 5:43 ` Alexey Kardashevskiy
2018-03-07 4:02 ` Alexey Kardashevskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180103000947.GE24581@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=bsingharora@gmail.com \
--cc=groug@kaod.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=slof@lists.ozlabs.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).