all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: u-boot-am335x-boneblack -> u-boot-am335x-evm-boneblack
Date: Wed, 21 Dec 2022 11:54:51 -0800	[thread overview]
Message-ID: <87len0y1kk.fsf@contorta> (raw)

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

Wondering what necessitated this change from the old variable name to a
new name...

commit c04528d2a2597d79278833f3607c806278253446
Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Date:   Tue Dec 20 21:25:27 2022 -0500

    gnu: u-boot-am335x-evm-boneblack: Fix variable name.

    * gnu/packages/bootloaders.scm (u-boot-am335x-boneblack): Rename to...
    (u-boot-am335x-evm-boneblack), to match the package name.
    * gnu/bootloader/u-boot.scm (u-boot-beaglebone-black-bootloader): Adjust
    accordingly.
...
diff --git a/gnu/packages/bootloaders.scm b/gnu/packages/bootloaders.scm
index bd9f7bb577..c8b8adbc93 100644
--- a/gnu/packages/bootloaders.scm
+++ b/gnu/packages/bootloaders.scm
@@ -889,7 +889,7 @@ (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-boneblack
+(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

The u-boot-am335x-boneblack was named to match the original target that
was removed from upstream, adapting the upstream am335x-evm to fit into
a smaller gap in the partition tables... (e.g. 2MB partition offset
instead of 4MB offset required by the default am335x-evm board
configuration).

Was this a side-effect of some of the changes that were implemented with
the raspberry pi series? Is the name change actually needed in some way,
or is it just "housecleaning" ? It doesn't actually "match" the name of
the target, which is "am335x_evm", not "am335x_evm_boneblack".

I would think keeping the old name would allow for seamless upgrades. Or
at least leaving a deprecated package placeholder or something like that
if the rename is actually needed... but a little unclear on the
situation at the moment.


With all that said... having 512MB of ram, I wonder how well a
beaglebone black would do running guix at all...

Are people actually using some of these low-end boards with guix? I'll
admit, I added a bunch of them in my early days of enthusiastically
contributing to guix... but wonder if they are pragmatic to use.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2022-12-21 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 19:54 Vagrant Cascadian [this message]
2022-12-22  9:18 ` u-boot-am335x-boneblack -> u-boot-am335x-evm-boneblack 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
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=87len0y1kk.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.