unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix on the ASUS C201PA
Date: Sat, 23 Mar 2019 14:04:09 -0700	[thread overview]
Message-ID: <871s2x5mly.fsf@ponder> (raw)
In-Reply-To: <874l7ty2ij.fsf@gnu.org>

On 2019-03-23, Ludovic Courtès wrote:
> Vagrant Cascadian <vagrant@debian.org> skribis:
>> There's a FIXME for properly fetching the veyron kernel configuration,
>> but otherwise it's looking almost like something worth formally
>> submitting... ?
>
> It looks like it!  Mark, could you comment on this patch, in particular
> the ‘kernel-config-veyron’ bit (see below)?  Danny is fine with it.  :-)
>
> It’s great that you managed to simplify this.  Then I guess we could add
> the example and other useful bits that Timothy had.

I feel like just getting a working kernel in guix will make it easier to
work on the "bootloader" integration and such, since the kernel is a
relatively large build, having to build that in a local branch only,
rebase, etc. to keep current ... has it's cost.

Although if you want to integrate the depthcharge/bootloader patches
too, they do work, though there's no way I know of to implement system
generation selection in a bootloader menu. Biggest reason I want to get
u-boot working, but no progress on that.

I have a few more changes to the veyron-specific config that were needed
for desktop use (CONFIG_CGROUP_PERF + related), without which, enabling
the desktop caused things like pam calls to fail... The desktop is
unfortunately painfully slow. I might not get a chance to submit the
updated patches for a few days yet...

In theory and ideally, it should be possible to enable the right
features in the "regular" linux-libre package, and document the extra
modules needed in the initrd, but I have not yet managed to figure out a
working combination there. Not sure if it would be better to just wait
for that at this point.

Now if it were just possible to build libreboot in guix... but since
libreboot is essentially it's own system, it would most likely have to
re-implement libreboot's build system in guix.


live well,
  vagrant

  parent reply	other threads:[~2019-03-23 21:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  7:20 Guix on the ASUS C201PA Timothy Sample
2019-03-06  8:59 ` Vagrant Cascadian
2019-03-06 14:33   ` Timothy Sample
2019-03-10  2:42     ` Vagrant Cascadian
2019-03-17  6:47       ` Vagrant Cascadian
2019-03-17 15:20         ` Timothy Sample
2019-03-18  5:38           ` Vagrant Cascadian
2019-03-19  7:22             ` Danny Milosavljevic
2019-03-23 16:33             ` Ludovic Courtès
2019-03-23 19:10               ` Mark H Weaver
2019-03-23 21:04               ` Vagrant Cascadian [this message]
2019-03-24 18:19                 ` Vagrant Cascadian
2019-03-06 12:02 ` swedebugia
2019-03-06 15:46 ` mikadoZero
2019-03-15 11:23 ` Ludovic Courtès
2019-03-15 17:39   ` Timothy Sample

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=871s2x5mly.fsf@ponder \
    --to=vagrant@debian.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 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).