#
…

2021-11-05

00:33kode54kettenis: Ubuntu provides Desktop iso for arm64 too, with a live environment and graphical installer
00:34kode54the 21.xx series even have Plymouth already enabled, not sure about 20.04
00:34kode54the 20.04.2 preinstalled hard drive image that Parallels provides for download has Plymouth disabled and also does verbose boot, so huge text scroller spill on every boot and shutdown/reboot
00:44yuyichao has quit [Ping timeout: 480 seconds]
01:05_aliceARM does have a standard for booting systems in a similar way to regular x86 PCs called SystemReady.... https://developer.arm.com/architectures/system-architectures/arm-systemready
01:05_aliceI think it'd be a good idea to make the u-boot EFI environment similar enough that existing SystemReady ISOs can boot with a device tree (instead of ACPI)
01:06_aliceit'd be the path of least friction for adopting a standard-ish way to install Linux that would also be user-friendly for people coming from x86 PCs
01:50marcansven: I think so, yeah
01:50marcanI think it's by design...
01:50marcandottedmag: the installer won't be setting up LUKS for you
01:51marcanI'm interested in secureboot/FDE-by-default stuff, but that at the very least needs to wait until we figure out the SEP properly
01:53marcan_alice: that is the plan
01:53marcanthat's why we're using u-boot EFI
01:53marcanit should work for anything supporting device tree
03:38kov has quit [Quit: Coyote finally caught me]
03:58phiologe has joined #asahi-dev
04:01PhilippvK has quit [Ping timeout: 480 seconds]
05:16yuyichao has joined #asahi-dev
07:43rkt has left #asahi-dev [#asahi-dev]
07:44rkt has joined #asahi-dev
07:57agrafmarcan: So, what if you're just treating the distro disk image as what it is: A container with partitions and some meta information
07:57agrafmarcan: Your installer would do the following:
07:57agraf1) Shrink system macOS APFS container
07:57agraf2) Inject 2nd OS (Linux) APFS container right after
07:58agraf3) Copy all partitions from the disk image after that 2nd OS APFS container
07:58agraf4) Find ESP GUID, copy firmware files inside
07:58agraf5) Copy U-Boot / edk2 into 2nd OS APFS container as kernel
07:59marcanwe're not using edk2 :p
07:59agrafFor step 3: It would copy contents as well as PARTUUID and GUID of these partitions of course
07:59agrafYes, not today :)
08:00agrafYou'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
08:00marcanso the other thing is we need to resize the data partition to the user specified size
08:00marcanwe'll deal with u-boot, that's not a problem
08:01agraf"resize the data partition": The already existing one?
08:01marcanbut the issue with copying the PARTUUID/GUID as-is is that it breaks with dual-boot, and gets really confusing if you have external disks with installs too
08:01marcanI mean whatever the distro rootfs partition is
08:02marcanthough I think for images like this usually there would be a startup script to do it on first boot
08:02agrafYes, that's part of the distro's responsibility
08:03marcananyway, I'm generally on board with the general flow, which isn't much different from my idea except I was thinking that instead of a disk image I'd use some json/whatever description of the partitions and individual files
08:03agrafI don't know if local dual-boot is all that terribly important. It makes everything a lot more complicated
08:03marcanbut that's an implementation detail
08:03marcanlocal dual-boot is important
08:03agrafDistros today all have existing dd'able images for ARM SBCs
08:03marcanbut yeah, I don't like hardcoded UUIDs
08:03marcanthat just sets users up for trouble in the future
08:03marcanyes, and those are SBCs, not real computers
08:03agrafI think it'd be easiest / best to stick to that as closely as possible
08:04svenmarcan: ok. i was asking because i'm about to submit apple,dwc3 bindings and was wondering if i should also add "t6000-dwc3", "t8103-dwc", "snps,dwc3" instead of just "t8103-dwc", "snps,dwc3"
08:04marcanpeople are going to want to use these things a lot more than they use SBCs, and we also need to assume less experienced users will be more common ;)
08:04marcansven: yeah, go ahead and add t6k
08:05marcanagraf: for dd-able images you can just forgo UUIDs and use device paths or whatever; that's typical on SBCs but won't work for us
08:05agraf"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
08:05agrafmarcan: Yes, but that's just part of the things you tell distros as part of your contract
08:05agrafmarcan: You can tell them "Always rely on UUIDs"
08:06marcansure, but once you use UUIDs now the device is unknown and conflicts are global
08:06marcanI would much, much prefer to have proper unique UUIDs
08:06agrafmarcan: Maybe you also add an additional piece that says "You have to regenerate the UUID on first boot" to solve dual-boot
08:06marcancloning UUIDs is a terrible idea
08:06marcanyeah, *that* could work :)
08:07agrafmarcan: 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 :(
08:08agrafmarcan: 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?
08:08marcananyway, I would at least randomize the PARTUUIDs (or rather: diskutil will do that for me anyway)
08:08agrafmarcan: I think that works, but it means you'll need to also document it as part of the installer/distro contract :)
08:08agrafmarcan: to make sure nobody relies on static PARTUUIDs
08:09agrafmarcan: I know of 1 compelling argument for PARTUUID: They work for finding a roofs without initramfs
08:09marcanI've used them for that
08:10marcanbut I don't want distros editing the GPT on first boot
08:10marcanand I don't want static PARTUUIDs either
08:10agrafBut again, start with "easy to work with for distros" and "extensible later if necessary" :)
08:11agrafI think you'll have distros editing the GPT on first boot by default for expanding the date partition, no?
08:11marcannah, all they have to do is resize2fs
08:11marcanthe actual partition would be created as full size already by the installer
08:11marcan(replace resize2fs with the appropriate dance for the fs/volume management in use)
08:12marcanthis is actually important to do in the installer, because users need to be able to choose how much space to allocate to linux and how much space to leave unallocated for whatever reason
08:12agrafOk, 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
08:12marcanthink e.g. planning to install a second distro
08:13agrafHow important is "leave unallocated space" really? :)
08:13marcanit's important for me :p
08:13marcanresizing things down later to make space for more stuff is more of a pain
08:13agrafHeh, ok :)
08:14agrafI believe most distros will assume that "free space at the end" means "space I can use to grow into"
08:14agraf(which is probably accurate for 99% of users out there)
08:16agrafAnyhow, 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.
08:16agrafThat 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.
08:17chadmedimo the problem with going with the disk image route is that you break the workstation paradigm that desktop users are used to and have been dealing with for... well, decades at this point.
08:17chadmedusers of workstations want to exercise a modicum of control over their disks and how the OS uses them, they dont want some image to just grow itself into all their free space on the first boot like so many ARM images do
08:18agrafchadmed: 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
08:19chadmedi think for the immediate term the best course of action is something gentoo-like, where the distro's responsibility begins with extracting a tarball of their rootfs, and it is an exercise for the user/asahi installer to prepare the disk according to their design. then, beyond that, as kettenis suggests, having compatibility with ARM SR images
08:19agrafchadmed: but we're talking about bootstrapping an ecosystem here for the "easy" route.
08:19chadmedwhich most big distros provide anyway
08:19chadmedmost arm forks of major distros already support the tarball rootfs method, and its simple enough to even integrate into the asahi installer if we so choose. and given that all our patches find their way upstream, we dont even need to take ownership of the kernel.
08:20agrafchadmed: no, rootfs doesn't give you distro ownership of kernel and UEFI payload (grub) for example - very bad idea
08:21chadmedit absolutely does when theyre configured properly. my raspberry pi runs artix, which i simply extracted a rootfs for and installed their kernel package once booted. as i said, the initial boot/handoff to the distro can be very easily automated through the asahi installer since all we will be presenting to users is m1n1+u-boot's efi
08:23chadmedplus, again, the end game should be ARM SystemReady images via uefi. it's what desktop users have come to expect from their machines. i think it is extremely poor form to equivocate the SBC experience with the desktop. performance aside, the platforms are absolutely nothing alike
08:24agrafchadmed: But that's the whole point - the above uses ARM SR images and mangles them into an Apple compatible environment
08:25agrafchadmed: 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"
08:25agrafAnd that's absolutely a useful goal to have, I just don't know if it should be step 1 ;)
08:26chadmedwell yeah thats my point of contention i think. the SR image should boot to a live medium a la PC, and users configure and install more advanced options via e.g. Anaconda as they would on any amd64 desktop
08:26chadmedrather than have the image directly dumped into their target partition
08:27marcanagraf: one issue is that I want to be able to stream images directly to the target disk, but I already built myself a seekable/cached fd view over HTTP for the ipsw in the installer... so that will work nicely for that use case too
08:27agrafchadmed: 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
08:27chadmedbut again, thats very endgame-y, and personally i think for the kinds of people who are interested in this in the immediate to near term future will be more than happy with "we give you m1n1+u-boot+an empty partition, configuring the rootfs is an exercise for the reader"
08:28marcanagraf: also we don't intend to own the kernel at all; if you want to be on our installer list you'd better be building kernels from usable trees for those images
08:28marcanfor Arch I will take care of that myself, as the reference distro
08:28agrafmarcan: perfect :)
08:29chadmedagraf: why? we have already established that u-boot can boot live media once it's been handed off to by iboot, so with that functionality in mind eventually the install process (beyond the intial setup of m1n1+uboot) will look virtually identical to how theyd set up an amd64 workstation right now
08:29agrafmarcan: 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
08:29marcanyes, we won't provide grub either
08:29agrafchadmed: because you need all the macOS system partition setup magic, no? How would you deal with that?
08:29marcanthat's *why* we're using the whole u-boot/efi thing
08:30chadmedmarcan's already written a script that deals with that, thats what i mean when i say "asahi installer"
08:30chadmedit sets up the boot policy and m1n1 right now, but of course can be easily rejigged to install a m1n1+uboot image, its a shell script after all
08:31marcanpython script
08:38agrafThat'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.
08:39agrafIt definitely isn't the "easy" route for not-heavily-sophisticated users though. That's more likely to be the SBC image.
08:40chadmedin terms of presenting a skeuomorph of a PC, its probably best though. its a happy medium that has worked for 20+ years in terms of ease-of-use vs flexibility
08:43chadmedi consider myself a pretty advanced computer user, and despite this the first time i was confronted with installing an OS on to an ARM system in the method you describe, i found myself confused and incensed that it did not like a PC, despite it being ostensibly "easier"
08:53aleasto has joined #asahi-dev
09:01psykose has quit [Read error: No route to host]
09:01psykose has joined #asahi-dev
09:13rkt is now known as Guest4991
09:13rkt_ has joined #asahi-dev
09:13rkt_ is now known as rkt
09:15Guest4991 has quit [Ping timeout: 480 seconds]
09:40kettenisagraf: we did teach the OpenBSD installer to preserve the essential Apple partitions
09:40j_eysven: what's the difference between the 'select' and 'properties' in apple,dwc3.yaml?
09:40j_eysven: select has t8xx only, not sure if thats intentional
09:41kettenisbut now that's done, the only thing that's needed is to have m1n1 with a u-boot payload and some free space
09:42kettenisand the installation experience is really not different from an x86 machine with UEFI
09:43kettenisdual booting macOS will work just fine
09:44svenj_ey: select makes sure that apple,dwc3 gets precedence over snps.dwc3.yaml as soon as the compatible contains t8103-... (which the t6k one will contain as well)
09:45j_eysven: got it
09:48kettenissven: I don't think the t6000 dwc3 should have t8103 as a compatible
09:48svenkettenis: that's what apple's device tree does and according to marcan t6k has the same reset quirk as t8103
09:50svenso t6000 would be "t6000-dwc3", "t8103-dwc", "snps,dwc3" then
09:51kettenisI guess you'd still be able to quirk t6000 and t8103 separately in that case
09:51kettenisso in that sense it is ok
09:52sveni'm also fine with "t6000-dwc3", "snps,dwc3" but then we'd need to already quirk both t8103 and t6000 with the same thing
09:53kettenisso there are two cases to consider:
09:54kettenisa) running a new kernel with an older DT
09:54kettenisb) running an older kernel with a newer DT
09:55kettenissuppose we find a new quirk that only applies to t8103 but breaks the t6000
09:56kettenisif we list both t6000 and t8103 as compatible for the t6000 we can support the quirk easily and only apply it to t6000
09:57kettenisbut if we then remove the t8103 compatible from the DT for the t6000, an older kernel would no longer work properly with the new DT
09:58kettenisso if we already know that t6000 needs the same reset quirk as the t8103 it is probably best to make that explicit
09:59kettenisor maybe we should have an apple,dwc3 compatible after all
09:59kettenis(I know I argued against it earlier)
10:20sventrue, we could enable the reset quirk for "apple,dwc3" then. we'd need a "apple,dwc3-v2" or something like that though if they ever fix that behavior in the future
11:01kettenison the other hand, the machine is usable with only the snps,dwc3 matching, so maybe that is good enough
11:02kettenisscenario b) is really there such that people can upgrade their kernel after updating m1n1 and the device tree
11:40agrafkettenis: 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) :)
11:58amwsven: Dumb question: I'm trying to get USB keyboard with your usb-reset/v2 + https://paste.debian.net/1218312 patch but I get the USB probe failing with missing memory resource?
12:01svenThe nodes are wrong. You want the same usb nodes as before but a different compatible. You also don’t need that branch unless you also setup i2c, usb pd and the connection to dwc3
12:03amwok - so need lots of other DT nodes and stuff to go before usable tree in the kernel
12:03sventhis only makes hot plugging works fwiw
12:03amwok - saw usb and got excited :-(
12:04svenusb already works
12:04amwnot if you don't have it in the dts ...?
12:04svenyou just need to add dwc3 nodes to the DT. i'll eventually submit those upstream as well but we'll need to get the apple,dwc3 binding figured out first
12:05amwCan we at least put a dwc3 node in the m1n1 dts area?
12:06amwAnother question is there a seperate dts for macbook vs mini ?
12:06j_eyeventually
12:08svenm1n1/dts imho should only track whatever is upstream
12:09amwSo where does the experimental / proposed stuff go if not in m1n1 for debugging/testing?
12:11j_eyrandom branches :p
12:13chadmedmu-one is probably the best staging ground we have right now for staging experimental stuff, right?
12:13chadmedits the most "complete" rn
12:15amwchadmed: That does seem to have a *very* complete DT - thanks
12:40amwchadmed: It still doesn't see my USB keyboard or USB drive :-(
12:41chadmedusb seems to be working for most other folks
12:48amwMy m1n1 booting line is: python3.9 proxyclient/tools/linux.py -b 'earlycon console=tty0 console=tty0 debug net.ifnames=0 rw root=/dev/sda1 rootdelay=5 rootfstype=ext4' Image-mu-one.gz t8103-j274-mu-one.dtb
12:51amwchadmed: I'm sure it's something dumb - but it's time for sleep so I'll look tomorrow. But anything obvious jumps to mind just tap it in
12:51amwI'll look at it tomorrow - thanks - night.
12:53chadmedim pretty sure nvme isnt meant to work yet?
12:53svennvme works with my downstream patches. they just need to be cleaned up before sent upstream
12:56chadmedah yeah i see. its just not finding sda1 and dumping the list of nvme partitions. i assume its a kernel config problem since usb2 should work regardless
13:26kettenis has quit [Quit: Lost terminal]
13:34yuyichao has quit [Ping timeout: 480 seconds]
13:51X-Scale` has joined #asahi-dev
13:53yuyichao has joined #asahi-dev
13:57X-Scale has quit [Ping timeout: 480 seconds]
13:57[X-Scale] has joined #asahi-dev
13:58kettenis has joined #asahi-dev
13:59kettenisagraf: yes, the lack of runtime access to UEFI variables does stand in the way of supporting multi-booting non-macOS OSes
14:02X-Scale` has quit [Ping timeout: 480 seconds]
14:08kettenismaybe we can do something clever there for these systems
14:09kettenisit should be possible to isolate nvram access from the OS in a fairly reliable way on this hardware
14:09kettenisnot sure if there is space in nvram for us to scribble in though
15:15yuyichao_ has joined #asahi-dev
15:16richbridger has quit [Remote host closed the connection]
15:16richbridger has joined #asahi-dev
15:18yuyichao has quit [Ping timeout: 480 seconds]
15:34dsrt^ has quit [Ping timeout: 480 seconds]
16:36agrafkettenis: 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
17:06[X-Scale] is now known as X-Scale
17:36sveni don't think SEP has any key-value store. it might be possible to abuse something else but i haven't seen anything so far
17:36sven(you'll also need APFS support to fully boot SEPOS but i guess that can be worked around)
17:37svenand at least I want to store my ssh/gpg keys in there but i think my use case doesn't align with what most people want to use it for ;)
18:13___nick___ has joined #asahi-dev
18:13___nick___ has quit []
18:15___nick___ has joined #asahi-dev
19:02timokrgr6 has joined #asahi-dev
19:08timokrgr has quit [Ping timeout: 480 seconds]
19:08timokrgr6 is now known as timokrgr
19:23jix_ has joined #asahi-dev
19:24jix has quit [Ping timeout: 480 seconds]
19:50dsrt^ has joined #asahi-dev
20:23aleasto has quit [Remote host closed the connection]
20:34yuyichao has joined #asahi-dev
20:38yuyichao_ has quit [Ping timeout: 480 seconds]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:24dottedmag has quit [Quit: QUIT]
21:26yrlf2 has joined #asahi-dev
21:27jannau_ has joined #asahi-dev
21:28yrlf has quit [Remote host closed the connection]
21:28jannau has quit [Remote host closed the connection]
21:28grange_c has quit [reticulum.oftc.net liquid.oftc.net]
21:28ponkey364[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28astrorion26[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28long[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28os has quit [reticulum.oftc.net liquid.oftc.net]
21:28roxfan has quit [reticulum.oftc.net liquid.oftc.net]
21:28d4ve has quit [reticulum.oftc.net liquid.oftc.net]
21:28arekm has quit [reticulum.oftc.net liquid.oftc.net]
21:28Synth[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28Fanfwe has quit [reticulum.oftc.net liquid.oftc.net]
21:28suricato has quit [reticulum.oftc.net liquid.oftc.net]
21:28crabbedhaloablut has quit [reticulum.oftc.net liquid.oftc.net]
21:28mariogrip[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28YichaoYu[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28wollymilkcap[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28TellowKrinkle[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28Guest3421 has quit [reticulum.oftc.net liquid.oftc.net]
21:28SocioProphet[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28simjnd[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28samfromspace[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28sajattack[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28nilsi[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28kdrag0n[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28lockna has quit [reticulum.oftc.net liquid.oftc.net]
21:28joerosenberg[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28fridtjof[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28CristianMgheruan-Stanciu[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28brentr123[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28AnushervonTabarov[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28davay[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28bastilian[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28AkihikoOdaki[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28xerpi[m] has quit [reticulum.oftc.net liquid.oftc.net]
21:28emilazy has quit [reticulum.oftc.net liquid.oftc.net]
21:28alicela1n has quit [reticulum.oftc.net liquid.oftc.net]
21:28psydroid[m]1 has quit [reticulum.oftc.net liquid.oftc.net]
21:28akemin_dayo has quit [reticulum.oftc.net liquid.oftc.net]
21:28mwalle has quit [reticulum.oftc.net liquid.oftc.net]
21:28Stary has quit [reticulum.oftc.net liquid.oftc.net]
21:28Esmil has quit [reticulum.oftc.net liquid.oftc.net]
21:28jato has quit [reticulum.oftc.net liquid.oftc.net]
21:29dottedmag has joined #asahi-dev
21:30grange_c has joined #asahi-dev
21:30astrorion26[m] has joined #asahi-dev
21:30alicela1n has joined #asahi-dev
21:30ponkey364[m] has joined #asahi-dev
21:30mwalle has joined #asahi-dev
21:30long[m] has joined #asahi-dev
21:30roxfan has joined #asahi-dev
21:30d4ve has joined #asahi-dev
21:30os has joined #asahi-dev
21:30arekm has joined #asahi-dev
21:30Fanfwe has joined #asahi-dev
21:30simjnd[m] has joined #asahi-dev
21:30Synth[m] has joined #asahi-dev
21:30samfromspace[m] has joined #asahi-dev
21:30sajattack[m] has joined #asahi-dev
21:30nilsi[m] has joined #asahi-dev
21:30lockna has joined #asahi-dev
21:30kdrag0n[m] has joined #asahi-dev
21:30joerosenberg[m] has joined #asahi-dev
21:30fridtjof[m] has joined #asahi-dev
21:30emilazy has joined #asahi-dev
21:30CristianMgheruan-Stanciu[m] has joined #asahi-dev
21:30AnushervonTabarov[m] has joined #asahi-dev
21:30brentr123[m] has joined #asahi-dev
21:30bastilian[m] has joined #asahi-dev
21:30AkihikoOdaki[m] has joined #asahi-dev
21:30davay[m] has joined #asahi-dev
21:30wollymilkcap[m] has joined #asahi-dev
21:30xerpi[m] has joined #asahi-dev
21:30YichaoYu[m] has joined #asahi-dev
21:30crabbedhaloablut has joined #asahi-dev
21:30suricato has joined #asahi-dev
21:30TellowKrinkle[m] has joined #asahi-dev
21:30SocioProphet[m] has joined #asahi-dev
21:30akemin_dayo has joined #asahi-dev
21:30Stary has joined #asahi-dev
21:30mariogrip[m] has joined #asahi-dev
21:30Guest3421 has joined #asahi-dev
21:30Esmil has joined #asahi-dev
21:30jato has joined #asahi-dev
21:40psydroid[m]1 has joined #asahi-dev
22:16timokrgr has quit [Quit: Ping timeout (120 seconds)]
22:16timokrgr has joined #asahi-dev
22:30yuyichao has quit [Ping timeout: 480 seconds]
…