2022-03-26
00:23user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
00:46kameks has joined #asahi-dev
01:03balrog has quit [Quit: Bye]
01:09balrog has joined #asahi-dev
01:19chadmed has joined #asahi-dev
01:25user982492 has joined #asahi-dev
01:33suricato has quit [Server closed connection]
01:33suricato has joined #asahi-dev
01:42yuyichao_ has joined #asahi-dev
01:44m2lsttn has joined #asahi-dev
01:48amarioguy has joined #asahi-dev
01:51yuyichao_ has quit [Remote host closed the connection]
01:52yuyichao has joined #asahi-dev
01:55m2lsttn has quit [Quit: Leaving...]
01:59jakebot has quit [Quit: The Lounge - https://thelounge.chat]
02:01jakebot has joined #asahi-dev
02:20Emantor has quit [Quit: ZNC - http://znc.in]
02:20Emantor has joined #asahi-dev
02:20kameks has quit [Ping timeout: 480 seconds]
02:34amarioguy has quit [Ping timeout: 480 seconds]
02:44kameks has joined #asahi-dev
02:46amarioguy has joined #asahi-dev
03:14dyronl^ has joined #asahi-dev
03:21phiologe has joined #asahi-dev
03:23asocialblade has joined #asahi-dev
03:24PhilippvK has quit [Ping timeout: 480 seconds]
03:26amarioguy has quit [Ping timeout: 480 seconds]
03:32asocialblade has quit []
03:32asocialblade has joined #asahi-dev
03:33asocialblade has quit []
03:33asocialblade has joined #asahi-dev
03:34user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:37asocialblade has quit []
03:38asocialblade has joined #asahi-dev
03:38kov has quit [Quit: Coyote finally caught me]
03:38asocialblade has quit []
03:38asocialblade has joined #asahi-dev
03:38kov has joined #asahi-dev
03:43doggkruse has joined #asahi-dev
03:58user982492 has joined #asahi-dev
04:51slimjimsoftware[m] has joined #asahi-dev
05:12doggkruse has quit [Read error: Connection reset by peer]
05:24robinp has quit [Ping timeout: 480 seconds]
06:20marcanmaz: t8103, t6000, t6001/2 cores are all slightly different revisions, that's why they have different MIDRs
06:23marcanI think apple forks their cores per SoC, then backports fixes and follows a different revision number lineage for each tape-out
06:24marcanif you look at the chicken bits, you can see they can mostly be sorted chronologically by looking at what got fixed/added, and you end up with interleaved soc/revision pairs
06:25marcanso for example, HID4_ENABLE_LFSR_STALL_LOAD_PIPE_2_ISSUE got added in t6000 rev >= 0x10, but base t6001 has it already
06:27marcanthat tells me they taped out t6000 before finding the first one, then found it before taping out t6001, then found the second one, or something like that
07:10slimjimsoftware[m] is now known as unsui[m]
07:10gladiac has quit [Remote host closed the connection]
07:10gladiac has joined #asahi-dev
07:13gladiac is now known as Guest376
07:13Guest376 has quit [Read error: No route to host]
07:13gladiac has joined #asahi-dev
07:13jannaumarcan: do you still have your m1n1 memory benchmarks? it looks like you never pushed them
07:14Dcow[m]1total = self.selected_part.container["CapacityCeiling"]... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/euwpyGosxuWvTzglSgtYvkie)
07:14Dcow[m]1Current size: 900.00 GB... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/fxWmOszlLeRQIaYGUwMNoHnv)
07:16Glanzmannchadmed: There are grounded cables available, mps had the same issue: https://www.apple.com/de/shop/product/MK122D/A/power-adapter-netzteil-verl%C3%A4ngerungskabel
07:16jannauI started investigating numa annotations would make sense the t6002. at least for sequential reads it doesn't seem to be the case
07:19chadmedso annoying they dont just add an earth pin on the header they ship with it. the metal grounding lug is there on the brick...
07:22marcanif you really start digging into the lower address bits you could probably map out the interleaving, but that wouldn't be useful for software anyway
07:31chadmedmps: lmao awesome, australian plugs arent really conducive to that though. our plugs always occlude the entire socket
07:35nicolas17from Retr0id: https://cdn.discordapp.com/attachments/779844089196576809/908436702484365372/PXL_20211111_192046702.jpg https://cdn.discordapp.com/attachments/779844089196576809/908436716162007040/PXL_20211111_192117778.jpg
07:54nicolas17 has quit [Ping timeout: 480 seconds]
07:58gruetzkopf has quit [Server closed connection]
07:58gruetzkopf has joined #asahi-dev
08:01herbas has joined #asahi-dev
08:05gtk2 has quit [Server closed connection]
08:05gtk2 has joined #asahi-dev
08:05the_lanetly_052 has joined #asahi-dev
08:09herbas has quit [Quit: herbas]
08:22the_lanetly_052 has quit [Ping timeout: 480 seconds]
08:23lockejan[m] has quit [Server closed connection]
08:23lockejan[m] has joined #asahi-dev
08:38jannaunice, I can now boot into the unmodified asahi desktop install. tethered m1n1+u-boot boot, i.e. I chainload m1n1 + mac studio dtb + u-boot, grub, kernel, initrd and rootfs on the nvme are provided by the installer
08:39kameks has quit [Ping timeout: 480 seconds]
09:05chadmedyeah i finally decided to bite the bullet and spec one out, then i noticed that delivery times here have blown out to 2 months...
09:17V has quit [Server closed connection]
09:18V has joined #asahi-dev
09:18minkuu[m] has quit [Server closed connection]
09:18minkuu[m] has joined #asahi-dev
09:20user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:23int80 has quit [Server closed connection]
09:23int80 has joined #asahi-dev
09:32gabuscus_ has quit [Server closed connection]
09:32gabuscus has joined #asahi-dev
09:32m6wiq has joined #asahi-dev
09:36alcazar has joined #asahi-dev
09:42Mary has quit [Server closed connection]
09:42Mary has joined #asahi-dev
09:44jannauhdmi on the mac studio can handle disconnect/reconnect, even with with a different display without dcp
09:56leonardeyer[m] has quit [Server closed connection]
09:56leonardeyer[m] has joined #asahi-dev
09:58lkvrsfld[m] has quit [Server closed connection]
09:58lkvrsfld[m] has joined #asahi-dev
10:07FarukAydn[m] has quit [Server closed connection]
10:07FarukAydn[m] has joined #asahi-dev
10:11MikaB[m] has quit [Server closed connection]
10:11MikaB[m] has joined #asahi-dev
10:13chengsun has quit [Server closed connection]
10:13chengsun has joined #asahi-dev
10:14di1[m] has quit [Server closed connection]
10:14di1[m] has joined #asahi-dev
10:18nico_32 has quit [Server closed connection]
10:18nico_32 has joined #asahi-dev
10:20zyroklarryfish[m] has quit [Server closed connection]
10:20zyroklarryfish[m] has joined #asahi-dev
10:21alexandruchi[m] has quit [Server closed connection]
10:21alexandruchi[m] has joined #asahi-dev
10:25Thib[m]12 has quit [Server closed connection]
10:25Thib[m]12 has joined #asahi-dev
10:27timokrgr has quit [Server closed connection]
10:27timokrgr has joined #asahi-dev
10:31Retr0idchadmed, as of the switch to usb-c, grounding the grounding lug on the charger still does not ground the macbook chassis, because the usb-c receptacle is made of plastic
10:40milek7I don't think you need grounded chassis, just need to ground EMI filter in the power supply
10:45subject38[m] has quit [Server closed connection]
10:45subject38[m] has joined #asahi-dev
10:47ChaosPrincess has quit [Quit: WeeChat 3.4]
10:49ChaosPrincess has joined #asahi-dev
10:53the_real_briel[m] has quit [Server closed connection]
10:53the_real_briel[m] has joined #asahi-dev
10:56chadmedyeah the mains voltage just needs to be stopped from being capacitively coupled into the low voltage side of the brick so grounding the mains side should be adequate
11:03nametable[m] has quit [Server closed connection]
11:03nametable[m] has joined #asahi-dev
11:05robinp has joined #asahi-dev
11:07robinpdoes everyone else get the netfilter filename conflicts when cloning linux onto a mac ? how do you fix it ?
11:09j`eyfrom a quick google looks like you have to do it on a volume basis, not per folder: use std::borrow::Cow;
11:19robinpj`ey: thanks for the linux - I guess I will just do that for now rather than stir up trouble...
11:20* Dcow[m]1posted a file: (388KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/HVhJMpkgzLJUzBFaLvUSHSWX/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202022-03-26%20%D0%B2%2016.49.41.png >
11:20robinpj`ey: nah - was just browsing source code and was just annoyed with there being 'changed files' in the git status that you can't get rid of
11:44krabador has joined #asahi-dev
12:04Foxboron has joined #asahi-dev
12:07mnc7[m] has quit [Server closed connection]
12:07mnc7[m] has joined #asahi-dev
12:12krabador has quit [Remote host closed the connection]
12:12badlydrawnface[m] has quit [Server closed connection]
12:12badlydrawnface[m] has joined #asahi-dev
12:28psykose has quit [Server closed connection]
12:28psykose has joined #asahi-dev
12:29just_curious[m] has quit [Server closed connection]
12:29borhanborhan[m] has joined #asahi-dev
12:29just_curious[m] has joined #asahi-dev
12:35Glanzmann has quit [Quit: leaving]
12:51the_lanetly_052 has joined #asahi-dev
13:02julip[m] has joined #asahi-dev
13:06herbas_ has joined #asahi-dev
13:11herbas_ has quit [Quit: herbas_]
13:19chadmed has quit [Remote host closed the connection]
13:27kita99 has joined #asahi-dev
13:37Fayn has joined #asahi-dev
13:45dyronl^ has quit [Remote host closed the connection]
14:08m6wiq has quit []
14:27Eighth_Doctorhey all, I'm starting work on bringing up Apple Silicon support in Fedora Linux as part of the Fedora Asahi project (https://pagure.io/fedora-asahi/project), and I was wondering about the feature matrix items that have 5.17 in parenthesis (https://github.com/AsahiLinux/docs/wiki/Feature-Support)
14:27Eighth_Doctorare those items present in the just-released 5.17?
14:28j`eyEighth_Doctor: btw glanzmann made a page here too https://github.com/AsahiLinux/docs/wiki/Fedora
14:28j`eyEighth_Doctor: I suggest you use the asahi branch for now, 5.17 doesnt have enough to be usuable
14:35Eighth_Doctorwhat is the asahi branch based on right now?
14:35Eighth_Doctorit seems like 5.17-rc7?
14:45Eighth_Doctorwe've been packaging up the other parts
14:46Eighth_Doctorm1n1, asahi-scripts, etc.
14:46Eighth_DoctorI just need to pull in the asahi work into the fedora kernel tree :/
14:46Eighth_Doctorunfortunately the main kernel maintainers merged the packaging files into the source tree so it's difficult to use another source tree directly for packaging a kernel
14:51Eighth_Doctoryeah, I'm extremely unhappy about it
14:51Eighth_DoctorI was unhappy when we made that change, and now I'm even more unhappy
14:52Eighth_Doctormoving to the RHEL workflow for the Fedora kernel has made experimentation much harder for folks like me :(
14:52Eighth_Doctorthat's the main tree
14:54Eighth_Doctorthe upside, as it were, is that it makes it much easier for us to continuously test the kernel sources nightly with the RHEL and Fedora test harness
14:54Eighth_Doctorand we do that, but... sigh
14:56Eighth_DoctorI'm not sure it was worth it after all, but...
14:56Eighth_Doctorit is nice seeing nightly snapshots of the kernel being tested
14:59Eighth_Doctorindeed
15:06hir0pro has joined #asahi-dev
15:09amarioguy has joined #asahi-dev
15:09hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:41matde[m] has joined #asahi-dev
15:46the_lanetly_052__ has joined #asahi-dev
16:03amarioguy has quit [Ping timeout: 480 seconds]
16:03kita99 has quit [Ping timeout: 480 seconds]
16:05m6wiq has joined #asahi-dev
16:09marcanEighth_Doctor: the udev trigger thing is to make udev trigger the nvme driver, *then* the firmware pull script runs, *then* normal udev trigger runs and loads the broadcom wifi driver
16:09jeffmiw has joined #asahi-dev
16:10marcanwithout that you either end up with firmware not working on first boot / being out of step, or the firmware pull script blocking on nvme that won't come until it's done
16:10marcanif you build the nvme driver and all its dependencies into the kernel you don't need it, of course
16:11Eighth_DoctorI see
16:17jeffmiw has left #asahi-dev [Leaving...]
16:18jeffmiw has joined #asahi-dev
16:19jeffmiwsven: what will be the best way to help upstreaming pending changes ? running checkpatch on asahi/bits/* branches ? what else ?
16:19Eighth_Doctormarcan: torvalds' tree
16:20Eighth_Doctorfedora-* branches follow stable tree though
16:20marcanok, then that's a good reason for us to try to avoid linux-next bases in the future, at least for our main branch
16:20Eighth_Doctore.g. fedora-5.17 follows linux-5.17.y
16:20marcanI have some merge scripts now anyway, so it would be fairly easy to offer/test both anyway
16:20sventhe main problem is that writing new drivers and/or reversing new hardware is usually more fun :D
16:20marcanthe main reason for tracking linux-next is so that we can pull in upstreamed changes ASAP, without waiting for the next merge window
16:21Eighth_DoctorI see
16:21Eighth_DoctorFedora just rebased its kernel to 5.17.0 this week, so things are very in sync right now
16:22Eighth_Doctorthe os-build branch gets reset every time a kernel rebase happens, to make sure we minimize our patch delta
16:23Eighth_Doctor and that directly feeds into https://koji.fedoraproject.org/koji/packageinfo?packageID=8
16:23marcanfor us asahi is just an auto-merge of our bits/ branches, which are frequently rebased on top of whatever linux-next I'm going by
16:23jeffmiwok, I'm willing to help upstreaming pending bits, so if someone sees something I can do to help in this area let me know ..
16:23Eighth_Doctormarcan: that makes sense, after all you're actively working next-next-next code :D
16:23marcan(which is why a couple bits/ branches base on each other, it's always MAINTAINERS changes, hint hint sven)
16:23Eighth_Doctorit's just a little fugly for me to work through, sorry :(
16:24marcanbut basically it's not actually too bad for us to pick a different base point, or merge linux-next after or split up bits/ in a way to make that easier
16:24Eighth_Doctorthat would be hugely appreciated
16:25Eighth_Doctorfwiw, the folks working on fedora-asahi are available via matrix on #asahi:fedora.im (https://matrix.to/#/#asahi:fedora.im)
16:25marcanhow about when something gets upstreamed, I pull that upstream tip into a bits-cur/ or something, or rebase it if it has too much unrelated history
16:25Eighth_Doctorthat would be very useful
16:25marcanand then I can have all the bits/ branches base off of an RC or whatever in general, and our main -next merge would happen between next and only the bits/ branches
16:25Eighth_Doctorhow difficult would it be for you to maintain a set also on the latest stable tree?
16:26Eighth_Doctornormal
16:26Eighth_Doctorfuck longterm
16:26Eighth_DoctorFedora kernels are aggressively rebased to the latest stable versions as they become available
16:26* Eighth_Doctorhas terrible experiences with the longterm kernels
16:27marcanI can probably just say the base is stable tbh, though I'll only rebase on top of X.Y versions, I won't be maintaining minor merges
16:27Eighth_Doctorrebases are fine
16:27j`eywell stable is 5.16, so that might require backporting some things that are not in the current asahi, but are in 5.17
16:27Eighth_Doctorstable is 5.17 now
16:27marcanI mean I won't do X.Y.Z releases but if you want those hopefully those merges won't be painful
16:27Eighth_Doctorno, I think that's fine
16:27Eighth_Doctorusually cherry-picks after the fact are easy
16:28Eighth_Doctorand I need to do cherry-picks anyway because of the discordant history
16:28marcanI'll give it a shot next time I rebase and see how it goes, it's getting more reasonable now that most patches to existing things are in
16:28Eighth_Doctorso if you have one based on v5.17 tag then I can work with it
16:28marcanI should send another wifi series out, that's probably the only one likely to cause conflicts longer term and it's mostly reviewed already anyway
16:28Eighth_Doctormy hope is to have this fully integrated into Fedora sometime between now and Fedora 39
16:29Eighth_Doctorthat's October of next year
16:29Eighth_DoctorFedora 37 is October of this year
16:29Eighth_Doctora Fedora Asahi Remix is probably going to become a thing sometime in the next few months
16:29marcanI hope to be fully back in kernel bikeshedding mode in a couple weeks at most, do a good round of that
16:29Eighth_Doctorjust need to get a working kernel
16:30Eighth_Doctorand a maintenance workflow in place for it
16:30Eighth_Doctorhehe yeah
16:30Eighth_DoctorI'm trying to hold to my promise to you when you started that I want to have Fedora be the first distribution after yours to have ARM Mac support
16:31Eighth_Doctor(also, I lead Fedora KDE :) )
16:31Eighth_Doctorthanks, I appreciate it
16:31marcanyou probably saw we have a couple forks of random things, like the xkeyboard stuff; all that is really just intended as sandboxes for improving mac support in $random_packages
16:32marcanso you don't have to care about that other than feeling free to backport patches if you want them early
16:32Eighth_Doctoras a Mac user for more than a decade, I've always appreciated the Mac hardware
16:32Eighth_Doctorand 5.19 will be backported to all currently supported Fedora releases at the time of its release
16:33Eighth_Doctorthen I just have to have a go at getting Anaconda to play nice on a Mac :)
16:33Eighth_Doctorpretty clever
16:33Eighth_DoctorI'm actually the calamares maintainer in Fedora, so I might steal a bit of it
16:33Eighth_Doctorfor the remix
16:34marcanI did that like the week before release, so at some point I gave up on sanity and just needed to hack things up to make it work
16:34sveni'm writing replies to the nvme review comments from my couch right now and yet you people are already distracting me again :-P
16:34Eighth_Doctora friend of mine is loaning me an M1 macbook pro since I can't afford a new computer at the moment, so that'll let me get my feet wet on this
16:35Eighth_DoctorI currently have a very tetchy 2014 MacBook Pro
16:35marcanthe good news is it won't really break anything if it moves, since it only really matters at install time
16:35doggkruse has joined #asahi-dev
16:37Eighth_Doctoryeah, well I wasn't going to try to beat marcan
16:37Eighth_Doctoryes, but you're the first to make a distributable thing
16:38Eighth_DoctorI want to be next after that :D
16:38Eighth_Doctorare the uboot things upstreamed yet?
16:38marcanthen again corellium ran ubuntu before anyone here but that was also throwaway code so shrug
16:40marcanI mean "hi ma I can run $distro" doesn't really mean much, you can pick whatever rootfs you want once you have a kernel with framebuffer and IRQs and maybe USB
16:40Eighth_Doctorand can someone else do it with distro support
16:40Eighth_Doctormy goal is to have it actually integrated into Fedora itself reasonably quickly
16:41Eighth_Doctorthen I get to have "fun" times trying to see if we can get this into CentOS/RHEL 10
16:41marcanas we've quipped before, Asahi's goal is to not exist as a distro (even if we never quite get there) :)
16:41Eighth_Doctorand I hope that Fedora's work will provide a blueprint for other distros that often look to us for how to do this to enable it for their own distros
16:42Eighth_Doctormarcan: finally broke them of that. 4k on RHEL 9
16:42Eighth_DoctorI was personally very pleased to see that change
16:42marcanthat's another one to poke the stick at soon, if only because it will trigger more discussion
16:43svenif we make swiotlb work with > PAGE_SIZE alignments we can just re-submit that 4k thing. I have a branch somewhere that addresses the other review comments fwiw
16:43hir0pro has joined #asahi-dev
16:44svenbut that swiotlb thing is a bit tricky and i've had a chance to grab some pencil+paper to work out how to make that happen together with this min_dma_align_mask or however it was called
16:44marcan(I'm not pulling it into asahi because I want people to feel the pain for a while, so packages get fixed first)
16:46Eighth_Doctorthe btrfs stuff is all sorted out now, thankfully
16:46Eighth_Doctorwhich is what really matters in the Fedora context
16:47Eighth_Doctorwe originally got that work done for POWER (which uses 64k pages), but it's even more helpful with ARM now
16:47Eighth_Doctorbecause now btrfs should behave properly on 16k and 4k pages
16:50Eighth_Doctorthere are now two different ways to do it: either with btrfs-fuse or with kernel 5.16+ btrfs
16:51Eighth_Doctorif it doesn't work with kernel-btrfs, please send an email to linux-btrfs@ about it to let them know
16:52Eighth_Doctor(btrfs-fuse is a read-only btrfs implementation designed to assist in recovery and similar scenarios)
16:52j`eyI dont use it, but I was thinking some people might like to reboot into different page_size kernels
16:53Denver has joined #asahi-dev
16:55Eighth_Doctorbtrfs should work fine in that case
16:55the_lanetly_052__ has quit [Remote host closed the connection]
16:55the_lanetly_052 has quit [Remote host closed the connection]
16:55Eighth_Doctorif the filesystem is created with 4k size (which it should by default now), then it'll work everywhere
16:55the_lanetly_052__ has joined #asahi-dev
16:55the_lanetly_052 has joined #asahi-dev
16:59nicolas17 has joined #asahi-dev
17:02andre4[m] has joined #asahi-dev
17:17asocialblade has quit []
17:18asocialblade has joined #asahi-dev
17:18andre4[m] is now known as quas4r[m]
17:20hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:35m6wiq has quit []
17:42hir0pro has joined #asahi-dev
17:48amarioguy has joined #asahi-dev
17:56amarioguy has quit [Ping timeout: 480 seconds]
18:10clee has joined #asahi-dev
18:27jeffmiw has quit [Ping timeout: 480 seconds]
18:36jeffmiw has joined #asahi-dev
19:07amarioguy has joined #asahi-dev
19:08hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:15user982492 has joined #asahi-dev
19:20___nick___ has joined #asahi-dev
19:20___nick___ has quit []
19:22___nick___ has joined #asahi-dev
19:31boardwalk has quit [Quit: The Lounge - https://thelounge.chat]
19:35hir0pro has joined #asahi-dev
19:49BenFE has joined #asahi-dev
19:51amarioguy has quit [Remote host closed the connection]
19:51amarioguy has joined #asahi-dev
20:02Denver has quit [Quit: Textual IRC Client: www.textualapp.com]
20:07Revy is now known as RevHelix
20:13BenFE has quit [Ping timeout: 480 seconds]
20:25hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:28hir0pro has joined #asahi-dev
20:34user982492 has quit [Ping timeout: 480 seconds]
20:35hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:41amarioguy has quit [Ping timeout: 480 seconds]
20:42user982492 has joined #asahi-dev
20:50hir0pro has joined #asahi-dev
20:58hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:41user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:52the_lanetly_052___ has joined #asahi-dev
21:53hir0pro has joined #asahi-dev
21:54Eighth_Doctoraleasto: no, I don't request IRC rooms by default for new rooms
21:54Eighth_Doctoralso, this is technically not an "official" room on fp.o namespace, it's on fedora.im namespace
21:54Eighth_DoctorI don't intend to make it a SIG or whatever, it's a short-term thing until it's all merged back into Fedora
21:58the_lanetly_052__ has quit [Ping timeout: 480 seconds]
21:59the_lanetly_052 has quit [Ping timeout: 480 seconds]
21:59the_lanetly_052 has joined #asahi-dev
22:45user982492 has joined #asahi-dev
23:16hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:22Fayn has quit []
23:41systwi has joined #asahi-dev