qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 2/2] spapr: generate DT node names
Date: Tue, 29 Sep 2015 11:40:20 +0200	[thread overview]
Message-ID: <560A5C84.4030804@redhat.com> (raw)
In-Reply-To: <560A4DCB.1080109@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]

On 29/09/15 10:37, Laurent Vivier wrote:
> 
> 
> On 29/09/2015 07:18, David Gibson wrote:
>> On Thu, Sep 24, 2015 at 12:27:39PM +0200, Laurent Vivier wrote:
...
>>> -    /* NOTE: this is normally generated by firmware via
>>> path/unit name, -     * but in our case we must set it manually
>>> since it does not get -     * processed by OF beforehand -
>>> */ -    _FDT(fdt_setprop_string(fdt, offset, "name", "pci")); +
>>> _FDT(fdt_setprop_string(fdt, offset, "name", +
>>> pci_find_device_name((ccode >> 16) & 0xff, +
>>> (ccode >> 8) & 0xff, +
>>> ccode & 0xff)));
> 
>> Heh.  This isn't wrong, but there's a non-obvious wrinkle as to
>> why. Generally flattened trees shouldn't require the 'name'
>> property (the consumer is supposed to infer that from the node
>> name).  However, since this may also be used to generate tree
>> fragments which get passed through the PAPR dynamic reconfiguration
>> interface, and that *does* expect the name property to be passed
>> through.
> 
> In fact, this is also the behavior of SLOF.

Well, SLOF builds an Open Firmware device tree (not a flattened device
tree), thus the "name" property is always required there.

 Thomas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-09-29  9:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 10:27 [Qemu-devel] [PATCH v4 0/2] spapr: generate DT node names Laurent Vivier
2015-09-24 10:27 ` [Qemu-devel] [PATCH v4 1/2] PCI: add missing classes in pci_ids.h to build device tree Laurent Vivier
2015-09-24 10:45   ` Thomas Huth
2015-09-24 10:27 ` [Qemu-devel] [PATCH v4 2/2] spapr: generate DT node names Laurent Vivier
2015-09-24 23:29   ` Gavin Shan
2015-09-25  8:29     ` Laurent Vivier
2015-09-25  9:12       ` Michael S. Tsirkin
2015-09-25 10:21         ` Laurent Vivier
2015-09-29  5:18   ` David Gibson
2015-09-29  8:37     ` Laurent Vivier
2015-09-29  9:40       ` Thomas Huth [this message]
2015-09-30  4:33       ` David Gibson

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=560A5C84.4030804@redhat.com \
    --to=thuth@redhat.com \
    --cc=agraf@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    /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).