#
…

2022-02-28

00:10bluetail[m] has joined #asahi-dev
00:58therealminzii[m] has joined #asahi-dev
01:09nepeat has quit [Server closed connection]
01:09nepeat has joined #asahi-dev
01:32royal1 has joined #asahi-dev
01:44Graypup_ has quit [Server closed connection]
01:44Graypup_ has joined #asahi-dev
01:56royal1 has quit [Ping timeout: 480 seconds]
02:34x56 has quit [Server closed connection]
02:35x56 has joined #asahi-dev
03:12alyssa has joined #asahi-dev
03:30skipwich has quit [Server closed connection]
03:30skipwich has joined #asahi-dev
03:37PhilippvK has joined #asahi-dev
03:40phiologe has quit [Ping timeout: 480 seconds]
03:50kov has quit [Quit: Coyote finally caught me]
06:30marcan(or both)
07:24kettenisprobably both
08:54akemin_dayo has quit [Ping timeout: 480 seconds]
08:55MajorBiscuit has joined #asahi-dev
08:55svenlooks like apple has an "instance" property in their ADT on the atcphy which is either 0 or 1 on t8103 and which, among other things, decides which fuses to use to tweak some registers
09:56the_lanetly_052 has joined #asahi-dev
10:00kettenisbut you can just have the node for the atphy reference the right nvmem cells isn't it?
10:04svennvmem cells already support bits = <start len>; so we can just have a single cell referencing the same fuse multiple times
10:05svenand afaict that's even enough to support t6000 with the same code
10:05svenerm.. *multiple cells referencing the same fuse
10:05svenjust with a different mask essentially
10:28Nspace has quit []
10:28bisko has quit [Read error: Connection reset by peer]
10:28Nspace has joined #asahi-dev
10:29bisko has joined #asahi-dev
10:38akemin_dayo has joined #asahi-dev
10:54c10l4 has joined #asahi-dev
10:55c10l4 is now known as c10l
11:32kloenk has quit [Remote host closed the connection]
11:39kloenk has joined #asahi-dev
12:44tanty has quit []
12:58tanty has joined #asahi-dev
13:28eragon has joined #asahi-dev
13:34svenurgh.. one of the t8103 phys needs a slightly different fuse sequence with two more fuse values while all the others (i.e. the other t8103 and all four t6000) need the same sequence :/
13:54marcansven: check for the extra fuses and decide that way?
13:55svenoh... true. that should work
13:55marcando we know what the fuses do? (reg names for these?)
13:55sventhe names are a bit weird sometimes, but they all seem to be related to clocks / PLLs
13:55bisko has quit [Read error: Connection reset by peer]
13:56marcanI wonder why the extra fuses...
13:56bisko has joined #asahi-dev
13:57marcananyway, we probably shouldn't have too high hopes of cross-compat for these phys, and robher doesn't really like having millions of generic DT names, so for this one it might make sense to just call it apple,t8103-atcphy
13:57marcanand the t6000 one could be apple,t6000-atcphy, apple,t8103-atcphy
13:57marcansince in this case it is compatible
13:58marcan(we do know they move the fuses around, so it's good we have the whole nvmem mechanism for that)
13:58svenstill need to map the names to the actual registers but it seems to first set one value, then setup another value, and finally updates the first value again
13:58svenwhile the others only need to set that first value ones. or something like that.
13:58svenit's still just rough notes here :D
13:58marcanheh, fair
13:59j`eysven: which t8103 needs more fuses?
13:59sventhe registers for t8103 and t6000 are actually the same, the target values just come from different offsets inside that fuse region
13:59svenpossibly because t6000 has four sets instead of two now
13:59svenj`ey: atc-phy1 i tihnk
13:59sven*think
13:59marcanapple moved the fuses around for pcie too, I think the fusemap isn't stable
14:00svenmakes sense
14:00ketteniswithout the phy driver, the ports still work as usb2 ports, so it isn't a complete disaster
14:00sveni guess you checked that pcie really only has a single fuseset?
14:00robherphys are pretty tied to process nodes and therefore change in almost every soc.
14:00j`eysven: ohh, I misunderstood that as one of the t8103 models (aka air, pro, mini etc), not one of the mulitple phys in the t8103
14:01marcanI'm not expecting all this stuff to magically work on future SoCs; I'm mostly betting on being able to get to the point where linux-asahi is today (except audio)
14:01svenj`ey: yeah, it's always atc-phy1 on all t8103 models
14:01marcanwhich has enough stuff for a distro install to go smoothly, and then you can upgrade to some HwE kernel
14:03marcansven: the pcie fuses are global for all of APCIe, not per-port
14:03sjg1kettenis: Re the boot scripts, if you have time to review the bootstd stuff, it would help
14:03marcanI expect there will be separate fuses for the two storage APCIe instances, but ANS2 deals with that
14:03svenok. just double checking because corellium also pretends that atcphy only has a single set of fuses fwiw
14:03marcan>corellium
14:04svenyes. the original pcie bringup was based on that
14:04kettenissjg1: I guess I really should try that series on my machines
14:04sventhat's why i'm asking.
14:04kettenissjg1: but marcan and jannau here have some fearious plans to use the bootscripts to pair u-boot to a specific ESP
14:04marcanbut nah, the pokes are into global PHY regs
14:04marcannot per-port regs
14:04marcanand there's a single APCIe instance
14:05marcanthis also fits the silicon
14:05marcanAPCIe is one block, with multiple SERDESes
14:05marcanwhile each ATCPHY is a separate block
14:05svenI guess there will be a second set for the thunderbolt pcie controller then
14:05marcanof fuses?
14:05marcanthere shouldn't be, that has no PHY
14:05marcanit should all be behind ATCPHY
14:06marcanit's not a PCIe PHY
14:06svenwell... the ADT has the fuses region as an entry in the thunderbolt pcie nodes
14:06svencould be wrong since the ADT often is ofc
14:07marcanit could be there's separate fuses for thunderbolt per se
14:07marcanbut it should be completely unrelated to the normal PCIe PHY fuses
14:08svencould be. something to figure out once someone gets into the mess that will be thunderbolt
14:08marcanor it could just be dummy too, if they share code with normal apcie
14:09marcansven: wait I don't see the fuses entry in apciec0
14:10marcanI see it in atc
14:10marcanand apcie
14:10marcannot apciec
14:10svenahhh....
14:10marcanso that makes sense
14:10svenit's in my 11.x ADT but apparently was removed in 12.x
14:10marcanso probably garbage copypasta from apcie then
14:11_jannau_kettenis, sjg1: we have no constraints adding a preferred boot partition UUID to bootstd either. I'm hoping adding it to bootstd will be less hacky than with the boot scripts
14:11marcanI'm guessing for apciec we can reuse the same driver, just have a different compatible since we probably need to skip some low level code
14:11marcanbut the higher level interface should be similar
14:12svenyeah, the more scary part is the rest required for thunderbolt :D
14:12marcanwell, get USB3 working first, that's a start :p
14:12marcanalso DisplayPort would be nice :>
14:26svenDP may just start to work "by accident" if that other DCP just works . XNU always applies USB3 tunables for one "lane" and DP tunables for the other
14:26svenbut let's see what happens
14:33royal1 has joined #asahi-dev
14:40yuyichao has quit [Ping timeout: 480 seconds]
14:50marcansven: there's a DP mux too
14:50marcanthe DCPs aren't mapped 1:1 to ATCs
14:50svenah, true
14:50marcan(pro has 2:4, max has 4:4 but still muxed)
14:50marcanthere's also this cute little "stream codec" input to the mux
14:50svenis that part of ATC or a separate node?
14:50marcanwhich is, apparently, what they call prores0 (and only prores0! not 1!)
14:50marcanit's a separate node
14:50kettenismarcan is that "stream codec" audio?
14:51marcanprores is video
14:51marcanso apparently prores0 has the ability to, somehow, bypass DCP and stream directly to displayport
14:51marcanlet's just say I have some idea what sekrit apple project that might be related to...
14:51svenhm. oh well. let me get usb3 up first then and someone else can care about DP if it's not very obvious afterwards :D
14:52svensounds like something that could be used for DRM as well if prores can also do decryption
14:52marcanprores doesn't really make any sense as a DRMed codec though
14:53* svenis just guessing without any context here :)
14:53kettenismarcan: I looked a bit closer at the wifi firmware stuff for OpenBSD
14:53kettenisone issue with the current tar file is that it uses symlinks
14:53marcansven: I mean, you know, low latency high quality codec bypassing the display pipe? what would you need such tight latency for?
14:53kettenisthe OpenBSD kernel does deliberately not follow symlinks when loading firmware
14:54svenoh.. some VR/AR stuff?
14:54kettenisthe other issue is that the brcm subdirectory doesn't match what we currently do for the broadcom wifi firmware
14:54marcanI mean the internet can't stop talking about apple's VR project lately so... :p
14:55marcankettenis: the manifest can be used to copy stuff around if symlinks won't work
14:56kettenisone thought I had was to have the Asahi Installer repackage the firmware into an OpenBSD-compatible firmware package
14:56kettenisI think the manifest contains enough information to do that
14:56kettenis(and obviously I would contribute that code)
14:59the_lanetly_052__ has joined #asahi-dev
15:00yuyichao has joined #asahi-dev
15:05the_lanetly_052 has quit [Ping timeout: 480 seconds]
16:32marcankettenis: it would be a bit tricky because we'd either always have to have multiple formats (wasteful) or we'd need different "generic UEFI" options, one for Linux variants and one for OpenBSD variants
16:32marcanideally I'd prefer it if we settle on some standard, and then the OS itself does whatever transform it needs to do to put it into its preferred structure
16:33marcanis it hard to do that transform once OpenBSD loads the tarball? I figured you could just untar it, rename the directory or whatever, and resolve symlinks
16:37kettenisdiscussing some options with Theo
16:37ketteniscurrently looking at selectively extracting files from the archive such that we can use them early on in the installer
16:38kettenisbut that is where the symlinks complicate things
16:39kettenisI see why you chose symlinks; it makes things more explicit
16:40kettenisbut would using hard links instead work for what you have in mind?
16:49marcanhm, in a tarball?
16:50marcanI guess that's a thing, need to check to see how to make that from python
16:50marcanlinux won't care either way
16:50kettenisyes, I think you use LNKTYPE instead of SYMTYPE
16:51tpw_rulesyeah, that's exactly how you do it
16:51marcansure, why not
16:54marcankettenis: feel free to test it and send a PR if it works for you
17:06royal1 has quit [Ping timeout: 480 seconds]
17:22svenmarcan: so... chances are I can already blindly support this T8112 phy as well :D
17:22svenlooks like the fuses are essentially the same again and just the "port reset" maybe works a bit different
17:24sven... or maybe this can't do a port reset anymore? but either way, it mostly uses t8103 functions except for essentially those two
17:25svenah, t6000 actually already doesn't have that port reset thing anymore apparently. so, uh, t8112 phy is more or less the same i guess
17:31alyssasven: sounds like you're having fun
17:32svenjust enjoying myself until the usb curse will inevitably strike again while writing this driver! ;)
17:32alyssait hasn't yet?
17:32svennot yet
17:33svenBut usb3 also isn’t working yet so there’s plenty of time
17:44bluetail[m]is it possible to create a live-stick so that we can test if we should? I have a odd setup of 7 usb disks which are fed by a active hub and going into one usb 3 port.
17:58svenit’ll be a few more weeks before there’s something to test
17:58alyssasven: hf
17:59bluetail[m]to anybody already running AsahiLinux: Is there power management? Does it always run on 100%? How is the power consumption? I know, no concerns in early stages, but I'm curious if there is such finding which requires us to build a new cpu governor.
18:00j`eybluetail[m]: #asahi is the channel for questions like that
18:01bluetail[m]ok. I will repeat there.
18:11MajorBiscuit has quit [Ping timeout: 480 seconds]
19:37the_lanetly_052__ has quit [Ping timeout: 480 seconds]
21:25thebigbossch[m] has joined #asahi-dev
21:35ketteniscool, the last patch for t6000 support is now in u-boot master as well
21:35kettenisI rebased the u-boot asahi branch once more even though it doesn't really make a difference
23:40erincandescent has joined #asahi-dev
…