all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: 34978@debbugs.gnu.org
Subject: [bug#34978] Enable support for veyron chrombooks
Date: Tue, 26 Mar 2019 15:50:24 -0700	[thread overview]
Message-ID: <87y351qmhb.fsf@aikidev.net> (raw)
In-Reply-To: <87mulkgmga.fsf@ponder>

On 2019-03-24, Vagrant Cascadian <vagrant@debian.org> wrote:
> On 2019-03-24, Vagrant Cascadian wrote:
>> Attached is a patch series that adds a linux-libre kernel variant for
>> "veyron" type chromebooks, tested on an Asus-C201
>> (a.k.a. veyron-speedy), and corresponding support for installing the
>> kernel so that the "depthcharge" bootloader can boot it, and an example
>> system config used on the veyron-speedy. It may also work on other
>> veyron models; they are untested.
>
> A bonus caveat:
>
> * currently u-boot-tools and tdb fail tests on armhf; but those should
>   probably be their own bugs...

"guix system reconfigure" works just fine when done from a checkout
(e.g. ./pre-inst-env guix system reconfigure ...), but unfortunately, if
I guix pull the very same commit:

  $ guix system reconfigure /home/vagrant/src/config/asus-c201-spdygx.scm
  guix system: error: failed to load '/home/vagrant/src/config/asus-c201-spdygx.scm':
  ice-9/boot-9.scm:2803:6: In procedure resolve-interface:
  no code for module (gnu bootloader depthcharge)

How could that happen?


live well,
  vagrant

  reply	other threads:[~2019-03-26 23:01 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 [this message]
2019-03-27  9:24     ` Efraim Flashner
2019-03-27 15:14       ` Vagrant Cascadian
2019-04-03 16:26 ` Ludovic Courtès
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=87y351qmhb.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --cc=34978@debbugs.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.