From: Vagrant Cascadian <vagrant@debian.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 34356@debbugs.gnu.org
Subject: [bug#34356] [PATCH] gnu: u-boot-novena: Allow booting from raw device offset.
Date: Sun, 10 Feb 2019 17:23:28 -0800 [thread overview]
Message-ID: <87k1i73ypb.fsf@ponder> (raw)
In-Reply-To: <20190210195954.107d21a0@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On 2019-02-10, Danny Milosavljevic wrote:
> On Wed, 06 Feb 2019 14:35:54 -0800
> Vagrant Cascadian <vagrant@debian.org> wrote:
>> (define-public u-boot-novena
> [...]
>> + ;; Patch configuration to disable loading u-boot.img from FAT partition,
>> + ;; allowing it to be installed at a device offset.
>
> Hmm, why?
>
> https://www.kosagi.com/w/index.php?title=U-boot-novena specifies that it
> loads u-boot.img from the first partition. Is it incorrect?
It's not incorrect, per se, but this was a simple way to get the
install-os functionality to work without significant refactoring.
I just recenty booted and refreshed the guixsd installation on the
novena I had, and was reminded that installation of the bootloader
required manual intervention from the user, and could potentially result
in an unbootable system of the SPL/u-boot.img were sufficiently out os
sync.
The more complicated way would be to make novena-installation-os and/or
embedded-installation-os smart enough to drop "u-boot.img" in the
correct place, on the first FAT or EXT* partition of the microSD. That
is certainly currently over my head to attempt that at the moment.
I think we had touched on this in the bugs where I introduced
u-boot-novena in #31404.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-02-11 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 22:35 [bug#34356] [PATCH] gnu: u-boot-novena: Allow booting from raw device offset Vagrant Cascadian
2019-02-10 18:59 ` Danny Milosavljevic
2019-02-11 1:23 ` Vagrant Cascadian [this message]
2019-02-11 10:04 ` bug#34356: " Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1i73ypb.fsf@ponder \
--to=vagrant@debian.org \
--cc=34356@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).