From: Vagrant Cascadian <vagrant@debian.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: u-boot-am335x-boneblack -> u-boot-am335x-evm-boneblack
Date: Tue, 27 Dec 2022 08:49:53 -0800 [thread overview]
Message-ID: <87a638rdu6.fsf@contorta> (raw)
In-Reply-To: <87h6xh8sus.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3285 bytes --]
On 2022-12-26, Maxim Cournoyer wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>> On 2022-12-22, Maxim Cournoyer wrote:
>>> Vagrant Cascadian <vagrant@debian.org> writes:
>> I will take a guess that it was commit
>> c2c1dfdf5760873f1db86d14873f725a105f7feb which removed the "name" bit:
>
> Oh, that explains it, thank you for digging a bit.
>
> The following should return us to the previous name, fixing that
> regression:
>
> --8<---------------cut here---------------start------------->8---
> modified gnu/bootloader/u-boot.scm
> @@ -144,7 +144,7 @@ (define u-boot-bootloader
> (define u-boot-beaglebone-black-bootloader
> (bootloader
> (inherit u-boot-bootloader)
> - (package u-boot-am335x-evm-boneblack)
> + (package u-boot-am335x-boneblack)
> (disk-image-installer install-beaglebone-black-u-boot)))
>
> (define u-boot-allwinner-bootloader
> modified gnu/packages/bootloaders.scm
> @@ -890,17 +890,23 @@ (define*-public (make-u-boot-package board triplet
> (define-public u-boot-malta
> (make-u-boot-package "malta" "mips64el-linux-gnuabi64"))
>
> -(define-public u-boot-am335x-evm-boneblack
> - (make-u-boot-package
> - "am335x_evm" "arm-linux-gnueabihf"
> - ;; Patch out other device trees to build an image small enough to fit
> - ;; within typical partitioning schemes where the first partition begins at
> - ;; sector 2048.
> - #:configs '("CONFIG_OF_LIST=\"am335x-evm am335x-boneblack\"")
> - #:name-suffix "-boneblack"
> - #:append-description "This U-Boot is built for the BeagleBone Black, which
> -was removed upstream, adjusted from the am335x_evm build with several device
> -trees removed so that it fits within common partitioning schemes."))
> +(define-public u-boot-am335x-boneblack
> + (let ((base (make-u-boot-package
> + "am335x_evm" "arm-linux-gnueabihf"
> + ;; Patch out other device trees to build an image small enough
> + ;; to fit within typical partitioning schemes where the first
> + ;; partition begins at sector 2048.
> + #:configs '("CONFIG_OF_LIST=\"am335x-evm am335x-boneblack\"")
> + #:append-description
> + "This U-Boot is built for the BeagleBone Black, which was
> +removed upstream, adjusted from the am335x_evm build with several device trees
> +removed so that it fits within common partitioning schemes.")))
> + (package
> + (inherit base)
> + ;; The name is not derived from the board name on purpose as the config
> + ;; is modified per the comment above, parting from the default
> + ;; am335x_evm configuration.
> + (name "u-boot-am335x-boneblack"))))
>
> (define-public u-boot-am335x-evm
> (make-u-boot-package "am335x_evm" "arm-linux-gnueabihf"))
> --8<---------------cut here---------------end--------------->8---
>
> Does it look good to you? If so, I'll commit it.
It doesn't look obviously wrong... but there are a lot of whitespace
changes that my lazy eyeballs might not catch... :)
I would like to be able to see the results with "git diff
--ignore-allspace" but it is not formatted in a way I understand how to
actually apply it to git.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-12-27 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 19:54 u-boot-am335x-boneblack -> u-boot-am335x-evm-boneblack Vagrant Cascadian
2022-12-22 9:18 ` pelzflorian (Florian Pelz)
2022-12-22 21:23 ` Maxim Cournoyer
2022-12-22 22:01 ` Vagrant Cascadian
2022-12-27 2:48 ` Maxim Cournoyer
2022-12-27 16:49 ` Vagrant Cascadian [this message]
2022-12-28 20:40 ` [PATCH] gnu: u-boot-am335x-boneblack: Revert to old name Maxim Cournoyer
2022-12-28 21:09 ` Vagrant Cascadian
2022-12-29 3:15 ` Maxim Cournoyer
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=87a638rdu6.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.