#
…

2025-11-12

00:04chadmed has quit [Quit: Konversation terminated!]
00:06chadmed has joined #asahi-re
00:06chadmed has quit []
00:06chadmed has joined #asahi-re
02:01chadmed has quit [Quit: Konversation terminated!]
02:01chadmed has joined #asahi-re
02:03hightower2 has joined #asahi-re
02:09hightower4 has quit [Ping timeout: 480 seconds]
05:32mattia013 has quit [Quit: mattia013]
05:32mattia013 has joined #asahi-re
06:22pb17 has quit [Ping timeout: 480 seconds]
06:28pb17 has joined #asahi-re
06:34seb_ has quit [Quit: Konversation terminated!]
06:36chadmed has quit [Quit: Konversation terminated!]
06:36chadmed has joined #asahi-re
07:43glem81005488994086988613 has joined #asahi-re
07:49glem8100548899408698861 has quit [Ping timeout: 480 seconds]
07:49glem81005488994086988613 is now known as glem8100548899408698861
08:05seb_ has joined #asahi-re
08:23jtingiris has quit [Quit: ZNC 1.9.1 - https://znc.in]
08:23jtingiris has joined #asahi-re
08:31ircfaggotsh has quit [Quit: Bridge terminating on SIGTERM]
08:31auscyber_ has quit [Quit: Bridge terminating on SIGTERM]
08:31appservice-irc[m] has quit [Quit: Bridge terminating on SIGTERM]
08:49seb_ has quit [Quit: Konversation terminated!]
09:20seb_ has joined #asahi-re
10:53runxiyu has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
10:54runxiyu has joined #asahi-re
11:04pb17 has quit [Ping timeout: 480 seconds]
11:08pb17 has joined #asahi-re
11:43runxiyu has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
11:46runxiyu has joined #asahi-re
11:46runxiyu has quit [Remote host closed the connection]
11:47runxiyu has joined #asahi-re
11:48nnym has quit [Ping timeout: 480 seconds]
11:51nnym has joined #asahi-re
11:52Administrator has joined #asahi-re
14:43donutsinbelly has joined #asahi-re
14:50seb_ has quit [Quit: Konversation terminated!]
14:51donutsinbelly has quit [Quit: Textual IRC Client: www.textualapp.com]
14:51donutsinbelly has joined #asahi-re
14:54donutsinbelly has quit []
15:14john-cabaj has joined #asahi-re
15:15john-cabaj has quit [Remote host closed the connection]
15:23seb_ has joined #asahi-re
15:26john-cabaj has joined #asahi-re
16:02chadmed has quit [Quit: Konversation terminated!]
16:03chadmed has joined #asahi-re
16:03bgb has joined #asahi-re
16:30seb_ has quit [Quit: Konversation terminated!]
17:10seb_ has joined #asahi-re
17:25mattia013 has quit [Remote host closed the connection]
17:27mattia013 has joined #asahi-re
18:55pb17 has quit [Ping timeout: 480 seconds]
18:58pb17 has joined #asahi-re
19:00opticron has quit [Read error: Connection reset by peer]
19:00opticron has joined #asahi-re
19:11bgb has quit [Remote host closed the connection]
19:11bgb has joined #asahi-re
21:23graphine27 has joined #asahi-re
21:28graphine27nickchan: do you know if it would be possible for M1 chips to make the ANS controller available over PCIe like T2?
21:30graphine27From what I've seen CreatePCIeUPDARTMapping is one of the functions used and it's present in M1 kexts as well. But some other things are missing from dt like mapper-pup-ans2 or apcieup-fn-nub-ans2
21:30chaos_princessis m1 capable of being a pcie endpoint? devices are usually either root or endpoint, i haven't seen many that can flip to either
21:31graphine27I was hoping this would be possible sice T2 can do it, but chances are pretty low.
21:34chaos_princessdifferent silicon, so doesn't make much sense to leave it there. If you accept "custom drivers on host" - then should be possible, can even expose it over usb3, since m1 is capable of role switching on usb.
21:35graphine27In the first NVMe patch I read this about T2: disable some quirks (the NVMMU and the weird submission array) and then exposes it over a PCIe interface.
21:36graphine27I'm guessing the quircks also can't be disabled on M1
21:36chaos_princessi may be misremembering, but i think you could on m1, but no longer can on m2+ or m1pro+
21:37chaos_princessis there a specific reason why you want it?
21:37graphine27Trying to enable the hardware on a different platform where the driver framework is not as flexible as linux
21:38graphine27Being able to use NVMe in the standard way would make things much easier
21:38chaos_princessoh, so it is not about exposing it via thunderbolt to external host, but to internal sw
21:39chaos_princessthen yea, ignore everything i said before
21:40graphine27Yes. Although I suspect T2 could have done it over thunderbolt, like when using the target disk mode you could see the ssd name
21:41chaos_princessw.r.t your thing, can you synthesize a fake pcie bus by trapping it with the hypverisor? in theory, you only need to trap config registers, and then expose the real nvme mmio as BARs
21:41glem8100548899408698861 has quit [Ping timeout: 480 seconds]
21:44graphine27It would be an option yes, but I was interested if the T2 way would work for bare metal functionality
21:45chaos_princessi'd put it as "not impossible" at least on m1. maybe blindly poke the mmio areas using t2 as reference and see what happens?
21:46graphine27I will try to trace what T2 does, if m1n1 can work correctly when booted via pongo I should be able to fully trace it
21:52nicolas17 has joined #asahi-re
22:30graphine27 has quit [Quit: Page closed]
23:48seb__ has joined #asahi-re
23:50seb_ has quit [Ping timeout: 480 seconds]
23:57glem81005488994086988613 has joined #asahi-re
…