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]
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:04svennvmem cells already support bits = <start len>; so we can just have a single cell referencing the same fuse multiple times
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:55bisko has quit [Read error: Connection reset by peer]
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: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:59sventhe registers for t8103 and t6000 are actually the same, the target values just come from different offsets inside that fuse region
14:00ketteniswithout the phy driver, the ports still work as usb2 ports, so it isn't a complete disaster
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:01marcanwhich has enough stuff for a distro install to go smoothly, and then you can upgrade to some HwE kernel
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:04kettenissjg1: but marcan and jannau here have some fearious plans to use the bootscripts to pair u-boot to a specific ESP
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: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:33royal1 has joined #asahi-dev
14:40yuyichao has quit [Ping timeout: 480 seconds]
14:51marcanso apparently prores0 has the ability to, somehow, bypass DCP and stream directly to displayport
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:53marcansven: I mean, you know, low latency high quality codec bypassing the display pipe? what would you need such tight latency for?
14:54kettenisthe other issue is that the brcm subdirectory doesn't match what we currently do for the broadcom wifi firmware
14:56kettenisone thought I had was to have the Asahi Installer repackage the firmware into an OpenBSD-compatible firmware package
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:37ketteniscurrently looking at selectively extracting files from the archive such that we can use them early on in the installer
17:06royal1 has quit [Ping timeout: 480 seconds]
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:32svenjust enjoying myself until the usb curse will inevitably strike again while writing this driver! ;)
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: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: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:35kettenisI rebased the u-boot asahi branch once more even though it doesn't really make a difference
23:40erincandescent has joined #asahi-dev