Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] Queries/suggestions regarding patch series "grub2: add support for arm and aarch64"
Date: Thu, 1 Nov 2018 00:02:32 -0200 (BRST)	[thread overview]
Message-ID: <1556527544.6024542.1541037752882.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <CAK4VdL0+P6HLVcTb21ECatLwBb0jPQ2sVOYtMNCUiLyw44Z5-w@mail.gmail.com>

> From: "Erico Nunes" <nunes.erico@gmail.com>
> To: "sumit garg" <sumit.garg@linaro.org>
> Cc: "buildroot" <buildroot@buildroot.org>
> Sent: Tuesday, October 30, 2018 4:23:27 PM
> Subject: Re: [Buildroot] Queries/suggestions regarding patch series "grub2: add support for arm and aarch64"

> Hi Sumit,
> 
> On Tue, Oct 23, 2018 at 7:58 AM Sumit Garg <sumit.garg@linaro.org> wrote:
>>
>> Hello Erico,
>>
>> Firstly, apologies for not posting these comments on your patch-set
>> [1] as I joined Buildroot ML yesterday only.
>>
>> I was recently exploring to test EFI boot using Buildroot on qemu
>> aarch64 target. But currently GRUB support is missing for aarch64
>> target in Buildroot. So I came across your patch-set. I have tested
>> your patch-set on qemu/u-boot aarch64 target using efi. So I would say
>> its:
>>
>> Tested-by: Sumit Garg <sumit.garg@linaro.org>
> 
> Thanks for your testing and feedback.
> 
> Yes it is taking a while to have this patchset reviewed, but right now
> there are well over 200 patches in the patchwork queue, so I think it
> is understandable that it is taking some time. At this point I believe
> it will only be considered after 2018.11 (for 2019.02) anyway.
> 
>> However, I will suggest you to use PARTUUID for root path in grub.cfg
>> as it will make it more generic and device independent as we could use
>> either virtio, sata, usb or mmc. So I would propose a similar change
>> as in [2].
>>
>> Apart from that, how do you think about adding qemu/u-boot target for
>> aarch64 to Buildroot? As u-boot already have efi booting support using
>> bootefi.
> 
> Using PARTUUID seems to be an interesting change. I'd like to hear the
> opinion of the other Buildroot developers before making this change in
> this patchset though, since most other platforms in Buildroot are not
> doing this.
> If there is interest in it, maybe we can do this change for other
> platforms too and in a separate patchset?
> For example, then it might be also interesting to change it in the
> pc_* platforms, as it may solve /dev/sda and /dev/vda issue for
> testing them with qemu.

PARTUUID is certainly an improvement. I used it here:

    https://patchwork.ozlabs.org/patch/976538/

-- 
Carlos Santos (Casantos) - DATACOM, P&D

  reply	other threads:[~2018-11-01  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23  5:58 [Buildroot] Queries/suggestions regarding patch series "grub2: add support for arm and aarch64" Sumit Garg
2018-10-30  9:05 ` Sumit Garg
2018-10-30 19:23 ` Erico Nunes
2018-11-01  2:02   ` Carlos Santos [this message]
2018-11-02 10:04   ` Thomas Petazzoni
2018-11-02 10:53     ` Sumit Garg
2018-11-02 11:00       ` Thomas Petazzoni
2018-11-02 13:10         ` Erico Nunes
2018-11-05 10:30     ` Carlos Santos

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=1556527544.6024542.1541037752882.JavaMail.zimbra@datacom.com.br \
    --to=casantos@datacom.com.br \
    --cc=buildroot@busybox.net \
    /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