#
…

2026-01-20

00:18pb17 has quit [Ping timeout: 480 seconds]
00:30hdbngr has joined #asahi-dev
00:34fl0_idjannau 16 core. I thought it was referred to as t6031 as well... but yeah I'll try to check that
00:39hdbngr has quit [Ping timeout: 480 seconds]
00:52hdbngr has joined #asahi-dev
00:56mixi has quit [Ping timeout: 480 seconds]
00:57pb17 has joined #asahi-dev
01:06mixi has joined #asahi-dev
01:08hdbngr has quit [Ping timeout: 480 seconds]
01:11hdbngr has joined #asahi-dev
01:26hdbngr has quit [Ping timeout: 480 seconds]
01:52hdbngr has joined #asahi-dev
01:57midou has quit [Read error: No route to host]
01:57midou has joined #asahi-dev
02:01hdbngr has quit [Ping timeout: 480 seconds]
02:05midou has quit [Ping timeout: 480 seconds]
02:11pb17 has quit [Ping timeout: 480 seconds]
02:19midou has joined #asahi-dev
02:21pb17 has joined #asahi-dev
02:27k70_ has joined #asahi-dev
02:29k70 has quit [Ping timeout: 480 seconds]
02:29k70_ is now known as k70
02:31midou has quit [Ping timeout: 480 seconds]
03:12hexdump0815 has joined #asahi-dev
03:14hexdump01 has quit [Ping timeout: 480 seconds]
03:14hdbngr has joined #asahi-dev
03:15tobhe_ has joined #asahi-dev
03:22midou has joined #asahi-dev
03:22tobhe has quit [Ping timeout: 480 seconds]
03:23hdbngr has quit [Ping timeout: 480 seconds]
03:26midou has quit [Read error: Connection reset by peer]
03:32midou has joined #asahi-dev
04:04midou has quit [Read error: No route to host]
04:14pb17 has quit [Ping timeout: 480 seconds]
04:21midou has joined #asahi-dev
04:32pb17 has joined #asahi-dev
04:56nora has joined #asahi-dev
04:56hdbngr has joined #asahi-dev
04:58nora_ has quit [Ping timeout: 480 seconds]
05:05hdbngr has quit [Ping timeout: 480 seconds]
05:09hdbngr has joined #asahi-dev
05:15midou has quit [Ping timeout: 480 seconds]
05:18hdbngr has quit [Ping timeout: 480 seconds]
05:22midou has joined #asahi-dev
06:00hdbngr has joined #asahi-dev
06:04chadmed has quit [Quit: Konversation terminated!]
06:04chadmed has joined #asahi-dev
06:04LarstiQsven: how large is your .zsh_history that you still have that? :)
06:07midou has quit [Ping timeout: 480 seconds]
06:08hdbngr has quit [Ping timeout: 480 seconds]
06:15midou has joined #asahi-dev
06:35midou has quit [Ping timeout: 480 seconds]
06:54hdbngr has joined #asahi-dev
06:57jannaufl0_id: the 16 core variant is t6031. the possible issues I saw are with the 14-core variant (t6034)
07:02midou has joined #asahi-dev
07:03hdbngr has quit [Ping timeout: 480 seconds]
07:10midou has quit [Read error: Connection reset by peer]
07:10hdbngr has joined #asahi-dev
07:13midou has joined #asahi-dev
07:19hdbngr has quit [Ping timeout: 480 seconds]
07:21midou has quit [Ping timeout: 480 seconds]
07:38noopwafelmy linux boot on the m3 air is still pretty broken, I had to sabotage smt and chicken bits and the cpuidle driver
07:41noopwafelmy tree is also full of hacks for other things, so this _entirely_ might be my fault, but if anyone has tips to avoid me reinventing the wheel, let me know
07:45midou has joined #asahi-dev
07:47jannaunoopwafel: https://github.com/jannau/m1n1/tree/t8122_bringup + https://github.com/jannau/linux/tree/t8122-j504 does work for the limited hw enabled / present in the device tree
07:48jannaunot sure what smt refers to and I have no idea if the cpuidle driver is used
07:49noopwafelsmt meaning bringing up more than one core.. :)
07:49noopwafeland thanks, I indeed based my dts on yours
07:49jannauthat works, all 8 cores are up and receive irqs
07:50noopwafelthanks! just that information helps a lot :)
07:50jannauI stripped and restructured the dt quite a bit from the last version I pushed
07:52jannaumoved the usb-c ports (not enabled) to the device .dts since j504 should be the only m3 device with i2c USB-PD port controllers
07:52noopwafelyep .. I have no i2c0
07:53nickchanso what does bit[0] of AGTCNTRDIR_EL{1,2,12} do after all
07:54nickchanseems like jannau figured them out
07:55jannaunickchan: I still don't know, I didn't find time yet to look at it
07:55nickchani see you set them in the PR
07:57jannauack, that doesn't mean I know what the bit does. switched the PR to draft
07:59midou has quit [Ping timeout: 480 seconds]
08:01hdbngr has joined #asahi-dev
08:09noopwafeljannau: thanks, that gives me working SMT after just adding a minimal j613 dts which is a big improvement at least :)
08:09hdbngr has quit [Ping timeout: 480 seconds]
08:11hdbngr has joined #asahi-dev
08:12chaos_princesssmt or smp? :P
08:12noopwafeldoes anyone have some idea what might be a reasonable firmware target for m3? I am running with 14.8.3 and wondering if I am going to waste my time porting to that
08:13chaos_princess14.latest seems fine?
08:13noopwafelugh right SMP :D
08:15noopwafelohhh jannau's tree also gets me _working serial from early boot_, amazing
08:16Shizyeah i was wondering, "slunds like you're describing smp" :p
08:16Shiznickchan: do we know what bit[1] does? :P
08:16Shizsurely one of them is related to the architectural timer clock scaling
08:17noopwafelI mean, if useful I could just play "set bits and see what happens"..
08:20hdbngr has quit [Ping timeout: 480 seconds]
08:29ravikant_ has joined #asahi-dev
08:41nickchanShiz: setting bit[1] sets the corresponding EL's timer to 24 MHz subject to VHE caveats
08:41Shizright, okay
08:41nickchanso if i had to guess bit[0] would have something to do with EL0
08:42Shizthe xnu source straight up sets the other bits to 0 too, wonder if that's meaningful
08:42nickchanit must setting some of the bits in the hypervisor
08:42nickchanbut ofc that's redacted
08:43nickchanShiz: i mean we know that there's a whole set of custom timer registers that's 1:1 to the arch ones likely with just with a different freq
08:44nickchanso for the other bits maybe go check their effect on *those* registers instead
08:44nickchaninstead of the arch ones
08:45hdbngr has joined #asahi-dev
08:45nickchanthis is not all need to play with hw to know what the rest of the arch register clones are
08:49midou has joined #asahi-dev
08:51nickchanfor example, agtcntrdir_el1 isn't anywhere in the public sources
08:51nickchanBut if you run strings on a kernel then you can see it
08:55nickchanthough it seems that apple changed from A... to AGT...
08:56nickchanive seen the same register first referenced as acntrdir_el1 but later agtcntrdir_el1 and the encoding is the same
09:10midou has quit [Remote host closed the connection]
09:17nickchannoopwafel: maybe find a register that reads out 0x16e3600 (24 MHz) or 0x3b9aca00 (1 GHz) other than CNTFRQ_EL0
09:17nickchanfrom how things are going in xnu source that register just had to exist....
09:18nickchanand then the set bits experiment can get going
09:19midou has joined #asahi-dev
09:20nickchanespecially the EL0 accessible registers
09:20nickchanfind_regs.py should list all the EL0 accessible regisetrs
09:25Shiznickchan: right, that tracks
09:29kitlithjannau: https://gitlab.freedesktop.org/kitlith/mesa/-/commit/279e9caf1090017001c235ed3ef9a5dc0a2d6f19 -- i'm not entirely sure that filtering out virtio at this stage is strictly necessary. It does show up as platform bus, I'm pretty sure it'll fail anyway when trying to find the connector, as drm_info fails to get any useful information when running under muvm. But I guess there's also little reason not to filter it out at this stage, aside f
09:39nickchanand when doing that might end up finding a CNTPCT_EL0 equivlant too
09:55hdbngr has quit [Ping timeout: 480 seconds]
10:00hdbngr has joined #asahi-dev
10:08hdbngr has quit [Ping timeout: 480 seconds]
10:18hdbngr has joined #asahi-dev
10:27hdbngr has quit [Ping timeout: 480 seconds]
10:27___nick___ has joined #asahi-dev
10:29hdbngr has joined #asahi-dev
10:49hdbngr has quit [Ping timeout: 480 seconds]
10:51___nick___ has quit []
10:53___nick___ has joined #asahi-dev
10:53___nick___ has quit []
10:55___nick___ has joined #asahi-dev
10:57hdbngr has joined #asahi-dev
11:02maor26 has joined #asahi-dev
11:06culman has joined #asahi-dev
11:12chadmed_ has joined #asahi-dev
11:12chadmed has quit [Read error: Connection reset by peer]
11:16culman has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
11:27chadmed_ has quit [Quit: Konversation terminated!]
11:27chadmed_ has joined #asahi-dev
11:33jmax_ has quit [Remote host closed the connection]
11:37culman has joined #asahi-dev
11:38crabbedhaloablut has quit []
11:38crabbedhaloablut has joined #asahi-dev
11:53culman has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
11:53culman has joined #asahi-dev
11:53culman has quit []
12:25ravikant_ has quit [Ping timeout: 480 seconds]
12:30hdbngr has quit [Ping timeout: 480 seconds]
12:37hdbngr has joined #asahi-dev
12:46hdbngr has quit [Ping timeout: 480 seconds]
12:48hdbngr has joined #asahi-dev
12:49culman has joined #asahi-dev
13:05culman has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
13:05ravikant_ has joined #asahi-dev
13:22___nick___ has quit [Ping timeout: 480 seconds]
13:23culman has joined #asahi-dev
13:24___nick___ has joined #asahi-dev
13:26hdbngr has quit [Ping timeout: 480 seconds]
13:34hdbngr has joined #asahi-dev
13:42hdbngr has quit [Ping timeout: 480 seconds]
13:51hdbngr has joined #asahi-dev
14:00hdbngr has quit [Ping timeout: 480 seconds]
14:03hdbngr has joined #asahi-dev
14:07fl0_id___ has joined #asahi-dev
14:23midou has quit [Read error: No route to host]
14:31midou has joined #asahi-dev
14:40hdbngr has quit [Ping timeout: 480 seconds]
14:47hdbngr has joined #asahi-dev
14:53yukamade some progress on t8123:
14:54yukaI was able to map the uart mmio ranges in early boot and use debug_putc after enable_mmu, traced up to aic init
14:54yukalikely fixed one mistake in my device tree's aic node parameter
14:55yuka*parameters
14:56yukanow it hangs at cpuhp_setup_state
14:56yukaOr, well, the debug_putc stops working after that, so I assume it hangs
15:02Dcow[m]yuka: could you please remind what is T8123 is?
15:02culman has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
15:04svenm4, should be t8132 I think
15:06nickchant8120 = a16, t8122 = m3, t8130 = a17, t8132 = m4
15:08fl0_id___yuka, do you have this up somewhere, just in case it helps me? I will probably also test some mcc.c changes, as tz_regs seem different, and i don't know what device was used for those.
15:11john-cabaj has joined #asahi-dev
15:14culman has joined #asahi-dev
15:14hightower3 has joined #asahi-dev
15:22hightower4 has quit [Ping timeout: 480 seconds]
15:35culman has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
15:39culman has joined #asahi-dev
15:43culman has quit []
15:50midou has quit [Ping timeout: 480 seconds]
15:57midou has joined #asahi-dev
16:52pb17 has quit [Ping timeout: 480 seconds]
17:01touch has joined #asahi-dev
17:02touchwill a broken screen m1 work for asahi development?
17:02touchi wanna look into touch id... i see sep is already implemented so i guess it won't be very hard.
17:05fl0_id___touch, how broken?
17:06nickchangood to assume completely broken
17:06touchalmost half of the screen is flickering
17:06nickchanthe m1n1 vuart exists so it should work
17:07fl0_id___yeah but you have to install that first
17:07nickchanexternal display works in macos
17:07nickchanthis is how people use headless macbooks
17:07touchright didn't think of that
17:08nickchanonce things are installed network and such can be configured using the vuart
17:08touchso is something like touch id a big mission to take on myself?
17:08nickchanbut asahi still does not have external display so it would a headless sytem
17:08touchi have no experience with asahi development, but i do have some exp with reverse engineering
17:09nickchani think the main complication is apfs's xART locker
17:09touchi see there is a branch that supports external display which i guess will be merged soon
17:09nickchanlots of SEP functions require that and asahi doesn't have apfs parsing
17:09sventhis is gonna need significant SEP reversing fwiw
17:09nickchan+if you break that=>dfu restore
17:10svenapfs isn't the issue, the file is continuous on the disk
17:10nickchaneven though supposedly the xART locker should be contiguous on disk
17:10svenjust find the start offset and take it from there
17:10svendon't bother with APFS
17:10touchyou mean apfs parsing by the sep?
17:10nickchanno, by AP OS
17:10svenreally, ignore APFS
17:11svenwhat needs to be done is reverse engineering of the SEP<->AP protocol
17:11nickchanhypervisor can sniff out all of these messages
17:11nickchanapplication processor
17:11nickchanwhere macos/linux runs on
17:11svenand this kinda needs a dedicated machine because if you mess that xART locker file up you might need to DFU revive the mac
17:12touchso basically this would be an application reverse engineering
17:12touchreversing the os/kernel
17:12svenno, we try to avoid binary reverse engineering whenever possible
17:12touchobviously
17:13svenhook the SEP communication and stare at the protocol to figure it out
17:13sventhat's likely also gonna be faster than reversing the kext (and probably also userspace)
17:13touchyeah that's always true. i rather seeing it in action and reimplementing
17:14sventhen try to build some python script that talks to SEP. for touchid you need at least user management and the communication with that touchid peripheral
17:14touchso hooking would be done through m1n1?
17:14sventhen once that works we can think about the linux driver and userspace daemon should look like
17:14sveniirc there's some initial SEP tracer in there already
17:15touchthat's good. but how would i see communication when there is actually touch id activity
17:15sventhat will come much later
17:15touchmhm alright
17:15touchgot also an example for a script?
17:15svenyou first need SEP to talk to you and understand how the user management there works
17:16sventouchid is then just shuffling encrypted data between SEP and the touchid hardware
17:16sveni kinda expect the first part of easily take 80% of the work
17:16nnym_ has joined #asahi-dev
17:16touchalright.
17:17touchwhat stage is usually all of this happenning
17:17touchon boot or when there is user switching and such
17:17svenstage?
17:17svenno idea
17:17touchalright
17:17sventhere's certainly stuff happening on boot, but no one knows what exactly and what's actually required
17:17nickchansep booting happens during boot because that's required to unlock the data partition
17:18nickchandata volume
17:18touchyeah and you need a password first to unlock so its interesting if it's something manadatory for the sep
17:18svenyeah, but i'm sure there's also lots of unrelated stuff happening. no one really looked into this so far :-)
17:18nnym has quit [Ping timeout: 480 seconds]
17:19touchhow much of debugging info would you say there is?
17:19svenno idea :D
17:19touchshit lol
17:19touchyep i looked into it
17:20sventouchid is a surprisingly big project ;)
17:20svenunfortunately the sensor won't talk to us at all and e.g. give us raw fingerprint data so we can't just bypass SEP
17:20touchyeah it sounds something big. i got no fear from it just need enough time for it
17:21touchi'm gonna guess not a lot of debugging info will be there so there will be a lot of figuring out what each log means
17:21touchit is fortunate for security
17:21svenmaybe, xnu can be very verbose at times
17:22touchyeah but it's security stuff
17:22touchprobably don't want much logging there if i was apple
17:22sventheir security architecture is good enough, they don't need to rely on obscurity
17:23sveni wouldn't make assumptions at this stage tbh
17:23touchi don't really know i'm just guessing
17:23chaos_princessget xars/xarm endpoints first, nothing relevant will talk to you w/o it
17:23chaos_princessand those are the annoying ones with a high chance of getting a trip to dfu city
17:23sveni have some notes on the gigalocker format itself somewhere, but it's just a simple key/value store
17:23touchsry what do you mean xars/xarm?
17:24chaos_princessliterally the endpoint names
17:24touchendpoint for what? the reader?
17:25chaos_princessendpoint 0xFD will tell you the endpoints that the sep firmware exposes and the buffer sizes
17:25chaos_princessthere is a stub driver in linux already that just loads the firmware and ignores every message received on 0xfd
17:25svenhttps://f.svpe.de/262f757f4eef4825164bd703903e9f5ef2f76bd6ca410511a101a361b62084ed_gl_parse.py.txt i guess those were my notes before i gave up due to the risk of dfu trips
17:26touchisn't just kext re would be easier? ghidra can be good many times
17:26chaos_princessgoing straight to ghidra is spicy
17:26touchbtw why is there the risk of dfu?
17:26svenplease read https://asahilinux.org/copyright/ and especially the reverse engineering policy
17:27touchuh i see
17:27chaos_princessanti-rollback tokens inside of sep, if sep data inside gl file is lost, we suspect it will invalidate all boot signatures and destroy nvme encryption keys
17:27touchbut i won't change anything inside the sep, just looking at the logs
17:27sveniirc i deleted that xart file just to see what happens and ended up in dfu :D
17:28svenSEP will ask you to update that file via the xars/xarm endpoints and you kinda have to do that
17:28chaos_princessonce you start talking to sep and/or interfering with xnu trying to talk to it, you may get things wrong
17:28touchmaybe ill change if i need to experiment
17:28nickchanabout the rtkit version 10 endpoint question i have reached a point where im pretty sure i cannot answer the question properly without tracing xnu so time to bite that bullet i guess
17:28svennickchan: or just move the endpoint decision into the drivers for now
17:28nickchani need that to meaningfully progress anyway
17:29nickchanon like... touch screen
17:29chaos_princessis it not z2?
17:29nickchanpretty basic if you ask me
17:30touchfor clarifying, if i mess something up with the sep i can always restore right?
17:30Bjarne[m]Does someone want to take a look at this?
17:30nickchanbut i think there's some differences
17:30chaos_princesstouch: yes, but dfu restore wipes the disk
17:30nickchanbut i haven't gotten to that part yet, because apple changed the spi in m1
17:30nickchanand the spi i need to deal with is more like the one found in s5l8700
17:30nickchanthan the one in m1
17:30touchincluding recovery?
17:31chaos_princessit is the most low level recovery mode that is "everything wrong, we are setting up the machine as new"
17:31nickchani can tell it's similar though it's not completely changed
17:31nickchanmaybe more like an aic1/aic2 situation
17:32nickchani have iboot tracer but of course iboot doesn't do touch events
17:33touchyou also know how much sep differes between generations?
17:33pb17 has joined #asahi-dev
17:33touchyou know what ill just look into it
17:33chaos_princessnot much, it is one of the few copros that need to be backwards compatible
17:35touchalright thanks, ill look into it.
17:35fl0_id___ has quit [Ping timeout: 480 seconds]
17:36__Tetris__4 has joined #asahi-dev
17:39__Tetris__4 has quit []
17:39__Tetris__0 has joined #asahi-dev
17:39ravikant_ has quit [Ping timeout: 480 seconds]
17:40nickchani will have pongoOS do some work before m1n1 for xnu tracing cause im not about to put sep firmware load race into m1n1
17:42__Tetris__ has quit [Ping timeout: 480 seconds]
17:42__Tetris__0 is now known as __Tetris__
17:44Bjarne[m]I was also poking around with macvdmtool. I managed to get serial debug output of the target on my macOS Host (DFU to DFU).
17:44nickchanconveniently there's *always* 0x800 contineous bytes of empty space + at least 0x400 bytes of empty space elsewhere inside xnu i could use
17:44nickchanso i can put hacked vbar inside xnu
17:44nickchanand other empty space of other shellcode
17:45Bjarne[m]But while SerialShim was running which should have hooked to the /dev/tty.debug-console right?
17:45nickchanserialshim removal is not needed on macos 15+
17:45Bjarne[m]That’s why! I was wondering :D
17:46nickchanRight i have to disable spectre mitigation cause otherwise almost all kernel memory gets unmapped in el0
17:46nickchanincluding the hacked vbar
17:48nickchanby unmapping i mean T1SZ changing
17:49nickchanbecause of some ktrr the pagetables can't be freely modified but it is ok to change T1SZ
17:57nickchanalso need to mention cpus=1 im not ready to deal with smp madness yet
17:59fl0_idwould linux:asahi vs linux:asahi-wip have meaninful changes that could impact m3 bringup things? so far I always used asahi
18:00jannauBjarne[m]: sigh, I wasn't watching the repo. Did you see https://github.com/AsahiLinux/tuxvdmtool/pull/3
18:02Bjarne[m][jannau](https://matrix.to/#/@_oftc_jannau:matrix.org): yes, but as I made my PR… :/
18:09jannauBjarne[m]: did you run `cargo fmt` on your changes? `const TPS_REG_MODE : u8 = 0x03;` look a little weird
18:15yukalol, I just rebased it and now the console output from linux itself is working
18:16jannauI think I'll merge #4 first so that the sysfs interface is gone
18:19fl0_idyuka thx
18:19fl0_idlol nice
18:19fl0_idrebased on what? asahi branch?
18:20yukaasahi-wip, but I was already based on that before
18:20yukabut possibly some other change I did at the same time was the cause
18:20fl0_idok, I should also try asahi-wip just in case
18:24fl0_id___ has joined #asahi-dev
18:25yukait now complains about a missing rootfs
18:25yukaso I guess I should give it a rootfs
18:26yukathis is all with cpuhp_setup_state() call in aic init commented out btw, since it hangs there otherwise
18:35fl0_id___ has quit [Ping timeout: 480 seconds]
18:38Bjarne[m][jannau](https://matrix.to/#/@_oftc_jannau:matrix.org): No I didn’t. I can run it now
18:39Bjarne[m]I also have built a setup for merging macvdm and tuxvdm, I’m rather confident it will work but I’m trying to use as little C Code as possible.
18:40Bjarne[m]Might take a few days until I’ve time to finish macOS implementation
18:45hdbngr has quit [Ping timeout: 480 seconds]
18:52hdbngr has joined #asahi-dev
19:01hdbngr has quit [Ping timeout: 480 seconds]
19:04Bjarne[m][jannau](https://matrix.to/#/@_oftc_jannau:matrix.org): I ran cargo fmt and added a commit to PR#4
19:05hdbngr has joined #asahi-dev
19:09chadmed_ has quit [Quit: Konversation terminated!]
19:09chadmed_ has joined #asahi-dev
19:14jannauBjarne[m]: manually merged. I already ran cargo fmt on each format. also fixed all clippy issues. thanks for this, I can now drop the horrible code from the downstream tipd driver
19:18Bjarne[m]I will continue with integrating macvdmtool then.
19:19jannauBjarne[m]: maybe wait for #3 or at least ignore the multiple transports aspects of it for now
19:23Bjarne[m]Also the disclaimer could be removed now from the readme right?
19:26jannauyes, also the outdated help text. I'll do it
19:29Bjarne[m]Oh, I missed that one!
19:36pb17 has quit [Ping timeout: 480 seconds]
19:49pb17 has joined #asahi-dev
19:49fatmalama has joined #asahi-dev
20:23john-cabaj1 has joined #asahi-dev
20:24john-cabaj has quit [Ping timeout: 480 seconds]
20:24john-cabaj1 is now known as john-cabaj
20:51arcade_droid has quit [Ping timeout: 480 seconds]
20:55JoshuaPeisach[mds] has joined #asahi-dev
20:55JoshuaPeisach[mds]kernel newbie here, question about the TODO in the “asahi” drm driver. I see it wants DMA address/range validation, is it basically just ensure address + range > kernel VA range global?
21:02chaos_princessmind linking the line?
21:02jannauyou mean the ones in mmu.rs?
21:04jannauI'm not sure but isn't the kernel VA range check more complicated as user space is free to place that where it likes
21:06___nick___ has quit [Remote host closed the connection]
21:06jannauyeah. we get to remove all the '.as_ref()' from the dev_* print macros again
21:33ravikant_ has joined #asahi-dev
21:33ravikant_ has quit []
22:11hightower3 has quit [Ping timeout: 480 seconds]
22:21fl0_id___ has joined #asahi-dev
22:51hdbngr has quit [Ping timeout: 480 seconds]
22:54hdbngr has joined #asahi-dev
22:57pb17 has quit [Ping timeout: 480 seconds]
22:59pb17 has joined #asahi-dev
23:19hdbngr has quit [Remote host closed the connection]
23:19hdbngr has joined #asahi-dev
23:22fl0_id___ has quit [Remote host closed the connection]
23:22fl0_id___ has joined #asahi-dev
23:36hdbngr has quit [Ping timeout: 480 seconds]
23:44hdbngr has joined #asahi-dev
23:52fl0_id___ has quit [Ping timeout: 480 seconds]
…