From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30371@debbugs.gnu.org
Subject: [bug#30371] [PATCH] system: Add Cubieboard2.
Date: Fri, 09 Feb 2018 17:42:29 +0100 [thread overview]
Message-ID: <87bmgyyv0q.fsf@gnu.org> (raw)
In-Reply-To: <20180209163611.5257192d@scratchpost.org> (Danny Milosavljevic's message of "Fri, 9 Feb 2018 17:05:17 +0100")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> I actually want to use it for Luke's EOMA68 board. He documented that for
> mainline it should be booted using Cubieboard2's u-boot bootloader config.
>
> I'm still not done ruling out possible shorts on the board. It's still a
> prototype and I'd rather not fry it on the first power-up attempt...
Right, neat. (You should email the list about that EOMA68 thing
BTW. :-))
> Can I somehow get a hold of the generic ARM 'flash-image that Hydra (supposedly)
> built? Doesn't seem to be picked up as substitute for me.
Dunno! Can you find the job in the Hydra Web UI?
>> I’m also unsure we need to have one variable for each possible board.
>> We are not going to distribute installation images for each of these
>> boards anyway.
>
> Yeah, once
>
> (1) the agetty patch is in
> (2) we have an initrd-"copy modules IF they are there" functionality
> (3) we have glibc spawni that's not broken
>
> we can have a generic [ARM] installation-os and the user can just boot it in qemu.
OK.
>> Perhaps it makes sense to have them *if* they are discoverable or listed
>> in the manual, *and* we provide instructions for people to build their
>> own installation image for these boards.
>>
>> Thoughts?
>
> We could have a procedure:
>
> (define (os-with-u-boot os board bootloader-target triplet)
> "Given OS, amends it with the u-boot bootloader for BOARD,
> installed to BOOTLOADER-TARGET, compiled for TRIPLET."
> (operating-system (inherit os)
> (bootloader (bootloader-configuration
> (bootloader (bootloader (inherit u-boot-bootloader)
> (package (make-u-boot-package board triplet))))
> (target bootloader-target)))))
>
> and document that the user is supposed to "-e" that.
Yes, that’s what I had in mind.
> It still wouldn't use the substitute for the flash-image then, right?
That would be a different derivation, so the image itself would still
need to be built. However, all its dependencies would already be
available as substitutes.
Thanks,
Ludo’.
prev parent reply other threads:[~2018-02-09 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 17:58 [bug#30371] [PATCH] system: Add Cubieboard2 Danny Milosavljevic
2018-02-09 13:55 ` Ludovic Courtès
2018-02-09 16:05 ` Danny Milosavljevic
2018-02-09 16:42 ` Ludovic Courtès [this message]
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=87bmgyyv0q.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30371@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 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.