all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: 61959@debbugs.gnu.org
Subject: [bug#61959] [PATCH 0/7] Add some Asahi Linux packages
Date: Mon, 6 Mar 2023 00:43:17 +0100	[thread overview]
Message-ID: <20230306004317.1baa5630@primary_laptop> (raw)
In-Reply-To: <20230304144415.9644-1-roman@burningswell.com>

[-- Attachment #1: Type: text/plain, Size: 2408 bytes --]

Hi,

> > The next step would be to support building a Linux with Rust
> > modules. I'm waiting for some patches from the Rust team to do this.
> 
> Can you explain more what you mean by this?
As I understand, some GPU drivers are written in rust. 

Though the GPU driver and the display controller are separate hardware
blocks, so one could use ARM Apple computers without 3D acceleration
but with working displays and desktop environments. 

The 3D acceleration is also experimental anyway, so as I understand
Asahi Linux users need to opt-in and install a specific package to be
able to use that.

What I wonder more generally here is also how to best deal with forks
and upstreaming.

As I understand Ashai is working with various upstream projects to
upstream code. So there are several possible approaches that aren't
necessarily mutually exclusive.

The project status[1] has information on what works with upstream code.

So for instance one way could be to add support though upstream
projects. Here it means that the laptops touchpads currently won't work
for instance, but almost all the important features for the Mac Mini
from 2020 would work.

That would still need a special kernel package built with 16K pages
(that is needed for some hardware features related to the IOMMU), but
it could probably be derived from the main kernel packages.

And the benefit here is that the maintenance could be done for free if
the new Linux packages are inherited from existing package and
automatically use the same version.

For the m1n1 package, Asahi Linux is the upstream, so there is probably
nothing special there.

> u-boot-apple-m1 is a modified version of u-boot from the Asahi Linux
> team, which is unlikely to be upstreamed from what I heard in the
> internet.
Do you have pointers and references for that?

Another way would be to (also) package all Asahi Linux forks whenever
possible and use that. Though in that case I wonder what is the plan
for updating the packages. For instance does Asahi Linux makes some
releases? If not how to decide on the frequency of updates? 

And will there be any plans for migrating to upstream projects when
forks are no longer necessary?

PS: Note that I'm just a random Guix user, I'm not a maintainer.

References:
-----------
[1]https://github.com/AsahiLinux/docs/wiki/Feature-Support

Denis.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-03-05 23:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 14:44 [bug#61959] [PATCH 0/7] Add some Asahi Linux packages Roman Scherer
2023-03-04 14:46 ` [bug#61959] [PATCH 1/7] gnu: Add m1n1 Roman Scherer
2023-03-04 14:46   ` [bug#61959] [PATCH 2/7] gnu: Add u-boot-apple-m1 Roman Scherer
2023-03-04 14:46   ` [bug#61959] [PATCH 3/7] gnu: Add asahi-fwextract Roman Scherer
2023-03-04 14:46   ` [bug#61959] [PATCH 4/7] gnu: libdrm: Update to 2.4.114 Roman Scherer
2023-03-04 14:46   ` [bug#61959] [PATCH 5/7] gnu: Add asahi-mesa Roman Scherer
2023-03-04 14:46   ` [bug#61959] [PATCH 6/7] gnu: Add asahi-mesa-headers Roman Scherer
2023-03-04 14:46   ` [bug#61959] [PATCH 7/7] gnu: Add asahi-mesa-utils Roman Scherer
2023-03-04 17:38 ` [bug#61959] [PATCH 0/7] Add some Asahi Linux packages Ricardo Wurmus
2023-03-05 10:53   ` Roman Scherer
2023-03-05 11:15     ` Roman Scherer
2023-03-04 19:42 ` Winter via Guix-patches via
2023-03-05 10:53 ` [bug#61959] [PATCH v2 1/7] gnu: Add m1n1 Roman Scherer
2023-03-05 10:53   ` [bug#61959] [PATCH v2 2/7] gnu: Add u-boot-apple-m1 Roman Scherer
2023-03-05 10:53   ` [bug#61959] [PATCH v2 3/7] gnu: libdrm: Update to 2.4.114 Roman Scherer
2023-03-05 10:53   ` [bug#61959] [PATCH v2 4/7] gnu: Add asahi-fwextract Roman Scherer
2023-03-05 10:53   ` [bug#61959] [PATCH v2 5/7] gnu: Add asahi-mesa Roman Scherer
2023-03-05 10:53   ` [bug#61959] [PATCH v2 6/7] gnu: Add asahi-mesa-headers Roman Scherer
2023-03-05 10:53   ` [bug#61959] [PATCH v2 7/7] gnu: Add asahi-mesa-utils Roman Scherer
2023-03-05 16:13 ` [bug#61959] [PATCH v3 0/7] Add some Asahi Linux packages Roman Scherer
2023-03-05 16:13   ` [bug#61959] [PATCH v3 1/7] gnu: Add m1n1 Roman Scherer
2023-03-05 16:13   ` [bug#61959] [PATCH v3 2/7] gnu: Add u-boot-apple-m1 Roman Scherer
2023-03-05 16:13   ` [bug#61959] [PATCH v3 3/7] gnu: libdrm: Update to 2.4.114 and adjust renamed options Roman Scherer
2023-03-05 16:14   ` [bug#61959] [PATCH v3 4/7] gnu: Add asahi-fwextract Roman Scherer
2023-03-05 16:14   ` [bug#61959] [PATCH v3 5/7] gnu: Add asahi-mesa Roman Scherer
2023-03-05 16:14   ` [bug#61959] [PATCH v3 6/7] gnu: Add asahi-mesa-headers Roman Scherer
2023-03-05 16:14   ` [bug#61959] [PATCH v3 7/7] gnu: Add asahi-mesa-utils Roman Scherer
2023-03-05 23:43 ` Denis 'GNUtoo' Carikli [this message]
2023-03-07  4:14 ` [bug#61959] [PATCH 0/7] Add some Asahi Linux packages Winter via Guix-patches via
2023-03-08 12:14   ` Roman Scherer
2023-03-08 12:13 ` [bug#61959] [PATCH v4 0/7] Change patch order Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 1/7] gnu: Add m1n1 Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 2/7] gnu: Add u-boot-apple-m1 Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 3/7] gnu: libdrm: Update to 2.4.114 and adjust renamed options Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 4/7] gnu: Add asahi-mesa Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 5/7] gnu: Add asahi-mesa-headers Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 6/7] gnu: Add asahi-mesa-utils Roman Scherer
2023-03-08 12:13   ` [bug#61959] [PATCH v4 7/7] gnu: Add asahi-fwextract Roman Scherer

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=20230306004317.1baa5630@primary_laptop \
    --to=gnutoo@cyberdimension.org \
    --cc=61959@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.