2022-08-28
00:12phiremarcan: yes I've tried to talk to the ALARM folks too. Got slightly more than radio silence, but they don't really seem to be interested in being anything more than a distro for low-cost single-board computers.
00:17phireWhich is understandable. It might be more accurate to say it's a project that feels like it has acheived it's goals and doesn't want to expand it's scope futher
00:21chadmedmarcan: could you define "up to standard" for the gentoo port? its in pretty good shape imo, we have an overlay and an installer that takes care of all the apple-isms. what else could i take care of to make it better (apart from binpkgs)?
00:22chadmednoting that once lina gets the kernel driver up to scratch ill copy over the mesa ebuild from the gentoo tree and add a VIDEO_CARDS for asahi but thats a while away
00:27Race has joined #asahi-dev
01:00DragoonAethis has quit [Quit: hej-hej!]
01:00DragoonAethis has joined #asahi-dev
01:04DarkShadow44 has quit [Quit: ZNC - https://znc.in]
01:04DarkShadow44 has joined #asahi-dev
01:18riker77_ has joined #asahi-dev
01:23riker77 has quit [Ping timeout: 480 seconds]
01:23riker77_ is now known as riker77
01:51e1eph4nt has joined #asahi-dev
02:02e1eph4nt has quit [Remote host closed the connection]
02:07psanford has quit [Ping timeout: 480 seconds]
02:09e1eph4nt has joined #asahi-dev
02:10psanford has joined #asahi-dev
02:17e1eph4nt has quit [Ping timeout: 480 seconds]
02:22bluetail21 has quit [Ping timeout: 480 seconds]
02:26e1eph4nt has joined #asahi-dev
02:27goosteady has joined #asahi-dev
02:34e1eph4nt has quit [Ping timeout: 480 seconds]
02:42chadmed_ has joined #asahi-dev
02:42e1eph4nt has joined #asahi-dev
02:47Mary has quit [Quit: The Lounge - https://thelounge.chat]
02:48Mary has joined #asahi-dev
02:56bluetail21 has joined #asahi-dev
03:10pyropeter1 has joined #asahi-dev
03:12PyroPeter_ has quit [Ping timeout: 480 seconds]
03:14chadmed_ has quit [Quit: Konversation terminated!]
03:29uniq has joined #asahi-dev
03:50uniq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:50e1eph4nt has quit [Ping timeout: 480 seconds]
03:55e1eph4nt has joined #asahi-dev
04:00duban has quit [Quit: I'm out]
04:03duban has joined #asahi-dev
04:49marcanFoxboron: he replied to my initial email within a day or two, but hasn't replied to my response for a week
04:51marcanmain things that need to be right are m1n1/u-boot/kernel updates with some kind of sensible automation (though it's gentoo so obviously there will still be some manual stuff) and an init.d script to update firmware on every boot if it has changed
04:51marcanthe latter, ideally before udev even starts (I need to change the arch script to do that too, right now it's racy)
04:52marcanmaybe some kind of "eselect dt" thing to choose which of the installed kernels' DTBs are installed into m1n1?
04:56kode54best part about gentoo on Apple Silicon is that you don't have to spend an hour configuring your kernel to fulfill the "desired" fully custom kernel that only has exactly what you'll ever need forever more
04:57kode54(there is no real way to do that anyway, there are countless peripherals you could conceivably attach
04:58kode54well, the last time someone tried to sell me on setting up Gentoo, they insisted I hand configure my kernel rather than use a jack-of-all-trades config
05:00marcanpersonally, these days I actually have a silly script on my Threadripper chroot that builds 3 kernels for all my servers (two variants intended for bare metal and one for VMs, though I will probably unify the two bare metal ones some day)
05:03marcananyway, I have some kernel stuff to take care of this coming week (maz: haven't forgotten about your USB ports) but I'll also start working on helping out with the Fedora port
05:03e1eph4nt has quit [Ping timeout: 480 seconds]
05:04kode54I'll take this to offtopic, but I've kind of fallen into a rut, and started maining my Ryzen machine on Arch instead for the time being
05:04marcanas for gentoo, maybe I should install it on my Mac Studio? though considering I want to run Ceph and the Gentoo maintainer for that has been kind of bad at keeping it building across compiler/boost updates, I'm a little worried. Fedora might be a better bet for that reason alone... but we'll see
05:05kode54good luck, it is annoying when updates just break things, then you have to pick up the pieces
05:12e1eph4nt has joined #asahi-dev
05:17phirekode54: I came the the conclusion that idealy ALARM would merge upstream into proper Arch Linux, or Arch Linux would otherwise transition into being a multi-arch distro. But you would kind of need someone willing to become a full-time maintainer on that effort to push that fowards
05:20e1eph4nt has quit [Ping timeout: 480 seconds]
05:29e1eph4nt has joined #asahi-dev
05:39DmitrySharshakov[m]I have a bit of concern about Fedora aarch64. It appears that it's hard/impossible to setup multiarch (x86_64 libraries on aarch64 system), so that might cause issues with emulation (box86/box64), which is an integral part of Apple Silicon experience and is generally needed for full compatibility
05:45e1eph4nt has quit [Ping timeout: 480 seconds]
05:46e1eph4nt has joined #asahi-dev
06:09hir0pro has joined #asahi-dev
06:35Glanzmannmarcan: From my point of view, what is missing for all distributions, is the ability to have multiple dts installed. In my head the way to that would be having keyboard support in m1n1, and be able to select the right m1n1, which has the right dt in it. And whilt it is already there no need for u-boot and grub. But of course this could also be the case but it no longer necessary. But maube you have a
06:35Glanzmannbetter idea. Than for Debian the kernel packages could package the corresponding /boot/efi/m1n1/m1n1-kernelversion.bin and we have multiple kernerls.
06:37Glanzmannkettenis: I aggree. But in practice we have that since beginning until now. We have an upstream kernel that does not boot with the asahi dt and vice versa.
06:39Glanzmannkettenis: Sure, but to my understanding that bug can not be fixed at the moment because the understanding of the hardware is not completle. And while it completes the dt will change, break more stuff in the future.
06:43GlanzmannAnyhow, while it is alpha software, I welcome the ability to have multiple dts without having the need of a second computer or copy over boot.bins in macos. But that is just me. I'm happy with removing this workaround until the hardware is better understood and manifested in the dt.
06:45uniq has joined #asahi-dev
06:57GlanzmannTo be honest if it annoys me to much, I will just implement it myself. But probably it doesn't. And since I only have m1 devices at the moment it would be useless for the Debian users, which need it the most.
06:57e1eph4nt has quit [Ping timeout: 480 seconds]
07:02marcanthe m1n1 boot picker thing might happen, well into the future, when it makes sense for secure boot
07:03marcanGlanzmann: and I really would appreciate it if you don't try to subvert our development incentives, though I can't stop you
07:24e1eph4nt has joined #asahi-dev
07:31uniq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:31shorneHello, I am a kernel maintainer of the OpenRISC port, I have some experience with toolchains and kernel. I would like to help on asahi, particularly getting suspend to work
07:32e1eph4nt has quit [Ping timeout: 480 seconds]
07:33DmitrySharshakov[m]Oh nice, welcoome! marcan is planning to work on s2idle the next stream or so (?).
07:34DmitrySharshakov[m]marcan: btw when is the next kernel stream planned?
07:34DmitrySharshakov[m]Presumably the main task is to figure out PSCI without the ARM Trusted Firmware. Correct me if my info is terribly outdated
07:35Glanzmann has quit [Quit: leaving]
07:36shorneDmitrySharshakov[m]: cool, in that case maybe I can help review patches, if I heard right drivers like pci need to be updated to handle the idle states
07:37DmitrySharshakov[m]Typically for PM ops we (the kernel living in EL2 while being capable of virtualization) must ask someone higher (EL3) to manage power interfaces. This is the PSCI calling ABI. But Apple SoC has no TrustZone extension, so PSCI need to be handled by the kernel itself. I guess marcan has already invented the idea of this fix
07:39DmitrySharshakov[m]I'm not sure (not a maintainer, I'm here mostly for news + I do some work for userspace audio in PipeWire), but 99% you can do this
07:39DmitrySharshakov[m]Quite a bit of testing should be needed to ensure the best efficiency and stability
07:41e1eph4nt has joined #asahi-dev
07:41DmitrySharshakov[m]Well, PCIe controller driver should definitely be updated for suspend/resume xD
07:41DmitrySharshakov[m]PSCI is power system coordination interface iirc
07:42DmitrySharshakov[m]Probably better to wait for marcan, as he certainly has more fresh info about PM than I do
07:43DmitrySharshakov[m]j`ey: yes it is, thanks
07:50hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:04uniq has joined #asahi-dev
08:07DmitrySharshakov[m]sven: WiFi on its own or because APCIe breaks in some way?
08:07DmitrySharshakov[m]What's wrong exactly? Might it be a generic brcmfmac issue or platform one?
08:08DmitrySharshakov[m]sven: Hasn't it yet been proposed?
08:09DmitrySharshakov[m]Well, not all ARM SoCs use PSCI for PM. Should M1 do so? Does it use PSCI in macOS? Can it be avoided by simply doing all by register writes (SMP bringup reversed)?
08:11svenWiFi on its own because apple invented sone suspend protocol that’s different from what brcmfmac supports
08:11DmitrySharshakov[m]x86 does its s2idle (S0ix) like this: 1. bring down non-boot cpus, 2. suspend pcie peripherals, 3. drive the CPU 0 into low-power idle
08:11svenI think there was at least one report that pcie itself also breaks but when I tested bt resume it just worked
08:12DmitrySharshakov[m]But yes, I guess that'd duplicate what is done by default PSCI
08:12DmitrySharshakov[m]sven: So you just suspended to idle, without bringing CPUs down?
08:13hir0pro has joined #asahi-dev
08:13DmitrySharshakov[m]I guess suspend protocol can be reversed by m1n1 introspection, or doesn't macOS suspend work while booted under HV?
08:14svenI think we already have a good idea how deep sleep work. Flip some sysreg to enable it, store cpu context, wfi, restore context, disable deep wfi again
08:15DmitrySharshakov[m]sven: Yea. Why would it break kernel concepts?
08:15DmitrySharshakov[m]sven: I meant cannot you watch macOS suspending and resuming wireless with m1n1 hypervizor?
08:18DmitrySharshakov[m]does arm even have deep sleep? Is it like x86 where EC wakes the system up? Probably ARM has a different concept
08:18j`eyI know someone that is 'against' the psci/efi/el2 idea, and was suggesting to maybe try improve the spin-table stuff, but that wouldn't help with the actual power usage
08:20DmitrySharshakov[m]sven: btw how are your ATCPHY/TB-NHI/USB3 works? Are you testing locally without a branch or there's a branch to watch the news?
08:21DmitrySharshakov[m]Ah, no kernel driver yet?
08:22DmitrySharshakov[m]And what's left/which questions are to be answered?
08:23DmitrySharshakov[m]Something like PD-out and DP tunneling?
08:23hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:24DmitrySharshakov[m]Have you figured out the DP thing you asked recently?
08:24DmitrySharshakov[m]Like plain DP not tunneled in TB4
08:25DmitrySharshakov[m]Or there's DCP dependency for it to work with external display?
08:29DmitrySharshakov[m]understood, good luck REing it for a perfect driver
08:31hir0pro has joined #asahi-dev
08:32DmitrySharshakov[m]well, yes actually!
08:36hir0pro has quit []
08:42hir0pro has joined #asahi-dev
08:42riker77 has quit [Quit: Quitting IRC - gone for good...]
08:49e1eph4nt has quit [Ping timeout: 480 seconds]
08:52riker77 has joined #asahi-dev
08:54DmitrySharshakov[m]Are you going to do it by a new register-based driver or adapt PSCI for running in EL2? Btw does OpenBSD kernel on M1/M2 run in EL2?
08:56DmitrySharshakov[m]Ah, so are you planning to run a bit of code in EL2 for the kernel to call into for PSCI actions?
08:57DmitrySharshakov[m]Probably needs a long-term solution that won't be a roadblocker to running the kernel in EL2
08:57j`eyDmitrySharshakov[m]: the PoC I wrote (for linux) puts the PSCI handler in m1n1, which is then put into the EFI memory map
08:58DmitrySharshakov[m]Ah, cool. So it'll call into U-Boot or so? I've not really seen PSCI-in-EFI
08:58DmitrySharshakov[m]Ah, m1n1 will also implement a part of EFI stuff
08:58DmitrySharshakov[m]j`ey: can I have a link to the branch?
08:59hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:59e1eph4nt has joined #asahi-dev
09:00hir0pro has joined #asahi-dev
09:02DmitrySharshakov[m]I've seen various cpuidle drivers for arm not being backed by psci, like [some Qualcomm one](https://github.com/torvalds/linux/blob/master/drivers/cpuidle/cpuidle-qcom-spm.c)
09:02DmitrySharshakov[m]Why cannot it be done this way for Apple SoCs?
09:03ricekot has joined #asahi-dev
09:03DmitrySharshakov[m]Yes, I was asking why they won't?
09:03DmitrySharshakov[m] * Yes, I was asking why they won't
09:04uniq has quit [Quit: Textual IRC Client: www.textualapp.com]
09:06DmitrySharshakov[m]That changes all the things. If m1n1 has to do that, then let it be sorta firmware to deal with PSCI in a generic manner. Will also reduce code duplication then. Thanks for explaining!
09:07e1eph4nt has quit [Ping timeout: 480 seconds]
09:07DmitrySharshakov[m]So macOS didn't ever have this problem as XNU is the reset vector (or called shortly after it)
09:10DmitrySharshakov[m]lol having no need to detect things saves quite a lot of thinking and LoC
09:18e1eph4nt has joined #asahi-dev
09:19DmitrySharshakov[m]This exactly :) Also any Linux driver has to match other drivers' and userspace behavior, so it needs some more complex approach
09:24svenApple also has some horrible hacks in their kernel. I still enjoy the fake-gpu-iommu kext and adt node that’s just a wrapper that calls back into the main gpu kext
09:25DmitrySharshakov[m]just why?
09:25svenso if the main kext allocates io memory it’ll call into their iommu api which calls the fake iommu kext which calls back into the main kext :D
09:26svenmy best guess is that the gpu kext team didn’t want to or wasn’t allowed to talk to the iommu team to get some api to just register custom iommu ops
09:28DmitrySharshakov[m]Well, not adding UAT as a type of IOMMU page, but introducing a fake driver translating UAT into common IOMMU call
09:28DmitrySharshakov[m]sven: maybe
09:31svenalso different incentives. Linux will probably support m1 drivers for 10+ years. Apple can just drop support or introduce breaking changes whenever they want to.
09:35DmitrySharshakov[m]Well, generally Apple also does ~10 years cycle (with end of it being maintenance bugfixes and security only), but with Linux the same HW should remain useful for a lot more considering its power. And, of course, those drivers need to be flexible enough (proven by M2) to be adaptable for newer generations
09:58svencan anyone with a m1 pro/max run trace_device("/arm-io/atxN-xbar") for all atcs and then plug two external screens into some usb-c ports using dp altmode?
10:26e1eph4nt has quit [Ping timeout: 480 seconds]
10:30bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:30bisko has joined #asahi-dev
10:36jannauhah, tricked myself. cn't trace atc0-dpxbar when stealing that port for the HV. I checked the adt first for a typo
10:45Foxboronmarcan: hrm, still not sure what it's about. Holla at me if you need anything into actual Arch though
10:50svenhrm, interesting. looks like I’ll have to go and figure out how the dcpext maps to bits in that register then
10:51svenxnu talks about dcpextN,M so maybe they want to support two streams inside each dcpext at some point? dunno
10:51bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
10:59ricekot has quit [Quit: ttyl]
11:09e1eph4nt has joined #asahi-dev
11:13hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:22bisko has joined #asahi-dev
11:27hir0pro has joined #asahi-dev
11:30chadmedmarcan: the overlay already has our u-boot, m1n1 and linux-asahi with the tags shipping with the installer keyworded as arm64 and the latest tag as ~arm64. update-m1n1 and update-vendor-fw are installed in /bin by the installer as well as a local.d script which runs update-vendor-fw on every boot. the only thing i need to get around to for feature parity is that python firmware thing if thats still relevant
11:30hir0pro has quit []
11:32chadmedi edited update-m1n1 to grab from /usr/src/linux/arch/arm64/boot/dts/apple/*.dtb, u-boot and m1n1 binaries after being build are doins-ed to /usr/lib/asahi-boot or wherever the alarm pkgbuild puts them, i reused the path
11:33hir0pro has joined #asahi-dev
11:35hir0pro has quit []
11:35chadmediirc the original intention for new hw enablement was to update the vendor-fw tarball from macos and have linux check it for changes on every boot
11:36chadmedwhich is how i got the bt firmware sorted, so i just went with it for now until we figure out something better
11:37chadmedthe script just immediately exits if theres nothing new so its not like its copying all the brcmfmac firmware on every boot or anything
11:42svenit’s a good idea to do it every boot because then you can also be sure it works because it’s tested all the time
11:42DmitrySharshakov[m]Btw does the script also forward the ICC profile to Linux? It could be useful, since all Macs have factory screen calibration. When DCP is ready (btw what stops it from being merged into Asahi branch?) we'll 100% be able to make use of it
11:43DmitrySharshakov[m]Unsure, but maybe simple simpledrm also can apply gamma ramps needed for calibration
11:44chadmedalso the simpledrm crtc does not have a gamma lut so colour correction wont work in kwin or mutter just yet, its why i cant daily linux just yet
11:44DmitrySharshakov[m]chadmed: I guess ICC profiles worked on Wayland for long now (with default colorspace)
11:46chadmediirc the whole reason its been an issue is because applications simply do not obey colour management information in the protocol, and the thrust now is for compositors/wms to take control of it
11:46DmitrySharshakov[m]sven: Well, I know it's somewhere in /usr/share for macOS, but to persist between reinstalls and wiping it should be somewhere in DT or EDID-like thing
11:46DmitrySharshakov[m]chadmed: Yes, when KWin applies the gamma (e.g. night colour setting), it does this over the whole screen
11:47DmitrySharshakov[m]Color management is a problem for HDR, where you need to process a lot of colorspaces and extra metadata
11:47chadmedyeah but the goal for kwin and mutter right now is to no longer apply gamma correction, which relies on LUTs from the kernel display driver
11:47chadmedthere were links to where theyre discussing this upstream for both compositors in #asahi-gpu if you can find them
11:49chadmedthis is an issue on eg nvidia cards, since their kms driver does not supply gamma luts which is why night mode doesnt work under wayland on some of those chipsets
11:51DmitrySharshakov[m]Hmm, okay, just need to find the right place to obtain a copy of calibration data (to the firmware question)
11:51DmitrySharshakov[m]So what are the showstoppers on the DCP code now?
11:52jannauchadmed: I think we should make ebuilds for the manually installed scripts and an asahi-meta ebuild
11:53chadmedjannau: agreed, it was on my list but ive had a bunch of stuff due these past few weeks and time slipped away from me. happy to take contributions as usual ;)
11:54jannauI hope the screen calibration data is in the adt, the dcp driver will need to provide it for DCP
12:00chadmedproduct/primary-calibration-matrix and product/artwork-display-gamut seem to be what we want wrt screen cal btw
12:00DmitrySharshakov[m]Are those in the ADT dump?
12:07DmitrySharshakov[m]Temperature compensation independent from gamma? Weird thing
12:07DmitrySharshakov[m]Maybe that's not color temperature but some thermal coefficients xD
12:08DmitrySharshakov[m]But that shouldn't matter for LCDs even in pro workloads
12:08DmitrySharshakov[m]What formats are those nodes and their data? Is there a dump to look at?
12:10jannauwtf apple "nits-to-pwm-percentage-part1" and "nits-to-pwm-percentage-part2" properties for the keyboard backlight
12:11DmitrySharshakov[m]could you please paste?
12:11DmitrySharshakov[m]Is there nits-to-pwm-percentage record for the screen and touchbar?
12:12gabuscus_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
12:12gabuscus has joined #asahi-dev
12:13jannauI think display-temp-compensation is thermal. I guess it's required for the the mini leds for max brightness in HDR mode
12:14e1eph4nt has quit [Ping timeout: 480 seconds]
12:15jannauno touchbar and the backlight has no such properties but it has "milliAmps2DACTablePart1" and "milliAmps2DACTablePart2"
12:17DmitrySharshakov[m]jannau: Does SMC report something related to screen temp?
12:18DmitrySharshakov[m]jannau: So you know current drive but don't know nits :/
12:19DmitrySharshakov[m]Did you take the dump on Liquid Retina XDR-enabled laptop (14" or 16")?
12:21DmitrySharshakov[m]I guess AS machines are going to have the most hwmon sensors ever
12:22DmitrySharshakov[m]Sound amps also have temp sensor available via i2c regs, so add 6 more on Pro's :)
12:24e1eph4nt has joined #asahi-dev
12:26DmitrySharshakov[m]What remains untested or nonfunctional within DCP driver which prevents it from being in Asahi kernel? If gamma LUT change is proposed than it could be changed
12:32e1eph4nt has quit [Ping timeout: 480 seconds]
12:39DmitrySharshakov[m]Also, what is the temperature range backlight can heat up? Maybe that's not only a technique to compensate light intensity correlation with temperature, but also a protection mechanism? I really hope it has proper cooling from the top cover and cannot be really hotter than ~50 °C
12:40e1eph4nt has joined #asahi-dev
12:48matthewayers[m]It probably is in there as a protection mechanism that is seldom used but is still necessary. I wouldn’t be surprised if some computers caught on fire or had issues due to the heat from the screen
12:48e1eph4nt has quit [Ping timeout: 480 seconds]
12:49matthewayers[m](At Apple during testing more than likely)
12:50matthewayers[m]Maybe not a single one by itself but a tightly packed array of them could be more of a threat
12:51tpw_rulesthen the chinese would have burned down half the western world with crappy led light bulbs by now
12:51DmitrySharshakov[m]Laptop LED backlight almost never has issues. Only TVs burn like that
12:52tpw_rulesan led overheats, goes open circuit, then something that really shouldn't suddenly has 250V across it
12:53tpw_rulesthen starts arcing. but a battery powered device like a laptop wouldn't have an led circuit like that
12:54DmitrySharshakov[m]I guess MacBook has the whole back cover as a heatsink to those LEDs, so they should be safe. To heat up over 50 degrees they need a couple tens of watts
12:57e1eph4nt has joined #asahi-dev
12:57hir0pro has joined #asahi-dev
13:01matthewayers[m]That’s a good point. I’m not the most experienced when it comes to LEDs, clearly 😅
13:03hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:09hir0pro has joined #asahi-dev
13:16rappet has joined #asahi-dev
13:35Race has quit [Ping timeout: 480 seconds]
14:04e1eph4nt has quit [Ping timeout: 480 seconds]
14:13e1eph4nt has joined #asahi-dev
14:22e1eph4nt has quit [Ping timeout: 480 seconds]
14:30e1eph4nt has joined #asahi-dev
14:38e1eph4nt has quit [Ping timeout: 480 seconds]
14:47Gaspare has joined #asahi-dev
14:48e1eph4nt has joined #asahi-dev
14:49Gaspare has quit []
14:54hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:56e1eph4nt has quit [Ping timeout: 480 seconds]
15:00the_lanetly_052__ has quit [Ping timeout: 480 seconds]
15:04hir0pro has joined #asahi-dev
15:05e1eph4nt has joined #asahi-dev
15:09the_lanetly_052__ has joined #asahi-dev
15:31nicolas17 has joined #asahi-dev
15:31the_lanetly_052__ has quit [Ping timeout: 480 seconds]
16:12e1eph4nt has quit [Ping timeout: 480 seconds]
16:21e1eph4nt has joined #asahi-dev
16:34e1eph4nt has quit [Remote host closed the connection]
16:36e1eph4nt has joined #asahi-dev
16:51e1eph4nt has quit [Ping timeout: 480 seconds]
16:51hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:53hir0pro has joined #asahi-dev
16:59e1eph4nt has joined #asahi-dev
17:09yuyichao_ has quit [Quit: Konversation terminated!]
17:10yuyichao_ has joined #asahi-dev
17:18rainlire[m] has joined #asahi-dev
17:22andersonwatts[m]1 has joined #asahi-dev
17:25Mrmaxmeier has quit [Quit: The Lounge - https://thelounge.chat]
17:26Mrmaxmeier has joined #asahi-dev
17:27Mrmaxmeier has quit []
17:28Mrmaxmeier has joined #asahi-dev
17:56hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:58mini0n has joined #asahi-dev
17:58hir0pro has joined #asahi-dev
17:59mini0n has quit []
18:02andersonwatts[m]1 "I'll help 10individuals how to earn $30,000 in 72 hours from the crypto market. But you pay me 10% commission when you receive your profit. if interested send me a direct message on WhatsApp by asking me (HOW) for more details on how to get started
18:02andersonwatts[m]1 +1 (559) 666‑3967
18:08andersonwatts[m]1 was kicked from #asahi-dev by ChanServ [SPAM]
18:49marcansven: pcie broke with the power domains going down, it probably will work with them marked always on as long as the pcie link also doesn't go down (since no hotplug)
19:11jakebot60 has quit [Quit: The Lounge - https://thelounge.chat]
19:13hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:13e1eph4nt has quit [Ping timeout: 480 seconds]
19:16hir0pro has joined #asahi-dev
19:23e1eph4nt has joined #asahi-dev
19:31e1eph4nt has quit [Ping timeout: 480 seconds]
19:40e1eph4nt has joined #asahi-dev
19:48e1eph4nt has quit [Ping timeout: 480 seconds]
19:56e1eph4nt has joined #asahi-dev
20:35balrog has quit [Quit: Bye]
20:43balrog has joined #asahi-dev
21:03e1eph4nt has quit [Ping timeout: 480 seconds]
21:13e1eph4nt has joined #asahi-dev
21:21e1eph4nt has quit [Ping timeout: 480 seconds]
21:23jakebot60 has joined #asahi-dev
21:30e1eph4nt has joined #asahi-dev
21:34benpoulson has joined #asahi-dev
21:40c10l0 has quit []
21:42benpoulson has quit [Ping timeout: 480 seconds]
21:44c10l0 has joined #asahi-dev
21:47c10l0 has quit []
21:47c10l has joined #asahi-dev
21:56hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
22:07systwi_ has joined #asahi-dev
22:11systwi has quit [Ping timeout: 480 seconds]
22:18mini0n has joined #asahi-dev
22:24mps has quit [Ping timeout: 480 seconds]
22:38e1eph4nt has quit [Ping timeout: 480 seconds]
22:44e1eph4nt has joined #asahi-dev
23:11cste005 has joined #asahi-dev
23:21mini0n has quit [Ping timeout: 480 seconds]
23:25e1eph4nt has quit [Remote host closed the connection]
23:34e1eph4nt has joined #asahi-dev
23:48jluthra_ has quit [Remote host closed the connection]
23:48jluthra_ has joined #asahi-dev
23:48Race has joined #asahi-dev
23:50e1eph4nt has quit [Remote host closed the connection]
23:53e1eph4nt has joined #asahi-dev
23:58yrlf has joined #asahi-dev