I'm curious, how have folks been adding the devicetree command to the grub menu entry? So far I've been manually editing the grub.cfg since that worked well with my development flow, but now things have changed a bit for me, and I'm looking for a way that it would be appended automatically when the config is autogenerated when installing a new kernel.
-Jeff
Hi,
In Fedora space we've added it to the BLS config side of things, in the vast majority of cases we don't need to specify anything so if it's not a ling in the grub defaults it doesn't get added, if it is it will. Details are in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1751307
Peter
On Thu, Oct 10, 2019 at 4:00 PM Jeffrey Hugo jeffrey.l.hugo@gmail.com wrote:
I'm curious, how have folks been adding the devicetree command to the grub menu entry? So far I've been manually editing the grub.cfg since that worked well with my development flow, but now things have changed a bit for me, and I'm looking for a way that it would be appended automatically when the config is autogenerated when installing a new kernel.
-Jeff _______________________________________________ Aarch64-laptops mailing list Aarch64-laptops@lists.linaro.org https://lists.linaro.org/mailman/listinfo/aarch64-laptops
Hi,
On Thu, 10 Oct 2019 at 16:00, Jeffrey Hugo jeffrey.l.hugo@gmail.com wrote:
I'm curious, how have folks been adding the devicetree command to the grub menu entry? So far I've been manually editing the grub.cfg since that worked well with my development flow, but now things have changed a bit for me, and I'm looking for a way that it would be appended automatically when the config is autogenerated when installing a new kernel.
In Ubuntu, we have a component called flash-kernel that looks at various things in /sys and a database (text files) of mappings between machines and devicetree blob names. I have added the current AARCH64 laptops to it [1], such that if a kernel has a matching devicetree blob it will be copied into /boot. It is integrated with grub & kernel maintainer scripts to run on install/upgrades.
Then I have also patched grub to emit devicetree command if there is a kernel specific devicetree blob next to the matching initrd & kernel. [2] I have submitted this patch both to debian [3] and upstream [4], but so far there was no traction on it. It would be nice to get it in.
[1] http://launchpadlibrarian.net/446134743/flash-kernel_3.98ubuntu4_3.98ubuntu5... [2] http://launchpadlibrarian.net/434747982/grub2_2.04-1ubuntu1_2.04-1ubuntu2.di... [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929427 [4] https://lists.gnu.org/archive/html/grub-devel/2019-05/msg00121.html
On Sat, 2019-10-12 at 13:09 +0100, Dimitri John Ledkov wrote:
<snip>
Then I have also patched grub to emit devicetree command if there is a kernel specific devicetree blob next to the matching initrd & kernel. [2] I have submitted this patch both to debian [3] and upstream [4], but so far there was no traction on it. It would be nice to get it in.
[1] http://launchpadlibrarian.net/446134743/flash-kernel_3.98ubuntu4_3.98ubuntu5... [2] http://launchpadlibrarian.net/434747982/grub2_2.04-1ubuntu1_2.04-1ubuntu2.di... [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929427 [4] https://lists.gnu.org/archive/html/grub-devel/2019-05/msg00121.html
Hi Dimitri,
It looks like your patch is waiting for a second consideration from Leif:
https://lists.gnu.org/archive/html/grub-devel/2019-05/msg00133.html
Is that correct?
best regards, Richard
-- Richard.Henwood@arm.com Server Software Eco-System Tel: +1 512 410 9612 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
aarch64-laptops@lists.linaro.org
-
Dimitri John Ledkov -
Jeffrey Hugo -
Peter Robinson -
Richard Henwood