#
…

2021-05-05

00:04odmir has quit [Ping timeout: 260 seconds]
00:08krbtgtkettenis: petitboot is a bit of an oddity indeed
00:08krbtgtapparently it's better than forth according to the IBMers i asked who chose it D:
00:15matt6 has quit [Ping timeout: 265 seconds]
00:30odmir has joined #asahi
01:15riker77 has quit [Ping timeout: 260 seconds]
01:16riker77 has joined #asahi
01:30odmir has quit [Ping timeout: 260 seconds]
01:57odmir has joined #asahi
02:22odmir has quit [Remote host closed the connection]
02:22odmir has joined #asahi
02:27odmir has quit [Ping timeout: 240 seconds]
02:37Namidairo has joined #asahi
02:38PhilippvK has quit [Ping timeout: 250 seconds]
02:39phiologe has joined #asahi
03:05gabiruh has quit [Remote host closed the connection]
03:05gabiruh has joined #asahi
03:06marvin24 has quit [Ping timeout: 250 seconds]
03:06marvin24 has joined #asahi
03:13crabbedhaloablut has quit [Ping timeout: 260 seconds]
03:14crabbedhaloablut has joined #asahi
03:29Namidairo has quit [Ping timeout: 268 seconds]
03:31crabbedhaloablut has quit [Ping timeout: 240 seconds]
03:33crabbedhaloablut has joined #asahi
03:53illya has quit [Quit: ZNC - https://znc.in]
03:56illya has joined #asahi
04:00crabbedhaloablut has quit [Ping timeout: 268 seconds]
04:02crabbedhaloablut has joined #asahi
04:30Namidairo has joined #asahi
04:42the-mentor3 has quit [Quit: The Lounge - https://thelounge.chat]
04:42the-mentor3 has joined #asahi
05:17VinDuv has joined #asahi
05:44Bublik_ has joined #asahi
05:46Bublik has quit [Ping timeout: 246 seconds]
06:04jeffmiw has joined #asahi
06:08jeffmiw has quit [Ping timeout: 240 seconds]
06:19VinDuv has quit [Quit: Leaving.]
06:25TheJollyRoger has quit [Quit: TheJollyRoger]
06:29Bublik has joined #asahi
06:31Bublik_ has quit [Ping timeout: 246 seconds]
07:10arndkrbtgt: the Sony PS3 was the original target for petitboot, and it could already boot a linux kernel that would only run on the ps3, so kexec was the easiest way to load a distro kernel
07:12JTLI always foudn it amusing that petitboot kind of originated from the PS3 homebrew scene
07:12JTLfound it*
07:12JTLand now it's used on IBM POWER hardware, some ARM boards, buncha other stuff :P
07:22tmlindfyi, there's also kexecboot that is a much simpler solution for folks needing a kexec gui
07:48ponikrf[m] has joined #asahi
08:14herbas has joined #asahi
08:21mazthere is also a set of patches that allow grub to run in *cough* userspace and use kexec as a backend. pretty neat for distro kernels.
08:36herbas has quit [Quit: herbas]
08:43raster has joined #asahi
09:43matt6 has joined #asahi
09:43matt6 has quit [Client Quit]
09:44matt6 has joined #asahi
09:44matt6 has quit [Client Quit]
09:44matt6 has joined #asahi
09:51matt6reject FORTH, accept TCL :P
09:52anarsoul has quit [Ping timeout: 245 seconds]
09:54anarsoul has joined #asahi
10:05Bublik_ has joined #asahi
10:06Bublik has quit [Ping timeout: 240 seconds]
10:09agnem has quit [Ping timeout: 260 seconds]
10:13agnem has joined #asahi
10:23JTL has quit [Ping timeout: 260 seconds]
10:26agnem has quit [Ping timeout: 260 seconds]
10:29klaus has quit [Ping timeout: 240 seconds]
10:29agnem has joined #asahi
10:31JTL has joined #asahi
10:40klaus has joined #asahi
10:49mazoddly enough, I really like Forth. I'll have my head checked...
11:05svenlol, grub in userspace :D
11:05sventhat sounds, er, fun
11:13kettenisI actually considered doing something like that when porting OpenBSD
11:13kettenisrunning the OS bootloader as a linux userland process
11:14kettenisbut the default petitboot environment doesn't really allow you to do that
11:23taziden has quit [Ping timeout: 245 seconds]
11:53m0drobert is now known as modrobert
11:54pipcet[m]sven: I don't think we want grub in userspace, but I suspect we'd be happier with the device tree mangling in userspace. The main problem kexec has and had is that the old kernel may leave hardware in a bad state, and that's not an issue for us as the first kernel doesn't even need to touch the interrupt controller or anything.
11:55mazthat's the patch hacked on to get it a bootloader on kevin.
12:19taziden has joined #asahi
12:21ephe_meral1 has joined #asahi
12:29segher_ is now known as segher
13:01choozy has joined #asahi
13:10jeffmiw has joined #asahi
13:14jeffmiw has quit [Ping timeout: 240 seconds]
13:20maknho___ has quit [Ping timeout: 252 seconds]
13:21maknho___ has joined #asahi
13:34modrobert has quit [Read error: Connection reset by peer]
13:35modrobert has joined #asahi
14:39maknho____ has joined #asahi
14:41maknho___ has quit [Ping timeout: 260 seconds]
14:48maknho has joined #asahi
14:51maknho____ has quit [Ping timeout: 240 seconds]
15:10choozy has quit [Remote host closed the connection]
15:15pipcet[m]do we have any way at all of loading macos if it isn't currently configured to be the boot OS? I tried installing the macos .macho as a custom kernel but could not get that to boot.
15:16pipcet[m]or to emulate it (https://worthdoingbadly.com/xnuqemu2/ doesn't work on actual kernels), or to get a memory image of a running macos system (I don't suppose they have /dev/mem :-) ), or anything like that? Because without a way of doing that, I don't see how all this hypervisor work will ever pay off.
15:39svenuh, by writing code that loads xnu and jumps to it under the hypervisor?
15:45pipcet[m]"writing code that loads xnu" is the problematic part, I fear.
15:46sveni don't
15:48pipcet[m]so which macho would we use? The .kc machos do not have plain AArch64 instructions in them.
15:48svenwhat do you mean with "not plain aarch64 instructions"?
15:48pipcet[m]running objdump on them produces gibberish :-)
15:49pipcet[m]the data section is fine, the code section...isn't.
15:49rwhitby has quit [Ping timeout: 250 seconds]
15:49rwhitby has joined #asahi
15:50sveni'm not sure what you're doing then but i didn't have any issues
15:51pipcet[m]maybe it's a macos version thing, and older machos work fine.
15:52pipcet[m]but so far the "load xnu and jump to it" part doesn't seem trivial to me. If it is, we should get that done first, I think, because that would give us debugging information even without a hypervisor.
15:55svenwhy would that give us any additional debugging information?
15:55pipcet[m]memory image of a working macos system? Hardware state while it's running?
15:56sventhat's *much* easier with the hypervisor up and running
15:56svenbut if you disagree: feel free to explore that direction :-)
15:57pipcet[m]you appear to be saying that it should be trivial to boot macos from, say, Linux, and the difficult bit is getting a hypervisor in. I think it's the opposite.
15:58pipcet[m]maybe we're both partly right and both parts are easy
15:58sveni'm not sure it would be easy from linux but it's going to be relatively easy from m1n1 when almost no hardware is up and running
15:59pipcet[m]why "going to be", though? If it's the easy part we should do it first, to see whether it isn't actually tricky or impossible.
15:59pipcet[m]and we're going to have to do it anyway before the hypervisor would be very useful
16:00svenwell, the code is open source. feel free to start working on that :)
16:00choozy has joined #asahi
16:00pipcet[m]yes, I have. And I've run into problems. That's why I think it's hard.
16:01jixhmm to me it seems there are two outcomes when trying this before the hypervisor is complete enough... a) jumping to the macos macho works right away b) it doesn't ... in case of a) there's nothing to do, in case of b) you'd probably want the hypervisor to be able to debug things
16:01yrlfpipcet: we can probably easily chainload MacOS from m1n1 (load it and jump in, basically), but without a hypervisor, that will not really be useful, since it effectively does the same as booting MacOS normally
16:02yrlfwith a hypervisor we can look and see what MacOS is doing while it's running
16:02pipcet[m]what would you even jump to?
16:02pipcet[m]the macho does not contain instructions that objdump or the CPU understand
16:03pipcet[m]yrlf: there are plenty of tricks we can play without a hypervisor...
16:06j`eypipcet[m]: well it must contain arm64 instruction?
16:06svenit does
16:07yrlfas far as I understand it, iboot2 will load the MachO, and jump to the entrypoint (same as it does with m1n1)
16:07yrlfthere's no reason why the MacOS binary should be different
16:08svenit isn't
16:08yrlfyeah, that makes sense
16:08j`eybut m1n1 doesnt support macho yet, right?
16:09yrlfj`ey: marcan added some stuff
16:09yrlf(e.g. proxyclient/macho.py)
16:09yrlfalso, when m1n1 chainloads itself, it loads a macho
16:10sventhat's not enough for a xnu macho though
16:10svenit only implements the minimal requirements
16:10yrlfsure, for a kernel image you'd have to extend that, right
16:10yrlfso it does not work out of the box yet, but it's not _that_ far off if I understand this correctly
16:11svenpretty much. it might need some reverse engineering of undocumented macho headers (or however that format works) but i'm willing to bet it's possible to figure those out by staring at them
16:17svenpipcet[m]: so i'm not sure what you're looking at but the latest mac os kernelcache still contains plain aarch64 instructions
16:18j`eysven: are you using objdump or otool?
16:19sveni, er, coerced an elf objdump to just disassemble everything
16:20yrlfusually, if I just want to disassemble something that the normal tools don't like I use radare2. though the more I learn about that tool the less I want to use it for that
16:21yrlf(I'm pretty sure if you throw the wrong binary at it you can easily get code execution from it)
16:21svenfor serious reverse engineering i generally stick to ghidra or ida pro. for quick glances objdump works fine though
16:21yrlfcase in point: it segfaults if you try to use it on m1n1.nacho
16:21yrlf*macho
16:31KindOne has quit [Quit: K-Lined]
16:56VinDuv has joined #asahi
17:10zkrx has quit [Ping timeout: 240 seconds]
17:12marcanpipcet[m]: the macos macho absolutely boots as a custom kernel
17:12marcanthat is the entire point
17:12marcanthe very first test I did to convince myself kmutil worked was patch the darwin version string to say "Linux" and boot it
17:13marcanworked fine (and that also kills any conspiracy theories about apple "blocking" anything for custom kernels)
17:13marcanthis is retail darwin, not a xnu source dump build, so everything enabled
17:13marcanI assume the only thing that wouldn't work is SEP-mediated DRM
17:14marcan(and this also means my hypervisor stuff *will* work, modulo a as-yet unconfirmed level of fuckery to deal with corner cases due to macos running in EL1 not EL2, but by definition nothing insurmountable)
17:15marcanand objdump absolutely disassembles it fine, so you must be doing something weird ;)
17:16marcanand yes, what I want to do could be accomplished with kexts, or with a patched FOSS XNU build, or any other number of ways
17:16marcanI chose the hypervisor approach because I liked it initially, and it is proving to have been an *excellent* idea because it also becomes a magical debugger for m1n1 and Linux themselves that anyone will be able to use, without a serial cable. built in USB to serial.
17:18marcanwill do more dev in the next 1-2 days; chances are good I'll have serial over a secondary CDC-ACM brought up really soon and that will mean anyone can load Linux kernels and debug m1n1 and Linux (and u-boot or whatever) bring-up with zero special hardware or cables or fuss, which is a big win
17:18marcan(single core initially, multicore will come a bit later, but that's good enough for a lot of work)
17:19marcansven: ghidra sadly barfs on current kernelcaches, but I'm trying to avoid disassembling anything at this point so I don't care
17:20marcanthe only thing I ended up doing in the early days was objdumping the xnu init section to figure out exactly what chicken bits Corellium got from there (and that told me they didn't know what they were doing and had copied useless stuff and added some of their own, so it was a good thing I did it :P)
17:20marcannot planning on ever looking at it again :)
17:33zkrx has joined #asahi
17:39pipcet[m]marcan: excellent news! As I said, on my device the kernel cache does not contain plain aarch64 instructions, and doesn't boot when installed as a custom kernel.
17:40marcanwhat are you calling the "kernel cache"?
17:40marcanif you mean the kernelcache file, that would be an img4 wrapper built by kmutil; you need to extract the mach-o from it first before feeding it back to it
17:40pipcet[m]it's a macho here.
17:41marcan$ aarch64-linux-gnu-objdump -D -b binary -m aarch64 kernelcache.macho | grep cntp
17:41marcan d514e4: d51be228 msr cntp_ctl_el0, x8
17:41marcan d51fb4: d51be228 msr cntp_ctl_el0, x8
17:41marcan d520dc: d51be228 msr cntp_ctl_el0, x8
17:41marcan d6d95c: d53de248 mrs x8, cntp_cval_el02
17:41marcanjust plain feeding it all brute force through objdump produces obvious code
17:42marcanunless something changed since january, which is when this is from
17:42roxfanpipcet[m]: pastebin the hexdump of firsr 0x200 or so bytes
17:43pipcet[m]possibly. the same line here gives no hits that are actual msr insns.
17:45roxfanthe header does look like a valid mach-o
17:47pipcet[m]yes. it does seem like a valid mach-o to me.
17:48marcanjust did it with my installed kernelcache, 11.2.3, 20D91, still yields valid code
17:49marcanlet me upgrade to 11.3.1...
17:50pipcet[m]let me boot into macos
17:51marcangoing to sleep now but I can confirm this tomorrow
17:52pipcet[m]that would be awesome!
17:52marcanmake sure you're looking at the right file (/System/Volumes/Preboot/*/boot/*/System/Library/Caches/com.apple.kernelcaches/kernelcache)
17:52pipcet[m]if it's a new apple trick we should probably work with the older version for now
17:52marcanyes, that shouldn't be a problem
17:52marcanthough I'm at a loss as to why they would do anything like this
17:53marcanand either way, they *are* releasing XNU source dumps; it might even be *easier* to do this with such a FOSS build, as those lack hypervisor support
17:53marcanwhich is good for us
17:54flying_sausages_ has quit [Quit: You just lost the game. Peace Out.]
17:54marcanonly reason I can think of why they'd encrypt XNU is to further obfuscate the M1-isms, though that cat is thoroughly out of the bag and if they do so I'm pointing squarely at ARM's lawyers being idiots
17:55marcanI mean they don't even encrypt iOS last I checked, haven't for a long time
17:55pipcet[m]it doesn't look encrypted. repetitive, compresses well. Just not valid insns.
17:55marcanare you sure you're disassembling in little-endian aarch64?
17:55flying_sausages has joined #asahi
17:56marcan$ hexdump -vC kernelcache | grep "28 e2 1b d5"
17:56marcandoes that hit? :p
17:57dhewgbuggy binutils version? I've had plenty of those
17:57marcanor buggy img4 tooling
17:58marcanthere is decompression involved
17:58marcanif that goes wrong I could see ending up with a good-looking but very borked kernel image
17:59pipcet[m]I'd appreciate any help, but it looks like my concerns seem specific to my machine so far (purchased in March)
18:00pipcet[m]maybe it's the limited rot-13 code edition.
18:02pipcet[m](great, it forgot my backlight brightness settings again)
18:04marcanpipcet[m]: upgrade isn't done yet but I lifted the staged kernelcache from the upgrade volume
18:04marcanstill disassembles fine
18:04marcanfor reference: Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:41 PDT 2021; root:xnu-7195.101.2~1/RELEASE_ARM64_T8101
18:05marcanimg4 has sha1 221763401520819850b4a71ff00ab0dab9b55108; mach-o has sha1 5a652f986f3fa29c69c94a046a9a7122cc115a41
18:05marcanunless I got confused this should be 11.3.1 which I think is the latest public version
18:06marcanso yeah, I don't know what's wrong with your kernelcache :)
18:08marcanoff to sleep now
18:08roxfanaha, you're looking at x64 kcache
18:09roxfanyou need to find the ARM one
18:09marcanI did ask if he was looking at the right file :p
18:09roxfanKWGHtuZw.bin: Mach-O 64-bit x86_64 filetype=12
18:10pipcet[m]it says "Darwin Kernel Version 20.3.0...RELEASE_ARM64_T8101"
18:10pipcet[m]and I don't have an x86_64 mac I could have confused that with.
18:10marcanthe OS is universal
18:10marcanthe x64 kernelcache is somewhere on disk on M1 macs
18:10marcanjust not where I told you to look for the file :P
18:11flying_sausagesany chance for an update here? :p https://asahilinux.org/blog/
18:11marcanflying_sausages: soon, sorry, I have an update pending but got too caughed up in hypervisor development :)
18:12pipcet[m]well, that's that mystery resolved then.
18:12marcanI'll do a catch-up march post on the upstreaming stuff, then april-may will probably be a combined update about hypervisor goodies since this month is going to be fun
18:17marcan*caught (damn, I can't english these days)
18:22marcanalso, um, I *thought* booting darwin required more mach-o loading stuff
18:23marcanI was wrong, because I just chainload.py'ed darwin and it worked, framebuffer and serial output and all (didn't get to the desktop, might not even be the right kernel, but whatever)
18:24marcanactually that isn't even setting up the devicetree and trustcache properly; the version in hv.py does.
18:24marcanwonder if *that* works
18:26pipcet[m]will play with it if it does and I can get at the kernelcache...
18:27marcanok, HV does not work :-)
18:27marcanwhich isn't entirely surprising. related to guarded exec I bet (hi sven)
18:27marcananyway, good night :-)
18:28pipcet[m]good night, and sorry for the confusion.
18:36svenmarcan: i never tried loading anything in ghidra. so far i've just used objdump to find the entry register for guarded exec and that's it :D
18:36svenbut yeah... let me document the guarded exec stuff for real now
18:37marcanfwiw, this is a far as darwin gets when chainloaded: https://mrcn.st/p/jNkTDWj6 (again this may or may not even be the right kernel for the current iboot2/sfr...)
18:37marcanlong delay after the SEP stuff; I did push a bit that was missing but it didn't help
18:37marcanthen more delays on the USB stuff
18:37marcanthen it panics on pcie
18:38marcanwill try tomorrow with the right kernel :)
18:38pipcet[m]...okay, macos lets me have a different image, and that chainloads a little. I must have done something wrong in the recovery terminal
18:38svenohhh... i messed up with guarded exec stuff actually :D
18:38sveni think it'll work just fine
18:38sveni confused PXN and UXN
18:39marcanwell, running it under the hv right now just hangs, no output or anything
18:39marcanwhich suggests an EL1 exception
18:39sventhough... it's strange that it doesn't hit an undefined MSR
18:39marcanthose are *EL1* exceptions
18:39marcan(because ARM)
18:39svenokay, that makes sense
18:39svenyeah, so that's gonna be ugly
18:39svenbecause you need SPRR enabled in EL2 to make it work in EL1
18:39svenand with SPRR you no longer get rwx pages
18:40marcanprobably the next thing I'll do is hook VBAR and add my own exception vector hooks that just hypercall on anything "interesting" like undefined instruction syndromes
18:40marcanand then I can fix things up in EL2 that way
18:40marcan(I *can* hook VBAR writes)
18:40svenbut i think you can just fake the guarded stuff
18:40marcanI think there's a good chance just hooking all undefined instruction exceptions will let me do what I want
18:41marcan(I hate ARM for not letting me just flip a bit to do that, unless I missed something / cc maz)
18:41marcan(I mean without NV)
18:41svenyou'll probably need to emulate the GL1 msrs
18:41svenyou get ELR,FAR,etc._GL1
18:41marcandocs please :)
18:41svenyeah, yeah, working on it now :D
18:42marcanthere is that "hook all impdef MSRs" bit though
18:42marcanwhich is *probably* enough
18:42marcanthen I don't need the vbar hook, but conversely I need to emulate all the *others*
18:42marcanhowever, apple has those per-class bits
18:43marcansven: got an encoding for one of those?
18:43svengexit?
18:43svenor the msrs?
18:43marcanI mean any msrs
18:43sven#define SYS_SPRR_CONFIG_EL1 sys_reg(3, 6, 15, 1, 0)
18:44sven#define SYS_GXF_CONFIG_EL1 sys_reg(3, 6, 15, 1, 2)
18:44svenfirst one enables sprr, second one the guarded stuff
18:44marcanwhat about ELR, FAR, etc?
18:45sveni've got all of them :D
18:45marcangive me one of those
18:45sven#define SYS_ELR_GL1 sys_reg(3, 6, 15, 10, 6)
18:45marcanah, not accessible by default I guess
18:45svennope, only from GL1 itself
18:46marcanhttps://mrcn.st/p/RA2VE5CV anyway there are your trap bits, and I bet bit 12 is related (trap instructions maybe?)
18:46sven(or GL2 for that matter. that thing is aliased to SYS_ELR_GL2 as well)
18:46marcanmakes sense, VHE style
18:46marcanwhich is also good for us if we need to let macos actually run in this mode
18:47svenso all this crap is disabled from hypervisor.framework
18:47svenbut i'm pretty sure you can enable it
18:47zkrx has quit [Ping timeout: 252 seconds]
18:47svenyou just need com.apple.private.hypervisor or something like that
18:47sveni'm pretty sure they *want* to run xnu in el1
18:48marcanI'm pretty sure they are planning on making this work at some point in the future
18:48marcanalso fwiw I don't care *too* much about w^x; I already had a similar problem with EL0 and solved it with a mirror. wouldn't be a big deal doing something similar for call() in the proxy if it comes to that.
18:48svenyeah, so if you don't care about rwx it's very simple to let m1n1 run with sprr as well
18:48svenit kinda already works if you keep the MMU disabled ofc
18:49marcanI only use self-modifying code from python; m1n1's stuff should already be w^x and properly page aligned, I did it properly from the get go
18:49marcanjust never bothered enforcing it
18:49svenso then we probably just need to move the stack to a rw alias
18:49svenand the malloc stuff
18:50marcanmore like move call() to point to a rx alias
18:50marcanI don't think I ever call() anything that is position-dependent
18:50marcan(and if I do I can fix that)
18:50svenoh, so you mean enable SPRR/GXF in call() and disable it before a return? that should work
18:51marcanoh, I just mean enable it whenever I feel like it, and then just keep call() working by pointing it at a rx mirror
18:51marcanwhile memory is normally otherwise rw
18:51marcan(excepe m1n1 .text)
18:51svenohh... yeah
18:51svenmakes sense
18:52marcanwill probably need to extend your pagetable code to support actual page granularity, or otherwise align m1n1 to larger blocks
18:52marcan... thankfully, I already wrote fancier pagetable code for the HV which I can just copy and paste and simplify :p
18:52marcan(or even probably use as-is if I clean it up a bit)
18:52zkrx has joined #asahi
18:53svenokay, let me clean up my current code which just disables the mmu for p.gl1_call and then write some documentation (and/or a blog post because it's kinda awesome how you can figure this all out by (un)educated guesswork)
18:53KindOne has joined #asahi
18:53marcanactually, there is some reason to implement self-reloading for m1n1, which would amount to copying .data from a stash and clearing .bss and jumping to the entry
18:54marcanwhich is a reason to have the .data image in the mach-o not be the real link address
18:54marcanand then I can align the latter
18:54marcananyway, ideas ideas
18:54marcangood night, seriously
18:54svennight :D
19:34maknho_ has joined #asahi
19:35maknho has quit [Ping timeout: 240 seconds]
19:47jeffmiw has joined #asahi
19:49riker77 has quit [Quit: Quitting IRC - gone for good...]
19:52zorun has quit [Ping timeout: 246 seconds]
19:52zorun has joined #asahi
19:58riker77 has joined #asahi
20:06VinDuv has quit [Quit: Leaving.]
20:39choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
20:43ephe_meral1 has quit [Ping timeout: 265 seconds]
20:52jeffmiw has quit [Ping timeout: 252 seconds]
21:07lazarosser[m] has joined #asahi
21:07lazarosser[m]Is there an eta to when Asahi will be ready?
21:09clover[m]Linux 5.13 I think
21:09* etawaves
21:10lazarosser[m]<clover[m] "Linux 5.13 I think"> Will I be able to install on ipad pro?
21:10clover[m]No clue. That would be OP though
21:10j`eylazarosser[m]: that's not an aim at the moment
21:10j`eysince there probably needs to be a boot exploit found for that
21:11lazarosser[m]That makes sense.
21:11svenit's far from "ready" once 5.13 is released
21:11clover[m]Im fine with my pinetab for now :p
21:11lazarosser[m]Since there is work essentially rewriting the whole stack
21:11lazarosser[m]Does this mean that m1 macs could technically be RYF compliant?
21:13skg has quit [Quit: 〜バイバイ〜!]
21:14skg has joined #asahi
21:15clover[m]Ido that acronym
21:15clover[m]* Idk that acronym
21:17lazarosser[m]<clover[m] "Ido that acronym "> RYF "Respects Your Freedom" it is a thing the FSF likes. It means everything is open source in the hardware. With no proprietary blobs.
21:20j`eylazarosser[m]: reat marcan's recent tweets about it
21:22jeffmiw has joined #asahi
21:25jeffmiw_ has joined #asahi
21:25jeffmiw has quit [Read error: Connection reset by peer]
21:29matt6 has quit [Quit: Connection closed]
21:49prusnak has left #asahi [#asahi]
21:50jeffmiw_ has quit [Remote host closed the connection]
22:40TomJepp has quit [Quit: ZNC closing...]
22:42TomJepp has joined #asahi
22:43jeffmiw has joined #asahi
22:47jeffmiw has quit [Ping timeout: 240 seconds]
23:10scubasteve has joined #asahi
23:26scubasteve has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
23:26scubasteve has joined #asahi
23:44odmir has joined #asahi
23:45chivay has quit [Quit: RIP]
23:46chivay has joined #asahi
…