From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: Re: RFC: Linux-Libre 5.5.x
Date: Sun, 22 Mar 2020 06:21:39 -0700 [thread overview]
Message-ID: <87sgi0le3g.fsf@ponder> (raw)
In-Reply-To: <87k13gqhrw.fsf@ponder>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On 2020-03-19, Vagrant Cascadian wrote:
> I've been working on trying to get a mainline or nearly mainline kernel
> working for pinebook pro, and there's a little better support in
> linux-libre 5.5.
>
> According to:
>
> https://linux-libre.fsfla.org/pub/linux-libre/releases/
>
> The 5.5 patches have been available since late January, and seem to be
> getting regular updates as needed.
>
> So far, I haven't had time to test and update linux-libre 5.5 with the
> kernel configs and so on, so I've been working on a
> linux-libre-arm64-generic package that uses the defconfig (much like
> linux-libre-arm-generic) and linux-libre 5.5.x.
I was able to test linux-libre 5.5.10 on x86_64 by copying the 5.4
kernel config over to 5.5 and building, and it seemed to work fine.
I also did a build of linux-libre-arm-generic using 5.5.10, and it
seemed to work fine as well.
It also occurs to me that it would be nice to get a newer kernel into
the upcoming release, unless there's a reason not to...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-03-22 13:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 19:14 RFC: Linux-Libre 5.5.x on pinebook pro Vagrant Cascadian
2020-03-19 19:25 ` Vincent Legoll
2020-03-20 4:35 ` Vagrant Cascadian
2020-03-22 13:21 ` Vagrant Cascadian [this message]
2020-03-23 4:08 ` Linux-Libre 5.5.x Vagrant Cascadian
2020-03-23 4:08 ` [bug#40190] " Vagrant Cascadian
2020-03-30 17:32 ` Vagrant Cascadian
2020-03-30 17:34 ` Vagrant Cascadian
2020-03-31 0:10 ` [bug#40190] Linux-Libre 5.6 Vagrant Cascadian
2020-03-31 14:30 ` Marius Bakke
2020-03-31 17:44 ` Vagrant Cascadian
2020-03-31 18:35 ` Guillaume Le Vaillant
2020-04-03 23:28 ` Vagrant Cascadian
2020-04-03 23:29 ` Vagrant Cascadian
2020-04-16 19:37 ` Vagrant Cascadian
2020-04-17 19:26 ` Mark H Weaver
2020-06-08 20:46 ` [bug#40190] Linux-Libre 5.7 Vagrant Cascadian
2020-06-08 20:52 ` Vagrant Cascadian
2020-06-09 2:43 ` [bug#40190] Linux-Libre 5.6 Leo Famulari
2020-04-06 4:12 ` [bug#40190] Works for me Brendan Tildesley
2020-04-06 10:38 ` [bug#40190] v4l2loopback module builds with 5.4 but not 5.6 Brendan Tildesley
2020-04-06 10:46 ` Danny Milosavljevic
2020-04-06 11:01 ` Tobias Geerinckx-Rice via Guix-patches via
2020-08-05 21:29 ` bug#40190: Linux-Libre 5.5.x Leo Famulari
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=87sgi0le3g.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@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.