all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 34978@debbugs.gnu.org
Subject: [bug#34978] Enable support for veyron chrombooks
Date: Wed, 03 Apr 2019 18:26:00 +0200	[thread overview]
Message-ID: <87d0m3rr6v.fsf@gnu.org> (raw)
In-Reply-To: <87wokogngm.fsf@ponder> (Vagrant Cascadian's message of "Sun, 24 Mar 2019 11:02:33 -0700")

Hello!

Vagrant Cascadian <vagrant@debian.org> skribis:

> I've taken the WIP patch that Timothy Sample proposed and split it into
> two patches (one for the bootloader support, and one for the example
> system config slightly adjusted for the new kernel package name), and
> dropped the prawnos kernel, though the linux-libre-arm-veyrong kernel
> config is largely based on the prawnos kernel config. The thread on
> guix-devel describes more of the background:
>
>   https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00053.html
>
> Big thanks to Timothy for the WIP patches that made it possible to get
> this far!

Neat!  I’ve applied all three patches.

I’ve also followed up by a commit that fixes the problem you mentioned,
namely that (gnu bootloader depthcharge) wouldn’t be included in what
‘guix pull’ provides.

Could you add a sentence or two in doc/guix.texi, under “Bootloader
Configuration”, to mention Depthcharge next to U-Boot?

BTW, if U-Boot and Depthcharge are able to install custom keymaps, it’d
be nice to implement that support like commit
8d058e7b1b1a409d3d9cc29c5650a98db4e78783 does for GRUB.

Thanks Vagrant & Timothy!

Ludo’.

  parent reply	other threads:[~2019-04-03 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-24 18:02 [bug#34978] Enable support for veyron chrombooks Vagrant Cascadian
2019-03-24 18:24 ` Vagrant Cascadian
2019-03-26 22:50   ` Vagrant Cascadian
2019-03-27  9:24     ` Efraim Flashner
2019-03-27 15:14       ` Vagrant Cascadian
2019-04-03 16:26 ` Ludovic Courtès [this message]
2019-04-03 16:59   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d0m3rr6v.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=34978@debbugs.gnu.org \
    --cc=vagrant@debian.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.