2022-06-30
00:07crabbedhaloablut has joined #asahi-dev
00:15loki_val has quit [Ping timeout: 480 seconds]
00:23amarioguy has joined #asahi-dev
00:23pseigo_ has joined #asahi-dev
00:26deh^ has quit [Ping timeout: 480 seconds]
01:29RevHelix has quit [Quit: No Ping reply in 180 seconds.]
01:30RevHelix has joined #asahi-dev
01:36millenialhacker has joined #asahi-dev
01:37RevHelix has quit [Quit: No Ping reply in 180 seconds.]
01:38RevHelix has joined #asahi-dev
01:44millenialhacker has quit [Ping timeout: 480 seconds]
02:11pseigo_ has quit []
02:11pseigo_ has joined #asahi-dev
02:14phiologe has joined #asahi-dev
02:17PhilippvK has quit [Ping timeout: 480 seconds]
02:46pseigo_ has quit []
02:46pseigo_ has joined #asahi-dev
02:55bisko has quit [Read error: Connection reset by peer]
02:59millenialhacker has joined #asahi-dev
03:06pseigo_ has quit []
03:07pseigo_ has joined #asahi-dev
03:07millenialhacker has quit [Ping timeout: 480 seconds]
03:24pseigo_ has quit [Ping timeout: 480 seconds]
03:29nicolas17 has quit [Quit: Konversation terminated!]
03:49kov has quit [Quit: Coyote finally caught me]
04:04millenialhacker has joined #asahi-dev
04:12millenialhacker has quit [Ping timeout: 480 seconds]
04:21pseigo_ has joined #asahi-dev
04:43amarioguy has quit [Ping timeout: 480 seconds]
04:59pseigo_ has quit [Ping timeout: 480 seconds]
05:03deh^ has joined #asahi-dev
05:05the_lanetly_052 has joined #asahi-dev
05:05millenialhacker has joined #asahi-dev
05:13millenialhacker has quit [Ping timeout: 480 seconds]
05:41loki_val has joined #asahi-dev
05:45loki_val_ has joined #asahi-dev
05:49crabbedhaloablut has quit [Ping timeout: 480 seconds]
05:53loki_val has quit [Ping timeout: 480 seconds]
05:58chadmed has quit [Quit: Konversation terminated!]
06:07millenialhacker has joined #asahi-dev
06:11deh^ has quit [Ping timeout: 480 seconds]
06:15deh^ has joined #asahi-dev
06:15millenialhacker has quit [Ping timeout: 480 seconds]
06:18jluthra has quit [Remote host closed the connection]
06:18jluthra has joined #asahi-dev
06:29deh^ has quit [Ping timeout: 480 seconds]
06:29MajorBiscuit has joined #asahi-dev
06:40deh^ has joined #asahi-dev
06:52Catyre_ has quit [Ping timeout: 480 seconds]
06:57chadmed has joined #asahi-dev
07:00millenialhacker has joined #asahi-dev
07:00deh^ has quit [Ping timeout: 480 seconds]
07:08millenialhacker has quit [Ping timeout: 480 seconds]
07:14Catyre has joined #asahi-dev
07:45millenialhacker has joined #asahi-dev
07:53millenialhacker has quit [Ping timeout: 480 seconds]
08:02kettenis has joined #asahi-dev
08:04pseigo_ has joined #asahi-dev
08:16bisko has joined #asahi-dev
08:26bisko has quit [Ping timeout: 480 seconds]
08:36millenialhacker has joined #asahi-dev
08:44millenialhacker has quit [Ping timeout: 480 seconds]
09:05DarkShadow44 has quit [Quit: ZNC - https://znc.in]
09:06DarkShadow44 has joined #asahi-dev
09:17c10l49 has quit []
09:18bisko has joined #asahi-dev
09:18c10l49 has joined #asahi-dev
09:18c10l49 has quit []
09:18c10l49 has joined #asahi-dev
09:21bisko has quit [Read error: No route to host]
09:24millenialhacker has joined #asahi-dev
09:25bisko has joined #asahi-dev
09:25bisko has quit []
09:32millenialhacker has quit [Ping timeout: 480 seconds]
09:38bisko has joined #asahi-dev
09:38the_lanetly_052__ has joined #asahi-dev
09:45the_lanetly_052 has quit [Ping timeout: 480 seconds]
09:46bisko has quit [Ping timeout: 480 seconds]
09:48pseigo_ has quit [Ping timeout: 480 seconds]
09:55marcan(and the aic1 binding apparently goes back quite a few Axx generations, folks backported Linux to some much older chips and the driver only needed trivial changes that can be autodetected)
09:56marcanalmost everything in M2 is directly compatible, or wildly new drivers in a few cases. the one annoying case I found so far is cpufreq (not upstream yet), which had to add a bit to the pstate counts, which was fine for the main switching register but shifted a field in the feedback register I'd discovered and started using.
09:57marcanthat one is nice to have so cpufreq can report the accurate *current* frequency, capped by hardware limits, not just what the kernel asked for.
09:58marcanmy current idea for that one is have a generic compatible that doesn't use that register (which is still very much a usable result), and then use the per-SoC compatibles to enable it knowing the bit count.
09:58marcanfor future SoCs that remain compatible (as far as we can tell) then we'd end up with something like "apple,tFOO-soc-cpufreq", "apple,t8112-soc-cpufreq", "apple,soc-cpufreq", if that works for you?
09:58millenialhacker has joined #asahi-dev
09:59marcan(with the driver only binding to apple,t8112-soc-cpufreq and apple,soc-cpufreq unless in the future we find something special to do for tFOO)
10:01marcanI might cap the "generic" compatible mode to 16 pstates or so, just to be safe, so in that case older kernels wouldn't reach the highest CPU p-states (which is still a usable state, we do expect people to upgrade kernels to seriously use new machines, I just want the things to be able to boot if at all possible)
10:03marcancurrent M2/t8112 status is that, if PCIe doesn't have any surprises (it's missing bootloader enablement still, haven't tested it), and if we'd done t8110-DART ahead of time (which we didn't, but was needed for M1 Pro/Max too, we just didn't get to it in time), M2 would've booted unmodified kernels with missing keyboard/mouse, RTC, and poweroff support (new hardware for those)
10:04marcanthis is very much a usable state of affairs for a distro installer if you can plug in an external keyboard, so I consider that a success story for my theory that we can support upcoming SoCs in old kernels with just bootloader/DT changes "enough to install a distro and upgrade to a hardware enablement kernel"
10:05_jannau_did you test the watchdog? reset in u-boot did not work for me (once) on M2. I have not looked at it at all
10:05marcanI remember something being broken there, yeah. reset did not work for me initially but did later, in the hypervisor?
10:06marcanalso, another funny thing I noticed: sleep in macOS does *not* kill the hypervisor now (not: the HV has always hijacked the CPU sleep mode stuff to stop them from disabling IRQs/etc)
10:07c10l49 has quit []
10:07marcannot sure if that means it's s2idle type stuff, or if the final sleep trigger would be the boot CPU going into low power mode and we just aren't doing that
10:07millenialhacker has quit [Ping timeout: 480 seconds]
10:08c10l49 has joined #asahi-dev
10:08marcanbut this is good for working out how sleep/wake works, especially if I can figure out how to trigger a wake signal in a way that macOS likes, without breaking the HV
10:12bisko has joined #asahi-dev
11:03jannaukettenis: t8112 bringup for u-boot: https://github.com/jannau/u-boot-1/tree/t8112/bringup
11:16millenialhacker has joined #asahi-dev
11:18ketteniss/has/have/ there, but maybe you want to rewrite that message anyway when we sigure that one out
11:24millenialhacker has quit [Ping timeout: 480 seconds]
11:29millenialhacker has joined #asahi-dev
11:29kettenis has quit [Read error: Connection reset by peer]
11:35kettenis has joined #asahi-dev
11:44millenialhacker has quit [Ping timeout: 480 seconds]
11:55pjakobsson has joined #asahi-dev
12:00deh^ has joined #asahi-dev
12:02millenialhacker has joined #asahi-dev
12:15millenialhacker has quit [Ping timeout: 480 seconds]
12:16deh^ has quit [Ping timeout: 480 seconds]
12:25deh^ has joined #asahi-dev
12:30millenialhacker has joined #asahi-dev
12:38millenialhacker has quit [Ping timeout: 480 seconds]
12:40deh^ has quit [Ping timeout: 480 seconds]
12:50deh^ has joined #asahi-dev
13:20marcandid you see my earlier comments on the new keyboard/touchpad story? TL;DR there is now a coprocessor involved, with the usual interface, but that interface isn't used for the actual data - there is another interface for that, which is logically independent. So far we've treated the coprocessors as an integral part of the device they manage, but in this case it really behaves more like a "helper".
13:21marcanso we have the coprocessor (which just needs to come up), the interface (which is a dumb byte FIFO - is there any subsystem binding / consumer type stuff that would fit here?), and then some kind of HID device binding on top. but that same FIFO hardware type is used as a special debug UART too (we just haven't implemented it yet), so it should also have a tty consumer driver. and in that case ...
13:22marcanlogically, I would say the coprocessor is one device, the FIFO is another device, and the HID mapping is a direct consumer (child node?) of the FIFO and a device link to the coprocessor so it can depend on it being up
13:23marcanso far we've only had one other device where the copro was *mostly* logically detached from the real device node, NVMe - in that case we ended up with a single device node for both, while that could've been modeled as separate devices. but that separate device abstraction is slightly leaky in the case of some debug commands at least, so there is some argument that a combined device is a good idea ...
13:24marcanI'm not so sure that's the case here, it really does sound like we should use separate devices to model this new keyboard/trackpad coprocessor and the associated FIFO interface / HID protocol.
13:25marcanone thing I thought of is having the coprocessor driver as a genpd, which feels a bit weird to say, but does provide the semantics we'd want ("this needs to be on before the consumer device") - I'll have to look at how it handles power management (can the copro turn off while the user isn't touching anything to save power and still get an IRQ? how would that work?) to see whether this actually ...
13:28marcanin every other case of coprocessors so far (display controller, GPU, power metrics controller, SMC, camera though that one's even more special, and I think the neural engine too) the main coprocessor interface/mailbox and protocol stack is the main communication mechanism, so I think what we're doing with the single node is correct and we should keep doing it.
13:36deh^ has quit [Ping timeout: 480 seconds]
13:36millenialhacker has joined #asahi-dev
13:51kov has joined #asahi-dev
13:52millenialhacker has quit [Ping timeout: 480 seconds]
14:05deh^ has joined #asahi-dev
14:13amarioguy has joined #asahi-dev
14:13marcanfor modules you need to define the other deps separately in the Makefile, otherwise they become separate modules
14:21psykose has quit [Remote host closed the connection]
14:21ptrc has joined #asahi-dev
14:22psykose has joined #asahi-dev
14:26deh^ has quit [Remote host closed the connection]
14:39nsklaus_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:51balrog_ has quit []
14:52balrog has joined #asahi-dev
15:36Catyre_ has joined #asahi-dev
15:42Catyre has quit [Ping timeout: 480 seconds]
15:49Catyre_ has quit [Remote host closed the connection]
15:56millenialhacker has joined #asahi-dev
16:04millenialhacker has quit [Ping timeout: 480 seconds]
16:14Catyre has joined #asahi-dev
16:25pseigo_ has joined #asahi-dev
16:27amarioguy has quit [Ping timeout: 480 seconds]
16:28yamii has quit [Quit: WeeChat 3.5]
16:29Catyre has quit [Remote host closed the connection]
16:36Catyre has joined #asahi-dev
16:39amarioguy has joined #asahi-dev
16:41millenialhacker has joined #asahi-dev
16:53millenialhacker has quit [Ping timeout: 480 seconds]
16:53MajorBiscuit has quit [Quit: WeeChat 3.5]
16:55Catyre has quit [Remote host closed the connection]
16:58pseigo_ has quit [Read error: No route to host]
16:58pseigo_ has joined #asahi-dev
17:02pythonen[m] has joined #asahi-dev
17:03nsklaus has joined #asahi-dev
17:04marcanhm, still doesn't work with apple-dart as a module, it claims to initialize fine but nothing can use the iommu properly
17:10marcanwas hoping to test some images but I'm punting until tomorrow, need to figure out what's going on here
17:16millenialhacker has joined #asahi-dev
17:19Catyre has joined #asahi-dev
17:25millenialhacker has quit [Ping timeout: 480 seconds]
17:27Catyre has quit [Ping timeout: 480 seconds]
17:31Catyre has joined #asahi-dev
17:34the_lanetly_052__ has quit [Ping timeout: 480 seconds]
17:39Catyre has quit [Ping timeout: 480 seconds]
17:55millenialhacker has joined #asahi-dev
18:01sven[ 2.272353] nvme-apple 27bcc0000.nvme: ANS did not boot <-- okay, how did that break now :<
18:13millenialhacker has quit [Ping timeout: 480 seconds]
18:27Catyre has joined #asahi-dev
18:27marcanokay, dart thing is fixed, linux-asahi package pushed. that has jannau's DART series plus fixes, lid switch regression fix, t8112 cpufreq support & related t600x DT change (mostly to make sure I didn't break it)
18:27marcanplease give it a smoke test, if it's not broken I want to make test installer images tomorrow
18:35Catyre has quit [Ping timeout: 480 seconds]
18:58kloenkWhich branch should I look at, so see how the RTKit adapter works? Just want to look at it, and see how hard it would be to write in rust
19:01millenialhacker has joined #asahi-dev
19:09millenialhacker has quit [Ping timeout: 480 seconds]
19:15kloenkSaw some bitmaps. They will be a bit to implement IIRC. And exporting it to C is not really possible yet. But should be manageable, maybe even quite automatic and I just have to write the header for now
19:18kloenkAFK right now. Will look again when back. Could be that I remember wrong and that was a different file
19:28kloenkThis one is the line I'm not sure how complicated it will be: "DECLARE_BITMAP(endpoints, APPLE_RTKIT_MAX_ENDPOINTS);"
19:36svenalso, looks like i broke the driver during this cleanup in more than one way. now it can scan again but refuses to pair new devices :(
19:38kloenk"APPLE_RTKIT_MGMT_EPMAP"and "APPLE_RTKIT_MGMT_EPMAP_REPLY" have the same value, is that intentional?
19:39kloenksame with "APPLE_RTKIT_MGMT_SET_AP_PWR_STATE" (rust can't have that in enums, so can only define it once)
19:41kloenkOkay, will have to see how to do it best. Could do const, but enum has a bit nicer syntax IMHO
19:42svenj`ey: it doesn't help that half the time I just don't know if it's the usual bluetooth flakiness or an actual bug in the driver :D
19:44kloenkI could do a enum with an anonymous struct. one u8 for the value of it, and one bool if its's reply or not
19:45Catyre has joined #asahi-dev
19:46Catyre has quit [Remote host closed the connection]
19:46Catyre has joined #asahi-dev
20:01Catyre has quit [Remote host closed the connection]
20:02Catyre has joined #asahi-dev
20:07millenialhacker has joined #asahi-dev
20:10Catyre has quit [Ping timeout: 480 seconds]
20:14Catyre has joined #asahi-dev
20:22millenialhacker has quit [Ping timeout: 480 seconds]
20:32svenlol, i was wondering why the music was pretty glitch-y and only then realized that I had all my debug spam and the tracer on :D
20:49joske has joined #asahi-dev
20:50joskeI built the new asahi branch (and u-boot and m1n1), and all seems fine, although I'm not sure the build was correct, uname says 5.18.0-asahi-dirty, shouldn't this say 5.18.7?
20:54Bastian[m]bluetooth mouse/keyboard?
20:56svenj`ey: fwiw, I’m waiting for robin to finish his iommu_set_bus cleanup and then I’ll get back to it
21:07joske has quit [Read error: Connection reset by peer]
21:11millenialhacker has joined #asahi-dev
21:20millenialhacker has quit [Ping timeout: 480 seconds]
21:35gladiac has quit [Quit: k thx bye]
21:53pseigo_ has quit [Ping timeout: 480 seconds]
21:55Catyre_ has joined #asahi-dev
22:01Catyre has quit [Ping timeout: 480 seconds]
22:01pseigo_ has joined #asahi-dev
22:02jannauI don't think there's a problem with watchdog. reset through the watchdog seems to disable the HW uart routing
22:28Catyre has joined #asahi-dev
22:35Catyre_ has quit [Ping timeout: 480 seconds]
22:54Redecorating[m]sven: I think this one should have 4377 https://github.com/Dunedan/mbp-2016-linux/blob/master/MacBookPro15%2C4/acpidump
23:15Catyre_ has joined #asahi-dev
23:21Catyre has quit [Ping timeout: 480 seconds]
23:22Catyre has joined #asahi-dev
23:24pseigo_ has quit [Ping timeout: 480 seconds]
23:28Catyre_ has quit [Ping timeout: 480 seconds]
23:34millenialhacker has joined #asahi-dev
23:42millenialhacker has quit [Ping timeout: 480 seconds]
23:58pseigo_ has joined #asahi-dev