2022-05-21
00:18Revy has joined #asahi
00:18RevHelix has quit [Read error: Connection reset by peer]
00:26erinc has joined #asahi
00:46erinc has quit [Ping timeout: 480 seconds]
01:13riker77_ has joined #asahi
01:18riker77 has quit [Ping timeout: 480 seconds]
01:18riker77_ is now known as riker77
01:20Emantor has quit [Quit: ZNC - http://znc.in]
01:20Emantor has joined #asahi
02:05phiologe has joined #asahi
02:08PhilippvK has quit [Ping timeout: 480 seconds]
02:40Mary has quit [Quit: The Lounge - https://thelounge.chat]
02:41Mary has joined #asahi
03:03PhilippvK has joined #asahi
03:06phiologe has quit [Ping timeout: 480 seconds]
03:29hromwootig has joined #asahi
03:31marvin24 has joined #asahi
03:35marvin24_ has quit [Ping timeout: 480 seconds]
03:38nicolas17 has quit [Ping timeout: 480 seconds]
03:46kov has quit [Quit: Coyote finally caught me]
04:41marcanElvishJerricco[m]: the kernel will support all prior supported versions of the OS-tied firmware, forever
04:41marcanthe kernel will also support all prior device trees (modulo missing newer hardware of course) *once upstreamed* but we make no guarantees about kernel/devicetree compat until that happens
04:42marcanwhich is why the Asahi reference distro is set up with a script that updates m1n1 stage 2 with the kernel's device trees when the kernel gets updated
04:42ElvishJerricco[m]marcan: That's good news. Does the firmware that we copy into /lib/firmware need to be from the same version as the currently installed macOS stub?
04:43marcanthe installer puts the currently installed stub's firmware in the ESP, so it is expected that it will always match and a distro should always copy it. whether mismatches will cause a problem in the future, only Apple can say. right now given the kinds of firmware involved in that tree, they *probably* won't.
04:44ElvishJerricco[m]Ok, but I'll make sure to plan around trying to match the macOS stub
04:44marcanthat's also why the reference distro has a boot-time script to update the copy in /lib/firmware, and there's a manifest file you can check to see if anything changed since last boot
04:44ElvishJerricco[m]Thanks!
04:45marcancurrently we only know of four things that go in /lib/firmware: wifi (only one done so far), bluetooth, video decoder, USB xHCI chip for some machines
04:45marcanother than video decoder those are all non-apple and it's hard to imagine how they could interact with other per-OS firmware (and system firmware should always be backwards compatible)
04:46marcanso I'm guessing mixing and matching won't cause a problem, but I'd rather plan for not doing that
04:47ElvishJerricco[m]Interesting. I'm curious, what causes a piece of firmware to require being loaded out of /lib/firmware by the linux OS instead of the previous boot stages?
04:47ElvishJerricco[m]Oh, so in theory m1n1 could do it, but we just have linux do it since linux already can
04:47ElvishJerricco[m]I'm guessing?
04:48marcanit could, but it'd still have to be read off of the ESP since those firmware blobs originate in either the XNU kernel or filesystem, and therefore we have to put them somewhere in the installer either way
04:49ElvishJerricco[m]Ok that makes sense.
04:50marcanthere's also SEPOS which will be a funny special case. that one will get passed to the kernel via a memory region from m1n1.
04:51marcanApple puts that one in memory for us but the kernel still has to load it into the coprocessor
04:51ElvishJerricco[m]So alright, plan will be to have the firmware match the macOS stub. The "NixOS way" will probably be to have the user specify which version they need, and automatically download that, rather than copying existing files from the ESP (NixOS tries to be stateless outside of your config file), but that's not strictly necessary. I'll see what ends up making most sense.
04:51chengsun has quit [Ping timeout: 480 seconds]
04:51marcanthat one is system firmware too, and *must* be synchronized or everything explodes, so that's the only sane way to do that
04:51ElvishJerricco[m]Oh, that seems a bit odd, but easy enough to work with
04:53marcanif you need to avoid literally writing to the root filesystem, you should have a userspace firmware loader that can read the files off of the ESP directly, or use a ramdisk, or whatever
04:53ElvishJerricco[m]Well the stub partition is; NixOS usually controls the ESP with automation (and little hacks if you want other OSes in your boot loader menu).
04:53marcansure, but the files the installer puts there are just a mirror of what's in the stub partition anyway, and intended to represent such
04:54marcanso if you plan of owning and wiping everything in the ESP partition you don't control, well, you're going to have a bad time the way our installer is currently architected
04:55marcanI expect people to manage their stuff in there but not to literally take over the entire partition
04:55ElvishJerricco[m]Yea we don't fully wipe the ESP; we just configure our boot loader automatically
04:56ElvishJerricco[m]That's plausible; we're definitely trying to move toward EFI based booting on ARM in general, and just relying on the user to properly configure an EFI environment like u-boot outside of NixOS. We currently have... a lot of hacks because we don't do it that way
04:57ElvishJerricco[m]So I was just hoping to keep the basic assumptions about what the user will have configured the same; i.e. the EFI environment, not necessary firmware.
04:58ElvishJerricco[m]It should be workable either way, and I know just who to talk to in the NixOS rooms about what they think we should do :)
04:58marcanthe firmware mechanism we have is intended as a generic thing any platform could use; there's just no good standard like that yet (other than what Android does which is their own thing)
04:58marcanit's just unfortunate we can't just redistribute those blobs and put them in linux-firmware (and have guarantees compat won't be a problem)
04:59marcanbut either way there is clearly a use case for "Linux needs firmware synchronized with platform state" even if that's not usually what happens now on desktop systems
04:59ElvishJerricco[m]Yea. We have some automation for nonredistributable firmware in NixOS, but it basically relies on the assumption that we can have the firmware in a content-addressed path on the root fs.
05:00ElvishJerricco[m]One big reason for this is that we can do rollbacks to old OS configurations from the boot loader. But I guess in principle that would be flawed for firmware like this, which you probably don't want to rollback
05:01ElvishJerricco[m]Yea ok. I'll think on it and talk to some NixOS people about it, but that's a fairly convincing point
05:01marcanlet's just say that's not a can of worms you want to open right now, and the platform is kind of designed to forbid that, by design (security)
05:02ElvishJerricco[m]Yea I have absolutely no intention of trying to automate the macOS stub from NixOS; we're just going to assume the user configured that
05:04marcanI don't know about NixOS internals but I imagine it shouldn't be too weird to automate it; there's plenty of approaches for not touching the root filesystem directly (tmpfs+overlayfs, just a tmpfs and a firmware loader looking in an alt path, etc)
05:05marcanif the specific way we do it right now (tarball+manifest) is suboptimal it's early enough to consider doing it a different way
05:07ElvishJerricco[m]No handling that should be fine. We can just add some scripting to the boot process that copies the firmware to a usable place (that's how tpw_rules did it in his nixos-m1 repo). The rootfs isn't readonly or anything like that, we just address *almost everything* by paths hashes in the names instead of normal FHS paths; we can still have things at more mutable paths.
05:52xfim has joined #asahi
06:01xfim_ has joined #asahi
06:01millenialhacker has joined #asahi
06:02xfim has quit [Ping timeout: 480 seconds]
06:07millenialhacker has quit []
06:07millenialhacker has joined #asahi
06:29derzahl has quit [Ping timeout: 480 seconds]
06:30derzahl has joined #asahi
06:34bienjensu[m] has joined #asahi
07:24hromwootig has quit [Ping timeout: 480 seconds]
07:24Ry_Darcy has joined #asahi
07:26hromwootig has joined #asahi
07:27Ry_Darcy has quit [Remote host closed the connection]
07:29Ry_Darcy has joined #asahi
08:07Bai-Chiang has quit [Ping timeout: 480 seconds]
08:15millenialhacker_ has joined #asahi
08:18millenialhacker_ has quit [Remote host closed the connection]
08:21jluthra has quit [Remote host closed the connection]
08:21the_lanetly_052 has joined #asahi
08:21jluthra has joined #asahi
08:39Ry_Darcy has quit [Remote host closed the connection]
08:52Ry_Darcy has joined #asahi
09:01Ry_Darcy has quit [Remote host closed the connection]
09:19millenialhacker_ has joined #asahi
09:21millenialhacker_ has quit [Remote host closed the connection]
09:26bps has joined #asahi
09:32hromwootig has quit [Ping timeout: 480 seconds]
09:53hromwootig has joined #asahi
10:09Ry_Darcy has joined #asahi
10:21Ry_Darcy has quit [Remote host closed the connection]
10:26Ry_Darcy has joined #asahi
10:27hromwootig has quit [Ping timeout: 480 seconds]
10:37hromwootig has joined #asahi
10:39hromwootig has quit [Remote host closed the connection]
10:41bps has quit [Ping timeout: 480 seconds]
10:45derzahl has quit [Ping timeout: 480 seconds]
11:17pilonsi_ has joined #asahi
11:19pilonsi has quit [Ping timeout: 480 seconds]
11:22darkapex1 has quit [Ping timeout: 480 seconds]
12:15Ry_Darcy has quit [Remote host closed the connection]
12:35al3xtjames3 has joined #asahi
12:35al3xtjames has quit [Read error: Connection reset by peer]
12:35al3xtjames3 is now known as al3xtjames
12:35Ry_Darcy has joined #asahi
12:45darkapex1 has joined #asahi
12:48Bai-Chiang has joined #asahi
13:01darkapex2 has joined #asahi
13:02darkapex1 has quit [Ping timeout: 480 seconds]
13:17Bai-Chiang has quit [Quit: Konversation terminated!]
13:18Bai-Chiang has joined #asahi
13:26Bai-Chiang has quit [Ping timeout: 480 seconds]
13:29Bai-Chiang has joined #asahi
13:32bps has joined #asahi
13:46MajorBiscuit has joined #asahi
13:51xfim_ has quit [Ping timeout: 480 seconds]
14:08xfim has joined #asahi
14:12Ry_Darcy has quit [Remote host closed the connection]
14:15Gaspare has joined #asahi
14:16xfim has quit [Quit: leaving]
14:16xfim has joined #asahi
14:18Gaspare has quit []
14:24Gaspare has joined #asahi
14:27Gaspare has quit []
14:30MajorBiscuit has quit [Quit: WeeChat 3.4]
14:31MajorBiscuit has joined #asahi
14:40Gaspare has joined #asahi
14:51Gaspare has quit [Quit: Gaspare]
14:55MajorBiscuit has quit [Ping timeout: 480 seconds]
15:10bps has quit [Ping timeout: 480 seconds]
15:11bps has joined #asahi
15:13nicolas17 has joined #asahi
15:30MajorBiscuit has joined #asahi
15:33bps has quit [Ping timeout: 480 seconds]
16:11the_lanetly_052 has quit [Ping timeout: 480 seconds]
16:27MajorBiscuit has quit [Ping timeout: 480 seconds]
16:34MajorBiscuit has joined #asahi
16:56on88ip[m] has joined #asahi
17:07MajorBiscuit has quit [Quit: WeeChat 3.4]
17:09ElvishJerricco[m]I guess the first thing is going to be packaging the installer with Nix-on-macOS. Don't get me wrong, I'm no stranger to `curl | sh` :P But it seems like it'd be nice to have it packaged with an actual package manager on macOS
17:09xfim has quit [Ping timeout: 480 seconds]
17:21kov has joined #asahi
17:30lounge-user has joined #asahi
17:32lounge-user is now known as AoV
17:56MajorBiscuit has joined #asahi
18:16lgarylmtdlt^ has joined #asahi
18:18MajorBiscuit has quit [Ping timeout: 480 seconds]
19:43MajorBiscuit has joined #asahi
19:55vmeson has quit [Ping timeout: 480 seconds]
19:59touttti has joined #asahi
20:03MajorBiscuit has quit [Ping timeout: 480 seconds]
20:17millenialhacker has quit [Quit: Konversation terminated!]
20:24xfim has joined #asahi
20:26psykose has quit [Remote host closed the connection]
20:27psykose has joined #asahi
20:43kaprestsHow is the notch on the 14 and 16 inch macbook pro's handled? Is it just up to the window manager or DE how to deal with it?
20:48touttti has quit [Remote host closed the connection]
20:49marcanthere's an issue in progress for figuring out how to deal with notches and the like in Wayland, but for now there is no support
20:49marcanonce there is some agreed mechanism we'll expose it (optionally), until then we'll hide it
20:52kaprestsI see makes sense. Is there any work for supporting it in X? And what are the difficulties? I seems simple to just place a status bar up there, with room in the middle, but I suppose there would have to be some way to deal with full screen mode
20:56kaprestsj'ey: Yea, but with a 'static' layout that should be no problem right? Say a simple polybar with no middle-modules and fixed with modules on the sides?
20:57j`eykaprests: yeah, you can do some work arounds, but the plan is to make wayland or whatever aware of it :)
20:58kaprestsYea, I guess it's better and more "safe" to do it that way, but would be cool if the whole screen could be exposed in some way for those who want to play around with the workarounds
21:00kaprestsOh aha, if it's not too difficult maybe I'll give it a try. Will be getting the 14 inch from work in a couple of weeks :)
21:00j`eyget_notchless_fb in src/kboot.c, I think it should just be as easy as not calling that function
21:01vmeson has joined #asahi
21:10ChaosPrincessat least they found the light and turned esc from a touchbar area into a physical button
21:31xfim has quit [Ping timeout: 480 seconds]
21:52lgarylmtdlt^ has quit [Ping timeout: 480 seconds]
22:03roxfan has quit [Ping timeout: 480 seconds]
22:20lgarylmtdlt^ has joined #asahi
22:23reillyeon has quit [Quit: The Lounge - https://thelounge.github.io]
22:23reillyeon has joined #asahi
23:02lgarylmtdlt^ has quit [Ping timeout: 480 seconds]
23:45boardwalk has quit [Quit: Ping timeout (120 seconds)]
23:45boardwalk has joined #asahi
23:48emenesesayc[m] has joined #asahi