From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GuixSD on Olimex A20 OLinuXino?
Date: Wed, 24 Jan 2018 15:24:18 +0100 [thread overview]
Message-ID: <20180124152418.0ee22842@scratchpost.org> (raw)
In-Reply-To: <87bmhj2w2u.fsf_-_@gnu.org>
Hi Ludo,
> I have one of these (maybe not the “LIME”, but does it make a
> difference?).
Yes, it makes a difference (in U-Boot only).
Which one do you have? There's MICRO, LIME, LIME2 and additional
variants with eMMC and without eMMC.
Most of these should already have entries in
gnu/system/install.scm . If not, one can easily add one
(add entry to gnu/bootloader/u-boot.scm, inheriting from allwinner-bootloader,
and then add entry to gnu/system/install.scm using it)
> How should I proceed? Is it enough to dump this on
> microSD and boot?
Yes.
> I would actually write the final system rather than the installation
> system given that ‘guix pull’ currently runs out of memory on that
> device.
You can also boot the image using qemu-system-arm -kernel ... -dtb ...
in order to directly load the Linux kernel (skipping u-boot).
Then set everything up in there.
Then copy the resulting image to the SD card.
You'd just have to specify the correct bootloader form in the final
system. (u-boot-a20-olinuxino-whatever-bootloader).
Like this does:
(define (adjust-bootloader os)
(operating-system (inherit os)
(bootloader (bootloader-configuration
(bootloader u-boot-a20-olinuxino-whatever-bootloader)
(target "/dev/mmcblk0")))))
next prev parent reply other threads:[~2018-01-24 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180122215320.16031.12314@vcs0.savannah.gnu.org>
[not found] ` <20180122215323.99D4A207FC@vcs0.savannah.gnu.org>
2018-01-24 14:03 ` GuixSD on Olimex A20 OLinuXino? Ludovic Courtès
2018-01-24 14:24 ` Danny Milosavljevic [this message]
2018-01-24 18:16 ` Danny Milosavljevic
2018-01-24 21:05 ` Ludovic Courtès
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=20180124152418.0ee22842@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 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.