All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: The development of GNU GRUB <grub-devel@gnu.org>,
	Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
Cc: Mark Salter <msalter@redhat.com>
Subject: Re: [PATCH] arm64: make sure fdt has #address-cells and #size-cells properties
Date: Thu, 31 Oct 2019 16:59:47 +0100	[thread overview]
Message-ID: <8a4c2abd-cf49-53dc-3e64-49d676de7f64@redhat.com> (raw)
In-Reply-To: <CAEaD8JOw610Mqy3QnS=xTeE1xAoLuXxya0=qa_xUDTB18yy7TQ@mail.gmail.com>

On 10/31/19 12:56 PM, Vladimir 'phcoder' Serbinenko wrote:
> This patch looks incomplete. What if "chosen" is there but does not contain
> the relevant fields?
>

My understanding is that if there's a chosen node already defined in the
Device Tree but without #address-cells and #size-cells properties, then
is a malformed DT and is not up to GRUB to correct it.

But if GRUB is adding a child node as is the case of the chosen node, then
is up to GRUB to make sure that there are #address-cells and #size-cells
properties also defined so the child nodes are addressed correctly.

But maybe I'm wrong on this, so I'll let Mark comment since he authored
the patch and knows better what's the problem that's fixing.

> On Thu, 31 Oct 2019, 11:39 Javier Martinez Canillas, <javierm@redhat.com>
> wrote:
> 
>> From: Mark Salter <msalter@redhat.com>
>>
>> Recent upstream changes to kexec-tools relies on #address-cells
>> and #size-cells properties in the FDT. If grub2 needs to create
>> a chosen node, it is likely because firmware did not provide one.
>> In that case, set #address-cells and #size-cells properties to
>> make sure they exist.
>>
>> Signed-off-by: Mark Salter <msalter@redhat.com>
>> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
>> ---
>>
>>  grub-core/loader/arm64/linux.c | 16 +++++++++++++++-
>>  1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> diff --git grub-core/loader/arm64/linux.c grub-core/loader/arm64/linux.c
>> index ef3e9f9444c..24d73732d89 100644
>> --- grub-core/loader/arm64/linux.c
>> +++ grub-core/loader/arm64/linux.c
>> @@ -78,7 +78,21 @@ finalize_params_linux (void)
>>
>>    node = grub_fdt_find_subnode (fdt, 0, "chosen");
>>    if (node < 0)
>> -    node = grub_fdt_add_subnode (fdt, 0, "chosen");
>> +    {
>> +      /*
>> +       * If we have to create a chosen node, Make sure we
>> +       * have #address-cells and #size-cells properties.
>> +       */
>> +      retval = grub_fdt_set_prop32(fdt, 0, "#address-cells", 2);
>> +      if (retval)
>> +        goto failure;
>> +
>> +      retval = grub_fdt_set_prop32(fdt, 0, "#size-cells", 2);
>> +      if (retval)
>> +        goto failure;
>> +
>> +      node = grub_fdt_add_subnode (fdt, 0, "chosen");
>> +    }
>>
>>    if (node < 1)
>>      goto failure;
>> --
>> 2.21.0
>>
>>
 
Best regards,
-- 
Javier Martinez Canillas
Software Engineer - Desktop Hardware Enablement
Red Hat


  reply	other threads:[~2019-10-31 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 10:37 [PATCH] arm64: make sure fdt has #address-cells and #size-cells properties Javier Martinez Canillas
2019-10-31 11:56 ` Vladimir 'phcoder' Serbinenko
2019-10-31 15:59   ` Javier Martinez Canillas [this message]
2019-10-31 17:24     ` Mark Salter
2019-11-05 14:47       ` Daniel Kiper
2019-11-07 16:40 ` Leif Lindholm
2019-11-07 17:39   ` Javier Martinez Canillas

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=8a4c2abd-cf49-53dc-3e64-49d676de7f64@redhat.com \
    --to=javierm@redhat.com \
    --cc=grub-devel@gnu.org \
    --cc=msalter@redhat.com \
    --cc=phcoder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.