2022-03-22
00:27chadmed has joined #asahi-dev
00:41nicolas17marcan: ohh, I figured 4 bytes couldn't be padding, but if the 00 is relevant that changes things :)
00:43ryan_nupp[m] has joined #asahi-dev
00:55skipwich has joined #asahi-dev
01:02caef^ has joined #asahi-dev
01:04yuyichao_ has quit [Ping timeout: 480 seconds]
01:06nicolas17and instead of figuring out how to explain that idea I decided to make a proof of concept https://cdn.imgpaste.net/2022/03/22/KMTj2v.png
01:15marcanbut the thing about the python is that it's not just a dissector, we often use the same frameworks to then build actual clients, e.g. DCP
01:16yuyichao_ has joined #asahi-dev
01:16marcanso writing wireshark modules would be somewhat duplicative if we're going to write that anyway
01:16nicolas17yeah I saw that the magic of construct and ipc.py lets you use the same code to dissect and to marshal new calls
01:16marcanand the protocols are very heterogeneous, DCP already uses two different IPC mechanisms (this is only one of them) plus other stuff
01:54j`ey has quit [Remote host closed the connection]
01:55j`ey has joined #asahi-dev
01:58nicolas17 has quit [Ping timeout: 480 seconds]
02:01minecrell has quit [Quit: Ping timeout (120 seconds)]
02:02minecrell has joined #asahi-dev
02:10nicolas17 has joined #asahi-dev
02:42kylealanhale has joined #asahi-dev
02:51riker77_ has joined #asahi-dev
02:55riker77 has quit [Ping timeout: 480 seconds]
02:55riker77_ is now known as riker77
03:00pzcz has joined #asahi-dev
03:02pzcz has quit [Remote host closed the connection]
03:06pzcz has joined #asahi-dev
03:06snek has quit [Server closed connection]
03:07snek has joined #asahi-dev
03:07pzcz has quit [Remote host closed the connection]
03:07sjg1 has quit [Server closed connection]
03:07sjg1 has joined #asahi-dev
03:09pzcz has joined #asahi-dev
03:10pzcz has quit [Remote host closed the connection]
03:20pzcz has joined #asahi-dev
03:21pzcz has quit [Remote host closed the connection]
03:26phiologe has joined #asahi-dev
03:29pzcz has joined #asahi-dev
03:29pzcz has quit [Remote host closed the connection]
03:29PhilippvK has quit [Ping timeout: 480 seconds]
03:35pzcz has joined #asahi-dev
03:36pzcz has quit [Remote host closed the connection]
03:40Gaelan has quit [Server closed connection]
03:41Gaelan has joined #asahi-dev
03:50kov has quit [Quit: Coyote finally caught me]
03:50kov has joined #asahi-dev
04:00nicolas17marcan: https://cdn.imgpaste.net/2022/03/22/KMfV0u.png starts to look more useful with request-response tracking :)
04:04kenzie35 has quit [Server closed connection]
04:04kenzie35 has joined #asahi-dev
04:05nicolas17I'm just exploring the possibilities, with my current code it would be completely impractical to decode all the methods
04:09Dcow[m]1yeah I know installer has it. I was thinking that maybe we can deliver only package deps with installer if macos has it. but ok.
04:09jn has quit [Read error: Connection reset by peer]
04:10jn has joined #asahi-dev
04:13kylealanhale has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:16kode54 has quit [Server closed connection]
04:16kode54 has joined #asahi-dev
04:16bpye has quit [Server closed connection]
04:16bpye has joined #asahi-dev
04:35nicolas17 has quit [Ping timeout: 480 seconds]
04:40tardyp has quit [Server closed connection]
04:40tardyp has joined #asahi-dev
04:40nkaretnikov has quit [Server closed connection]
04:40nkaretnikov has joined #asahi-dev
04:58pzcz has joined #asahi-dev
04:58pzcz has quit [Remote host closed the connection]
05:01pzcz has joined #asahi-dev
05:02pzcz has quit [Remote host closed the connection]
05:03axboe has quit [Server closed connection]
05:03axboe has joined #asahi-dev
05:07pzcz has joined #asahi-dev
05:07pzcz has quit [Remote host closed the connection]
05:17WhyNotHugo has quit [Server closed connection]
05:17WhyNotHugo has joined #asahi-dev
05:20coder_kalyan has quit [Server closed connection]
05:20coder_kalyan has joined #asahi-dev
05:21nametable[m]Is tethered boot with m1n1 the best bet for beginning to reverse engineer hardware and test changes to the kernel? So far I have tested the release version of Asahi Linux, but now I am looking to start messing around with the hardware
05:22nametable[m]Also, does m1n1 boot either Linux or MacOS? If I understand right, m1n1 just allows a debug interface over USB while the system is running... letting me examine and change registers....?
05:30gpanders_ has quit [Server closed connection]
05:31gpanders_ has joined #asahi-dev
05:44nyx_o has quit [Server closed connection]
05:45nyx_o has joined #asahi-dev
05:46pzcz has joined #asahi-dev
05:47pzcz has quit [Remote host closed the connection]
06:06balrog has quit [Server closed connection]
06:06balrog has joined #asahi-dev
06:11kylealanhale has joined #asahi-dev
06:30megalokafes_ has quit [Server closed connection]
06:30megalokafes_ has joined #asahi-dev
06:33jeffmiw has quit [Ping timeout: 480 seconds]
06:46Simonx22 has quit [Server closed connection]
06:46Simonx22 has joined #asahi-dev
06:47kevans91 has quit [Server closed connection]
06:47kevans91 has joined #asahi-dev
06:52winter has quit [Server closed connection]
06:52winter has joined #asahi-dev
07:04King_InuYasha has quit [Server closed connection]
07:04King_InuYasha has joined #asahi-dev
07:34Darkmatter66 has quit [Server closed connection]
07:35Darkmatter66 has joined #asahi-dev
07:35kylealanhale has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:47skipwich has quit [Server closed connection]
07:47skipwich has joined #asahi-dev
07:47Major_Biscuit has joined #asahi-dev
07:48juancri has joined #asahi-dev
07:55Major_Biscuit has quit [Ping timeout: 480 seconds]
07:59Glanzmann has quit [Quit: leaving]
08:19kylealanhale has joined #asahi-dev
08:27kylealanhale has quit [Ping timeout: 480 seconds]
08:54tbodt has quit [Server closed connection]
08:54tbodt has joined #asahi-dev
08:55MajorBiscuit has joined #asahi-dev
09:08rbenua has quit [Server closed connection]
09:09rbenua has joined #asahi-dev
09:26koorogi has quit [Server closed connection]
09:26koorogi has joined #asahi-dev
09:36hitmoon has joined #asahi-dev
09:38pzcz has joined #asahi-dev
09:39pzcz has quit [Remote host closed the connection]
09:49hays has quit [Server closed connection]
09:49hays has joined #asahi-dev
10:00Z750 has quit [Server closed connection]
10:00Z750 has joined #asahi-dev
10:03joske has joined #asahi-dev
10:05joskemarcan: I'm trying to adapt the asahi-alarm-builder for manjaro linux, I have a question regarding the pacstrap step, where does this asahilinux-keyring package come from? Is it already in the Arch repos?
10:10joskej`ey: thx, I have that build on my current setup and installed, but the pacstrap (basestrap in manjaro) seems to try to get it from arch repos
10:12chadmedthe image builder contains the asahi mirrorlist and runs a shell script to install it into pacman.conf and set up the asahi repo properly
10:23marcan(that's the only package needed since otherwise we start with a fully baked ALARM tarball)
10:25arndsven: I'm trying to make sense of the nvme+sart driver, as it feels a bit awkward to have a custom interface for something that is half an IOMMU. I think i would be nicer to either have sart fully integrated with the apple-nvme driver, or more generic with its own dma_map_ops or as part of drivers/iommu.
10:27svenarnd: i wanted to reply later today but essentially the issue is that NVMe has two IOMMU-like things. once this tightly coupled NVMMU for most commands and then this SART thing for buffers like the syslog and some vendor-specific NVMe commands that don't use the normal PRPs
10:29emptynine has quit [Server closed connection]
10:29emptynine has joined #asahi-dev
10:29sventhere's one array (which apple calls linear sq) where you setup the command and then another array where you set it up again (which apple calls NVMMU)
10:29sventhey split it because they have this fake-hypervisor which setups the latter while the kernel sets up the first
10:31svenand if it's more than two pages they setup the PRP structure twice, once inside kernel-controller memory and a second time inside fake-hypervisor-controlled memory
10:32joske has quit [Remote host closed the connection]
10:33joske has joined #asahi-dev
10:34svenI don't have any strong preference for keeping SART separate. it just felt like a different device.
10:34arndsven: so there is no address translation at all between NVMe and RAM, but multiple address filters?
10:36Ariadne has quit [Server closed connection]
10:36Ariadne has joined #asahi-dev
10:37arndsven: ok, thanks for the background, I'll read the implementation again to get to a more informed opinion. For the moment, I'm leaning towards "not-in-my-backyard" and would rather see the SART code merged into the nvme driver because that keeps it out of drivers/soc ;-)
10:38mazsven: I had similar questions about the rtkit driver, which smells a lot like a "standard" mailbox driver...
10:38arndsven: not sure if that has any implications on the DT binding, kettenis might have an opinion on what representation of the SART makes the most sense for openbsd or u-boot though
10:40tmlind has quit [Server closed connection]
10:40tmlind has joined #asahi-dev
10:40svenabout to grab lunch, can reply about rtkit later. but if we move rtkit to mailbox we have to keep SART separate because both rtkit buffers and nvme vendor-specific commands (which we may or may not need in the future) are filtered by SART
10:40arndregarding the rtkit driver, the mailbox subsystem is generally a very leaky abstraction, but the one thing it does provide is a way to multiplex a number of mailbox instances over a shared hardware block, and a somewhat generalized DT binding for describing that multiplexing
11:01_alice has quit [Server closed connection]
11:01_alice has joined #asahi-dev
11:10skoobasteeve has quit [Server closed connection]
11:10skoobasteeve has joined #asahi-dev
11:14the_lanetly_052 has joined #asahi-dev
11:15pzcz has joined #asahi-dev
11:16pzcz has quit [Remote host closed the connection]
11:34kameks has joined #asahi-dev
11:34robher has quit [Server closed connection]
11:34robher has joined #asahi-dev
11:48KDDLB has quit [Server closed connection]
11:48KDDLB has joined #asahi-dev
11:49WindowPain has quit [Server closed connection]
11:50Skirmisher has quit [Server closed connection]
11:50Skirmisher has joined #asahi-dev
11:51WindowPain has joined #asahi-dev
11:53povik has quit [Server closed connection]
11:53povik has joined #asahi-dev
11:57chadmed has quit [Remote host closed the connection]
11:58subject38[m] has quit [Server closed connection]
11:58subject38[m] has joined #asahi-dev
11:58ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
12:09pfdub[m] has quit [Server closed connection]
12:10pfdub[m] has joined #asahi-dev
12:15os has quit [Server closed connection]
12:15os has joined #asahi-dev
12:19svenalright, rtkit. for nvme that thing is extra awkward because all we need there is boot and shutdown and no more communication after that. that already doesn't fit well with the mailbox API.
12:20svenmarcan knows more details about SMC, but there some parts are handled by the rtkit core (syslog, etc.) while others are handled by the SMC driver. that would be split across mailbox and SMC then. buffers are also mapped as if they are MMIO there and handed out by the co-processor
12:21svenso if we had this inside mailbox we'd have some quirks for probably every single co-processor
12:23marcanmaz: if you want my personal opinion on mailbox, using that subsystem at all was a mistake because it just *sucks*
12:23marcanit is poorly designed, and different drivers interpret its design in different, incompatible ways
12:23marcanbut now we're stuck with it, fine, as a dumb low-level abstraction on top of the raw mailbox hardware
12:24marcanbut trying to use it above RTKit is something we thought of, and decided would be an even worse idea because it clashes even more with the mailbox design
12:24caef^ has quit [Remote host closed the connection]
12:24marcanRTKit is really a higher level interface and needs to deal with things like buffer/memory management too
12:25svenI also briefly looked into remoteproc, but that seemed to to mostly deal with virtio and firmware loading which we both don't have here
12:26the_real_briel[m] has quit [Server closed connection]
12:26the_real_briel[m] has joined #asahi-dev
12:26marcanarnd: our conclusion re: mailbox was that because Apple's coprocessors generally only do one thing, trying to use the mailbox abstraction to provide the multiplexing is just a waste of time
12:27marcanand the existing abstraction does *not* work properly, IIRC due to how it handles queuing, if we try to expose the different endpoints as different channels
12:27marcanthe only copro that does have a ton of interfaces some of which are logically separate is DCP; that one has sub interfaces for dealing with things like DisplayPort hardware and the DP2HDMI etc, besides the main giant dcpep
12:28marcan*but* display controllers are a tightly tied mess already, so I don't see using different drivers for that in linux buying us anything really
12:28marcanit'd just end up being a pile of drivers with a ton of incomprehensible cross-dependencies
12:28marcanmight as well just accept that there's no good way to do it and go monolith; at least it won't be a gpu+display monolith like x86 GPUs
12:29arndis there some more information about the rtkit documented somewhere? I'm probably still missing a few of the fundamental bits
12:30marcanrtkit is just apple's RTOS; we use the name to refer to the shared framework it implements over the mailbox
12:30arndare there multiple instances running the same type of firmware on the chip but with different purposes?
12:30marcane.g. SMC will reuse all of the RTKit stuff as-is from the NVMe submission, but instead builds up a key/value interface over a user endpoint
12:31marcanGFX also will, though I'm dreading having to do more refactoring of mailbox if it ends up being a performance bottleneck there, since there it actually matters
12:31pzcz has joined #asahi-dev
12:31marcanSMC, NVMe, and DCP pretty much cover all the "weird" combinations of memory management for RTKit core endpoints, and all three are already up and running, so the current RTKit module design is already fairly well proven in that regard
12:32pzcz has quit [Remote host closed the connection]
12:32limegorilla[m] has quit [Server closed connection]
12:32limegorilla[m] has joined #asahi-dev
12:33svenjust more horribly because if you lock that processor up or do something wrong the entire SoC will reset *sigh*
12:33marcanthat is the SMC RTKit backend (there's another layer in there because I want the upper level SMC stuff to work on T2 and pre-T2 x86 macs too, which do not use RTKit)
12:34marcan(pre-T2 Macs do some ioport interface for the key/value access, while T2 macs do some ACPI thing)
12:35marcannote: the atomic thing is a special case for sending the final system shutdown/reboot command to SMC, which has to happen in atomic context; this is probably going to be the only consumer of that particular API
12:36marcan(it is not spinlocked properly either, I gave up on that since it doesn't matter for this sole use case and trying to do it properly was too much of a mess)
12:36marcanno, T2 macs use a different thing (they do use RTKit internally but I don't think any of that is exposed)
12:38marcan[gpio/RTC/power_supply/whatever else] > macsmc-* driver > [SMC higher level key-value abstraction] > macsmc > [SMC key-value back-end ops] > macsmc-rtkit > [RTKit endpoint API] > rtkit helper > [mailbox API] > apple-mailbox
12:39marcanmacsmc-* drivers instantiate mfd sub-devices on top of macsmc, using a generic, higher-level key-value API
12:39marcanmacsmc is fairly thin, it mostly provides helpers for reading/writing different key types, enumerating/searching for keys, and does the general mfd registration
12:40marcanmacsmc-rtkit is the actual mfd parent driver, it just initializes RTKit and provides the backend ops and then calls macsmc to actually register the mfd and everything on top
12:41marcanand then in the rtkit case, that also builds on top of the RTKit helper library and talks to the hardware mailbox over the mailbox abstraction
12:41marcanthe upper macsmc-* driver are always probed, but not all SMC instances in different machines would have all those features. they check to see if the relevant keys exist, if they do they probe, otherwise they ENODEV
12:42arndok, got it. I don't think I'll be able to remember all this, but I the bigger picture makes sense
12:42marcanso for example only M1s have GPIOs and handle the RTC through this (and those specific upper drivers have DT bindings which on x86 wouldn't exist), but macsmc-power is configless and I think should instantiate on T2 Macs too to provide nice battery stats there (possibly better than the ACPI ones)
12:45linuxgemini9 has quit [Server closed connection]
12:46marcansince that's specifically battery/charging related (non-laptops do have power stats available, but those belong in hwmon)
12:46linuxgemini9 has joined #asahi-dev
12:46marcanalso tangential, but DCP actually talks to the SMC key-value interface over a backdoor mailbox, all on its own (the copro, not us) :)
12:48marcanone of the design decisions that went into RTKit was punting the specifics of how device addresses are mapped to the upper level driver, because it's just too variable
12:48al3xtjames has quit [Server closed connection]
12:48al3xtjames has joined #asahi-dev
12:48turo has quit [Server closed connection]
12:48turo has joined #asahi-dev
12:48marcanNVMe has that SART whitelist thing, plus the NVMMU which is not used for RTKit, mostly, except for some debug mode commands sven found which IIRC break that model
12:49marcanwhile DCP uses an IOMMU for everything, including its own firmware mapped via the DAPF (which we normally don't even touch from linux), and that adds an offset to virtual addresses
12:49sventhere are some vendor specific commands that all require SART for their buffers because they don't use the common PRPs thing
12:49marcanso we actually have 1 addres space for SMC (physical only), but 3 for DCP (physical, IOVAs that the IOMMU maps, and DVAs used by RTKit/DCP stuff which is IOVA plus an offset in the top bits)
12:50marcanso since the specifics of mapping buffers and translating addresses differ from instance to instance, RTKit punts that to a callback back into the parent driver so it can do whatever it needs to do
12:51marcane.g. the SMC driver just verifies that any addresses SMC gives us are in the expected (whitelisted) SRAM range, then does an ioremap
12:51svendifferent co-processors also need a different way to hibernate them for suspend and/or reset. if you send them to the wrong power state they just won't come up again. and ofc that state differs between most of them
12:51marcanyeah, and also whether the AP or the copro allocates memory varies by copro and specific endpoint
12:52marcanso since there's all this variability we pretty much need a bespoke interface between RTKit and whatever's on top
12:54marcanthere's also the fact that none of this is ever going to be useful outside these tightly coupled apple devices anyway
12:54marcanlike mailbox already did but that's just because it's a crap design, it *could've* been done properly :)
12:55sveneven though you dislike mailbox so much I still think that is the correct place for the low-level HW stuff
12:55marcanI'd fix it but I'd have to talk to everyone already (ab)using it and figure out what we do with that mess
12:56svenfair enough. I think it was find for the very basic single channel thing but I didn't bother with the atomic API there
12:56marcanwhich isn't even properly documented and different drivers/consumers interpret it differently
12:57marcanhonestly the way it does queuing etc is just not a good match for how these mailboxes work on apple
12:57marcanthat could be improved, but again, making sure not to break other consumers is always a pain
12:58svenyeah, the queuing doesn't fit well for the FIFO-backed mailboxes we have. but that could be fixed and IIRC the maintainer comment something like "no need to do this right now unless you have a good reason" back when I made that a better fit for v1
12:58arndmarcan: I completely agree with your description of the problems in the mailbox subsystem, don't have any good ideas for solving them either though
12:59joske has quit [Remote host closed the connection]
12:59arndI'm probably responsible for some of the early mistakes, but fundamentally we had (right from the start) people trying to fit very different hardware concepts into a single API
13:00arndand then some drivers slipped in that completely ignored some of the decisions we had already made for the other drivers
13:00msteffen has quit [Server closed connection]
13:00msteffen has joined #asahi-dev
13:01nametable[m] has quit [Server closed connection]
13:01nametable[m] has joined #asahi-dev
13:01mazmarcan: thanks for the braindump. it'd be good to have some if this rational as part of the cover letter or ML discussion, because IRC really isn't the right medium for that (or anything else IMO... ;-)
13:03snnw[m] has quit [Server closed connection]
13:03snnw[m] has joined #asahi-dev
13:17pzcz has joined #asahi-dev
13:17DarkShadow4444 has quit [Server closed connection]
13:17RevHelix has quit [Server closed connection]
13:17DarkShadow44 has joined #asahi-dev
13:18pzcz has quit [Remote host closed the connection]
13:34joske has joined #asahi-dev
13:39kameks has quit [Ping timeout: 480 seconds]
13:39yuyichao_ has quit [Ping timeout: 480 seconds]
13:48roxfan has quit [Ping timeout: 480 seconds]
13:50sjg1 has quit [Server closed connection]
13:50sjg1 has joined #asahi-dev
14:00yuyichao_ has joined #asahi-dev
14:15Gaelan has quit [Server closed connection]
14:16Gaelan has joined #asahi-dev
14:23joskemarcan: the line with the bind mount (mount --bind "$ROOT" "$ROOT") ends up mounting /dev/nvme0n1p5 on /home/jos/Projects/asahi-alarm-builder/root type ext4
14:25kov has quit [Server closed connection]
14:25kov has joined #asahi-dev
14:30Glanzmann has joined #asahi-dev
14:33XeR has quit [Server closed connection]
14:33XeR has joined #asahi-dev
14:39joskewell in any case this mount step seems not necessary for manjaro, basestrap (their copy of pacstrap) doesn't seem to care about a mountpoint
14:40kenzie35 has quit [Server closed connection]
14:40kenzie35 has joined #asahi-dev
14:46fortelling[m] has quit [Server closed connection]
14:46fortelling[m] has joined #asahi-dev
14:47jakebot has quit [Server closed connection]
14:47jakebot has joined #asahi-dev
14:48kode54 has quit [Server closed connection]
14:48kode54 has joined #asahi-dev
14:48bpye has quit [Server closed connection]
14:48bpye has joined #asahi-dev
14:50irth has quit [Server closed connection]
14:51irth has joined #asahi-dev
15:00nkaretnikov has quit [Server closed connection]
15:00nkaretnikov has joined #asahi-dev
15:04Emantor has quit [Server closed connection]
15:04Emantor has joined #asahi-dev
15:11axboe has quit [Server closed connection]
15:11axboe has joined #asahi-dev
15:14MZG[m] has quit [Server closed connection]
15:14MZG[m] has joined #asahi-dev
15:21nyx_o has quit [Server closed connection]
15:21nyx_o has joined #asahi-dev
15:29balrog has quit [Server closed connection]
15:30balrog has joined #asahi-dev
15:31ExeciN[m] has quit [Server closed connection]
15:31ExeciN[m] has joined #asahi-dev
15:35qiuren[m] has quit [Server closed connection]
15:35qiuren[m] has joined #asahi-dev
15:38MajorBiscuit has quit [Ping timeout: 480 seconds]
15:41roxfan has joined #asahi-dev
15:42trouter has quit [Server closed connection]
15:43trouter has joined #asahi-dev
15:43yrlf has quit [Server closed connection]
15:44yrlf has joined #asahi-dev
15:47Simonx22 has quit [Server closed connection]
15:48Simonx22 has joined #asahi-dev
15:50winter has quit [Server closed connection]
15:50winter has joined #asahi-dev
15:57dumistaken[m] has joined #asahi-dev
16:15ryan_nupp[m] has quit [Server closed connection]
16:16ryan_nupp[m] has joined #asahi-dev
16:21riker77 has quit [Server closed connection]
16:21riker77 has joined #asahi-dev
16:24phiologe has quit [Server closed connection]
16:36Darkmatter66 has left #asahi-dev [#asahi-dev]
17:18AntoniosPapadakis[m] has joined #asahi-dev
17:23c10l2 has joined #asahi-dev
17:29dabaiste^ has joined #asahi-dev
17:30marcan(maz has made us default to _relaxed for everything except where required and now arnd is saying the opposite)
17:31c10l has quit [Ping timeout: 480 seconds]
17:34mazmarcan: we've had that battle for a long time, and I don't think we'll ever agree on that one.
17:36mazmarcan: my point is that barriers are expensive, even on shiny HW like this one, and that *removing* barriers is incredibly hard. it also plays to the mindset of "I don't know what I'm doing, so I'll be adding barriers until it behaves".
17:36mazI'd rather people reason about what they are writing and use the right amount of synchronisation.
17:37maz*documenting* why you use barriers or not is just as important as the barriers themselves (or lack thereof).
17:41alyssa has joined #asahi-dev
17:42Taro[m] has joined #asahi-dev
17:48r0ni has joined #asahi-dev
17:59nicolas17 has joined #asahi-dev
18:21jannauI hope there's not much to fix. apple did claim ultrafusion is transparent to software so I assume Linux will just work ;)
18:30mazjannau: keep us posted! I hope to have my serial adapter ready by the time it lands (specially as I'm foolishly trying to write the firmware is bloody Rust...)
18:38mazalyssa: firmware to drive the FUSB302 that enables the UART and allows me to remotely reboot the box. I already have one on the mini, but need a spare for the Studio. and since I can't get the same parts I used the first time, I'm redoing everything from scratch.
18:48Glanzmannjannau: Yep, that one. When you mentioned that there are updates for macos, I rebooted and searched for updates. None for me. But when you said ultrafusion, slowly I understood.
18:49thasti has quit [Remote host closed the connection]
18:52the_lanetly_052 has quit [Ping timeout: 480 seconds]
18:53thasti has joined #asahi-dev
18:56jannaumaz: second try was a success. I would have been surprised if it is not one of the outer ports on the backside
19:11jannaudisplay init fails and then "assert(irq < 0x1000); // Will probably need updating for multi-die"
19:17m6wiq has joined #asahi-dev
19:37LuigyLeon[m] is now known as luigy[m]
19:40GlanzmannApropos dcp. I just rebased jannaus dcp branch on top of current asahi. If someone wants it: https://tg.st/u/dcp-2022-03-22.tar - all trivial
19:45alyssa(n.b. kernel is currently rebuilding with suspend support. cannot test kernel changes for 30 min until that finishes.)
19:46alyssa(otherwise the whole driver would refuse to load, clearly it does load since that patch works)
19:58learning_ has joined #asahi-dev
19:59learning_ has quit []
20:04mnc7[m] has joined #asahi-dev
20:12j`eyI used initcall_blacklist=apple_pcie_init,apple_pcie_driver_init to stop pcie from being loaded (while testing suspend)
20:13m6wiq has quit []
20:20rucadi[m] has joined #asahi-dev
20:32j`eycurrent dmesg failure with PCIe suspend https://paste.gg/p/anonymous/dec5f8894df84ddbaff7cf3b5c1a619f
20:34kita99 has joined #asahi-dev
20:34m6wiq has joined #asahi-dev
20:36nicolas17me playing around with a DCP wireshark dissector while having a hundred other things to do
20:37PaterTemporalis has quit [Ping timeout: 480 seconds]
20:38zoey has joined #asahi-dev
20:44zoey is now known as Guest48
20:48Guest48 has quit [Quit: Page closed]
20:49jannauit's probably pmgr. clock/power gates have a die id in the most significant nibble. there's just a single pmgr instance which looks identical to a single m1 max
20:54joske has quit [Remote host closed the connection]
20:55alyssaI think this does what we want, but with so many other issues with suspend/resume on these machines it's honestly hard to know
21:00jannaualyssa: looks like a good first step for s2idle. I wonder if macos also suspends dcp via rtkit
21:00alyssathat patch at minimum gets the video to stop ("no signal" on my display) and then come back after
21:16nicolas17idk if this wireshark thing is useful but at least it got my executive functioning un-stuck yesterday
21:24Darktux has joined #asahi-dev
21:29m6wiq has quit []
21:34Darktux has quit [Quit: Konversation terminated!]
21:34Darktux has joined #asahi-dev
21:34Darktux has quit []
21:35kelito has joined #asahi-dev
21:59kelito has quit [Quit: Konversation terminated!]
22:12GlanzmannI see. But since I'm running a bigger resolution right now, I probably already have the answer. :-)
22:23jannauGlanzmann: on the mini vram can fit 5.5 million pixels, would be good for 3440x1600 or 3840x1433 at 32bpp
22:36Candygoblen123[m] has joined #asahi-dev
23:03kelito has joined #asahi-dev
23:09kelito has quit [Remote host closed the connection]
23:30efegurkan[m] has joined #asahi-dev
23:37pzcz has joined #asahi-dev
23:38pzcz has quit [Remote host closed the connection]
23:40badlydrawnface[m] has joined #asahi-dev
23:46AntoniosPapadakis[m]I'm interested in helping out the Asahi Linux development in my free time. I obviously have some hardware that I can use to test. Where should I start? Thank you all.