Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Asahi Linux Support - any plans?

23 views
Skip to first unread message

Andrew Worsley

unread,
Aug 4, 2022, 8:50:03 AM8/4/22
to
I am wondering if there are any plans for supporting Asahi/M1 linux in
the debian kernels?
At the moment there are about 173 patches from the v5.19 kernel - see
https://paste.debian.net/1249157/

Is that too many to be practical for debian arm64 building?

What about an experimental kernel?

Is a separate package more suitable?

Who would I talk to about debian installer support.

I tried asking on debian-kernel IRC but it seems to be mostly
automated postings.

Thanks

Andrew

Diederik de Haas

unread,
Aug 4, 2022, 12:10:02 PM8/4/22
to
On donderdag 4 augustus 2022 14:40:14 CEST Andrew Worsley wrote:
> I am wondering if there are any plans for supporting Asahi/M1 linux in
> the debian kernels?
> At the moment there are about 173 patches from the v5.19 kernel - see
> https://paste.debian.net/1249157/

The normal course of action is to get it included in the upstream linux kernel
first and then Debian will pick it up 'automatically' at some point.
If there are kernel modules that need to be enabled, then that is something
that needs to be done on the Debian kernel side, but it would still need to be
available in the upstream kernel (first).

HTH
signature.asc

Andrew Worsley

unread,
Aug 4, 2022, 9:40:02 PM8/4/22
to
Thanks Diederik, so I'm guessing 173 is way too much but a lot of it might not
be critical to something running on the M1 (versus M2).

If I was to find a smaller set of say 10 patches to 5.19 that booted a usable
system would I be able to submit those patches some where for building (arm64 of course)?

Andrew

Marc Haber

unread,
Aug 5, 2022, 2:10:03 AM8/5/22
to
On Fri, Aug 05, 2022 at 11:36:40AM +1000, Andrew Worsley wrote:
> Thanks Diederik, so I'm guessing 173 is way too much but a lot of it might
> not
> be critical to something running on the M1 (versus M2).
>
> If I was to find a smaller set of say 10 patches to 5.19 that booted a
> usable
> system would I be able to submit those patches some where for building
> (arm64 of course)?

Is there any reason why you don't take those patches upstream where they
belong?

Greetings
Marc

--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

Andrew Worsley

unread,
Aug 5, 2022, 3:10:02 AM8/5/22
to
I believe the Asahi team has them all submitted via the various relevant maintainers
and they are working their way through the groups. Some patches make significant
changes and there is obviously discussion about whether they need to be reworked
before being passed up.

That said there was this recently on the 5.19 kernel release from Linus Torvalds...


"...
On a personal note, the most interesting part here is that I did the
release (and am writing this) on an arm64 laptop. It's something I've
been waiting for for a _loong_ time, and it's finally reality, thanks
to the Asahi team. We've had arm64 hardware around running Linux for a
long time, but none of it has really been usable as a development
platform until now.
..."

Andrew Worsley

unread,
Aug 6, 2022, 8:50:03 AM8/6/22
to
The patches are being put upstream by developers far better than me -
but it will take time.
I just had a painful time trying to trim down the patchset but it's
not likely to be below 100 for a while yet.
The Asahi team are doing a good job of keeping them rebased onto the
latest kernel and I'm using
debian bookworm + Asahi kernel on an M1 MacBook Air very nicely as my
work and general machine.

I was thinking if it is fairly easy to build a "feature-set" for M1/M2
that is pretty functional - it would allow the
work to progress on getting the debian installer working for it for
bookworm. The initial installing part is quite complex
as there is no way around booting into apple's recovery mode to set up
the boot stub.
Once that is done then you can build and install Asahi kernels
packages as normal:

make -j 8 bindeb-pkgdpkg -i
../linux-image-5.19.0-asahi-00001-gddbaa60fc907_5.19.0-asahi-00001-gddbaa60fc907-9_arm64.deb

No need to touch the installer again

If the bookworm debian installer supports apple M1 it will be really
useful to many people.

Andrew

On Fri, 5 Aug 2022 at 16:06, Marc Haber <mh+debia...@zugschlus.de> wrote:
>
0 new messages