#
✕ nick:agraf
#asahi-dev · 2023-06-15 22:17
agrafsven: Yup, still looking for volunteers :)
#asahi-dev · 2022-01-26 22:16
agrafjannau: I see :). Well, definitely something you can work around by blending manually I guess. Or fiddling with the overlay plane's size & contents.
#asahi-dev · 2022-01-26 22:06
agrafOh, so the whole screen stops rendering?
#asahi-dev · 2022-01-26 22:03
agrafAnd yes, xvideo. Obviously not with the cursor pane but with a generic one. But I assumed you implement generic pane support in the DRM driver?
#asahi-dev · 2022-01-26 22:03
agrafjannau: if it only has 4 total, that leaves 2 generic overlay panes to use, no? :)
#asahi-dev · 2022-01-26 21:56
agrafjannau: Also, what happens when you move towards the edge? It just won't keep moving, so the cursor stays fully displayed while it should be half hidden?
#asahi-dev · 2022-01-26 21:55
agrafjannau: Nice, does that work automatically with xv as well? :) I remember that was the mechanism of the day ~20 years ago to overlay video inside a window quickly. Feels so out of touch now that everything is texture rendered
#asahi-dev · 2021-11-05 16:36
agrafkettenis: yeah, or maybe find something completely separate for us to store varstore data in the SEP. The only downside to that would be that you'd lose SEP access from Linux (because it's owned by UEFI RTS then), but that's probably something perfectly ok for most people
#asahi-dev · 2021-11-05 11:40
agrafkettenis: That works too, you'd basically end up with single-distro as well though, because of lack of UEFI variables :). I'm happy with that as well. Just not terribly thrilled about an installer poking at file systems that are not provided by itself (ESP) :)
#asahi-dev · 2021-11-05 08:39
agrafIt definitely isn't the "easy" route for not-heavily-sophisticated users though. That's more likely to be the SBC image.
#asahi-dev · 2021-11-05 08:38
agrafThat's something that would work with the flow above as well (modulo all the hazard that goes along with running the actual installer because it may not be fully aware that it needs to preserve the partition layout). Just use the "installer iso" (which also has an ESP and normal partitions) instead of the "SBC image" as target image.
#asahi-dev · 2021-11-05 08:29
agrafchadmed: because you need all the macOS system partition setup magic, no? How would you deal with that?
#asahi-dev · 2021-11-05 08:29
agrafmarcan: My point was that you don't want to dictate any of the post-UEFI-App flow. If a distro wants to use systemd-boot, they should be able to. If they want to patch grub with awkward config options, they should be able to
#asahi-dev · 2021-11-05 08:28
agrafmarcan: perfect :)
#asahi-dev · 2021-11-05 08:27
agrafchadmed: I don't think that's really possible. The installer flow on Apple Silicon would most likely be a macOS application that then runs/mimicks the distro installer
#asahi-dev · 2021-11-05 08:25
agrafAnd that's absolutely a useful goal to have, I just don't know if it should be step 1 ;)
#asahi-dev · 2021-11-05 08:25
agrafchadmed: Again, if you want anything more sophisticated than "take an image and throw it onto the system", you're in the land of "distro provides its own installer"
#asahi-dev · 2021-11-05 08:24
agrafchadmed: But that's the whole point - the above uses ARM SR images and mangles them into an Apple compatible environment
#asahi-dev · 2021-11-05 08:20
agrafchadmed: no, rootfs doesn't give you distro ownership of kernel and UEFI payload (grub) for example - very bad idea
#asahi-dev · 2021-11-05 08:19
agrafchadmed: but we're talking about bootstrapping an ecosystem here for the "easy" route.
#asahi-dev · 2021-11-05 08:18
agrafchadmed: that flow is something that distros will then need to enable themselves. If a distro really wants to provide all of that flexibility, give them the tools to provide their own installer that gives you all these knobs
#asahi-dev · 2021-11-05 08:16
agrafThat way you also pave a very natural path into passing ownership of almost everything to distros. You wouldn't be in the business of owning the kernel for example.
#asahi-dev · 2021-11-05 08:16
agrafAnyhow, IMHO best would be to build a workflow around the already existing ARM SBC images - even if you don't actually dd them over. Then document a few requirements you put onto that image to be Asahi compatible.
#asahi-dev · 2021-11-05 08:14
agraf(which is probably accurate for 99% of users out there)
#asahi-dev · 2021-11-05 08:14
agrafI believe most distros will assume that "free space at the end" means "space I can use to grow into"
#asahi-dev · 2021-11-05 08:13
agrafHeh, ok :)
#asahi-dev · 2021-11-05 08:13
agrafHow important is "leave unallocated space" really? :)
#asahi-dev · 2021-11-05 08:12
agrafOk, another thing to make sure you document properly. I don't know if all first boot scripts will growfs if they don't also resize
#asahi-dev · 2021-11-05 08:11
agrafdata*
#asahi-dev · 2021-11-05 08:11
agrafI think you'll have distros editing the GPT on first boot by default for expanding the date partition, no?
#asahi-dev · 2021-11-05 08:10
agrafBut again, start with "easy to work with for distros" and "extensible later if necessary" :)
#asahi-dev · 2021-11-05 08:09
agrafmarcan: I know of 1 compelling argument for PARTUUID: They work for finding a roofs without initramfs
#asahi-dev · 2021-11-05 08:08
agrafmarcan: to make sure nobody relies on static PARTUUIDs
#asahi-dev · 2021-11-05 08:08
agrafmarcan: I think that works, but it means you'll need to also document it as part of the installer/distro contract :)
#asahi-dev · 2021-11-05 08:08
agrafmarcan: and that means you limit their ability to change things. What if I want to build a btrfs based image tomorrow? Or one with 5 partitions?
#asahi-dev · 2021-11-05 08:07
agrafmarcan: UUIDs are intrinsically in distros' turf. You don't want to even remotely know about them, otherwise you pull yourself too deeply into the details of how the distros build their images :(
#asahi-dev · 2021-11-05 08:06
agrafmarcan: Maybe you also add an additional piece that says "You have to regenerate the UUID on first boot" to solve dual-boot
#asahi-dev · 2021-11-05 08:05
agrafmarcan: You can tell them "Always rely on UUIDs"
#asahi-dev · 2021-11-05 08:05
agrafmarcan: Yes, but that's just part of the things you tell distros as part of your contract
#asahi-dev · 2021-11-05 08:05
agraf"yes, and those are SBCs, not real computers" -> That's a very difficult argumentation line :). Modern SBCs are easily in the same performance ballpark as "real computers" a few years ago. And their user base isn't necessarily more or less sophisticated either
#asahi-dev · 2021-11-05 08:03
agrafI think it'd be easiest / best to stick to that as closely as possible
#asahi-dev · 2021-11-05 08:03
agrafDistros today all have existing dd'able images for ARM SBCs
#asahi-dev · 2021-11-05 08:03
agrafI don't know if local dual-boot is all that terribly important. It makes everything a lot more complicated
#asahi-dev · 2021-11-05 08:02
agrafYes, that's part of the distro's responsibility
#asahi-dev · 2021-11-05 08:01
agraf"resize the data partition": The already existing one?
#asahi-dev · 2021-11-05 08:00
agrafYou'd also want to make sure that U-Boot searches the ESP per GUID rather than hardcoded "first partition" - not sure that's there yet
#asahi-dev · 2021-11-05 07:59
agrafYes, not today :)
#asahi-dev · 2021-11-05 07:59
agrafFor step 3: It would copy contents as well as PARTUUID and GUID of these partitions of course
#asahi-dev · 2021-11-05 07:58
agraf5) Copy U-Boot / edk2 into 2nd OS APFS container as kernel
#asahi-dev · 2021-11-05 07:58
agraf4) Find ESP GUID, copy firmware files inside

plus ›