#asahi-dev · 2025-05-23 16:00
LarwiveHi, I want to contribute to the project. I have a M3 pro. I'm thinking about testing code, as the contribution page advised.#asahi-dev · 2025-05-22 15:32
svenyeah, we really don't want to corrupt that thing#asahi-dev · 2025-05-22 15:27
nickchanif gigalocker is corrupt then the init_data_protection boot-task in macOS should fail#asahi-dev · 2025-05-22 15:25
nickchanand normal macOS will obviously not boot as well since data volume is always encrypted#asahi-dev · 2025-05-22 15:24
nickchansven: i think breaking xarts would outright make the boot picker (recoveryOS) not boot - not actually tested though#asahi-dev · 2025-05-22 15:11
nickchani don't think there's rw apfs fuse drivers#asahi-dev · 2025-05-22 13:25
j`eyhttps://github.com/sgan81/apfs-fuse read only though#asahi-dev · 2025-05-22 13:22
svenbecause if it does you lose access to e.g. all encrypted data on the macos volumes#asahi-dev · 2025-05-22 13:22
svenis there a apfs-fuse driver? we'll have to test that one very well so make sure it doesn't corrupt that xARTs partition in any way#asahi-dev · 2025-05-22 13:19
svenprobably#asahi-dev · 2025-05-22 13:12
alyssasven: FUSE sounds like the sanest for SEP no?#asahi-dev · 2025-05-22 10:22
svenlooks like smc will be merged after -rc1 🥳#asahi-dev · 2025-05-22 08:45
svenlet me put it differently: I don't care much about apfs support in the kernel honestly but I'm also not going to complain if someone else manages to get it upstream #asahi-dev · 2025-05-22 08:44
nickchanprobably safe to assume that corellium interanlly uses that module for something too so there's commerical interest#asahi-dev · 2025-05-22 08:44
nickchanlinux-apfs-rw maintainer does has an incentive to maintain it since it's corellium code and that guy works at corellium#asahi-dev · 2025-05-22 08:43
svenbut as long as we don't have to maintain it ;P#asahi-dev · 2025-05-22 08:42
svenyup#asahi-dev · 2025-05-22 08:42
j`eybut a big burden, code wise#asahi-dev · 2025-05-22 08:42
svenit would just make it a bit more convenient and less hacky#asahi-dev · 2025-05-22 08:41
j`eybut it sounds like AFPS driver wouldnt help for the SEP use case then#asahi-dev · 2025-05-22 08:40
nickchani don't think kernel space access is really needed unless one wants to access SEP encrypted apfs from the kernel which no linux driver can do right now even for normal encryption#asahi-dev · 2025-05-22 08:39
svenso unless we want to parse that protocol in kernel space which doesn't seem like a good idea it's all userspace access#asahi-dev · 2025-05-22 08:38
svengigalocker is a key/value store and SEP just requests reads/write from there through its protocol#asahi-dev · 2025-05-22 08:38
nickchanand then an OS may need multiple volumes for different purposes and that's what the volume role is for#asahi-dev · 2025-05-22 08:38
svenj`ey: so, uh, open(/dev/nvme0ns0p3) and then just read/write essentially#asahi-dev · 2025-05-22 08:38
j`eysven: oh ok#asahi-dev · 2025-05-22 08:37
nickchansven: volumes in a container share space (though optional fixed allocations could be made) . To tell which volume is for which OS there are "volume groups"#asahi-dev · 2025-05-22 08:37
sventhe access would happen from asahi-sepd from userspace anyway#asahi-dev · 2025-05-22 08:36
j`eyand SEP driver would use some block(?) APIs in the kernel directly?#asahi-dev · 2025-05-22 08:36
svenso we can kinda bypass all the apfs crap once we know where it is#asahi-dev · 2025-05-22 08:36
svenbut it's stored contiguously on the disk#asahi-dev · 2025-05-22 08:35
svenruntime#asahi-dev · 2025-05-22 08:35
j`eyis the gigalocker stuff used at SEP runtime, or would it just be m1n1?#asahi-dev · 2025-05-22 08:35
sventhe gigalocker thing we can also hack: figure out the offset of the file from m1n1 inside that disk image and then just use raw disk r/w to modify it#asahi-dev · 2025-05-22 08:35
svenwhat might be interesting for users is that apple container(?) feature where they could have a volume for macos and one for linux that share the available space. not sure if the apfs driver supports this or if that's even something users want#asahi-dev · 2025-05-22 08:35
j`eyhard to know how many people from stats.asahi would actually want this#asahi-dev · 2025-05-22 08:32
nickchanthe gigalocker file probably isn't much of an io burden#asahi-dev · 2025-05-22 08:32
nickchanBut maybe that entirely falls in what should be handled by fuse not sure#asahi-dev · 2025-05-22 08:31
nickchanin reference to this https://lore.kernel.org/asahi/n7kkoptktdvldadvymcfmnaw3yqbk6bfmzpxvgdkpsvvpc3p7i@ilqcgz7wur7i/ and stats.asahilinux.org does have some sizable numbers#asahi-dev · 2025-05-22 08:30
nickchannow granted that is an usecase that only uses a small part of the filesystem code#asahi-dev · 2025-05-22 08:29
nickchanfor the interest of having apfs in the kernel would it be safe to assume every asahi linux user would be using it eventually as part of using the SEP's xART gigalocker file? that usecase be sufficiently common#asahi-dev · 2025-05-21 16:34
fl0_idoh well guess i can wait#asahi-dev · 2025-05-21 16:34
fl0_idstarted compiling with only one core... oops#asahi-dev · 2025-05-21 14:41
chaos_princessi've just copied whatever asahi-kernel ebuild used#asahi-dev · 2025-05-21 14:41
alyssachaos_princess: new url :o#asahi-dev · 2025-05-21 14:36
fl0_idthx#asahi-dev · 2025-05-21 14:23
chaos_princesshttps://asahi.jannau.net/cgit/@asahi/kernel/kernel.git/plain/kernel-aarch64-16k-fedora.config?id=6e09c88d5eaa7f010172a239e620b917fcbb108b#asahi-dev · 2025-05-21 14:22
fl0_idI was looking for it on github, but didn't see it#asahi-dev · 2025-05-21 14:21
fl0_idwithout having asahi installed, is there an easy way to get the asahi kernel config? (for compiling elsewhere for testing purposes)#asahi-dev · 2025-05-21 09:20
fl0_idmmh they're gone again. I could also assist with running things on m3. though tbh I didn't bother with stage2 anything yet