#
…

2023-04-28

00:11brolin has quit [Ping timeout: 480 seconds]
00:15Guest12331 has quit []
00:15vx has joined #asahi
00:16vx is now known as Guest12368
00:19martinr1 has quit [Ping timeout: 480 seconds]
00:23martinr1 has joined #asahi
00:27Zopolis4_ has quit []
00:30jamespmo_ has joined #asahi
00:32martinr1 has quit [Ping timeout: 480 seconds]
00:37jamespmorgan has quit [Ping timeout: 480 seconds]
00:42julio7359 has joined #asahi
00:46brolin has joined #asahi
00:58martinr1 has joined #asahi
01:03possiblemeatball has joined #asahi
01:06martinr1 has quit [Ping timeout: 480 seconds]
01:09Brainium has quit [Quit: Konversation terminated!]
01:30martinr1 has joined #asahi
01:33julio7359 has quit [Ping timeout: 480 seconds]
01:38martinr1 has quit [Ping timeout: 480 seconds]
01:48elvishjerricco has joined #asahi
01:54elvishjerricco has quit [Read error: Connection reset by peer]
01:55brolin has quit [Ping timeout: 480 seconds]
01:56brolin has joined #asahi
01:57julio7359 has joined #asahi
02:00gabuscus has quit []
02:04martinr1 has joined #asahi
02:08elvishjerricco has joined #asahi
02:12martinr1 has quit [Ping timeout: 480 seconds]
02:12elvishjerricco has quit [Read error: Connection reset by peer]
02:14elvishjerricco has joined #asahi
02:17gabuscus has joined #asahi
02:17elvishjerricco has quit [Read error: Connection reset by peer]
02:17elvishjerricco has joined #asahi
02:23elvishjerricco has quit [Read error: Connection reset by peer]
02:31rvalue has joined #asahi
02:31_rudi1 is now known as _rudi
02:32elvishjerricco has joined #asahi
02:36julio7359 has quit [Ping timeout: 480 seconds]
02:38martinr1 has joined #asahi
02:46martinr1 has quit [Ping timeout: 480 seconds]
02:52brolin has quit [Ping timeout: 480 seconds]
03:00elvishjerricco has quit [Read error: Connection reset by peer]
03:04julio7359 has joined #asahi
03:07brolin has joined #asahi
03:09elvishjerricco has joined #asahi
03:12martinr1 has joined #asahi
03:12elvishjerricco has quit [Read error: Connection reset by peer]
03:15elvishjerricco has joined #asahi
03:20martinr1 has quit [Ping timeout: 480 seconds]
03:44martinr1 has joined #asahi
03:51marvin24_ has joined #asahi
03:52martinr1 has quit [Ping timeout: 480 seconds]
03:54marvin24 has quit [Ping timeout: 480 seconds]
03:56possiblemeatball has quit [Quit: Quit]
03:57brolin has quit [Ping timeout: 480 seconds]
04:17martinr1 has joined #asahi
04:25martinr1 has quit [Ping timeout: 480 seconds]
04:47Tolik2000 has joined #asahi
04:47Tolik2000 has quit [Remote host closed the connection]
04:48martinr1 has joined #asahi
04:56martinr1 has quit [Ping timeout: 480 seconds]
04:59Tolik2000 has joined #asahi
04:59Tolik2000Hello everybody
04:59Tolik2000How protected the hardware is? I mostly mean pstate and power domain stuff, and also SPI flash chip with boot data. Can we play around safely with what is enabled in DT? Is there some protection that only allows access to the NVRAM partition, blocking access to other parts of the NOR chip? Also, can it be harmful if cpu or gpu pstate data is modified in DT? We weren't able to determine where those were used for. Can DT mods be used to over/under-clock/vo
05:00Tolik2000Is /dev/mtd0 the nvram partition, or the whole chip?
05:01Tolik2000By power domain stuff I mean both bad power curves and pstates as well as sequencing and other stuff with turning it on off
05:02Tolik2000I heard SMC manages power, throttle etc. But then why do we have to use those power curves and fp math for GPU?
05:02martinr1 has joined #asahi
05:02marcanTolik2000: yes, only the nvram partition is exposed in the DT
05:02marcanCPU pstate data is informative only, it is not used by the driver
05:03Tolik2000It means /dev/mtd0 doesn't contain other data like iboot config stuff?
05:04marcanGPU pstate data is passed to the firmware but it is unclear whether that actually sets the voltage/frequency or is only used for power estimation and pstate control
05:04marcanso "we don't know, mess with it at your own risk"
05:04Tolik2000So the cpu opp-microvolt and opp-microwatt is to calculate estimated power for, e.g. EAS to work? Got it
05:04greguu has joined #asahi
05:05marcanCPU pstates shouldn't even have those properties right now?
05:05Tolik2000Maybe only in experimental eas branches?
05:05marcanthough we will add at least microwatt for EAS
05:05marcanmicrovolt isn't even constant
05:05marcanvoltages are calibrated per-device
05:05marcanthe GPU data is replaced with ADT data in m1n1
05:06Zopolis4_ has joined #asahi
05:06marcanso the values in the template DT don't even matter
05:06marcan(just the OPP count)
05:06Tolik2000Got it, thanks
05:07Tolik2000And common PD stuff should be safe to turn on/off since critical stuff is on direct SMC control? I mean for kernel infrastructure and driver testing / experimenting
05:08marcanwe've screwed things up like that in the past (also clobbering all GPIO registers) and nobody has destroyed any hardware yet
05:08marcanworst case the thing just locks up or reboots
05:08Tolik2000Well, I know some ways of rebooting easily. ACIO is my faw
05:08Tolik2000C* fav lol
05:08marcanI'd be more worried about the GPU stuff since it's a ton of tables and we just don't know how critical it is (lina has been very careful to get the data the same as macOS or almost)
05:09marcanbut outside of that yeah, I don't think you can break anything
05:09marcanSMC has a watchdog, if you crash it it reboots your machine within 30 seconds
05:09Tolik2000It's runtime computed from ADT props?
05:09marcanyes, and leakage fuses and other stuff
05:09marcanit's complicated
05:09marcanand the power estimates aren't 1:1 with macOS but it's close enough
05:09marcan(and the formulas macOS uses there don't seem to be very well behaved either)
05:10Tolik2000Great job!
05:10marcanbut there's other tables and stuff unrelated to that max power estimate thing which is basically 1:1 identical to macOS as far as I know
05:10marcanwithin 1 LSB tolerance
05:10Tolik2000I've seen the broken curve on one of the Lina's streams
05:10marcanyeah that one's a WTF
05:10marcantells me that one estimate doesn't really matter :p
05:11marcanbut some of the other stuff might, nobody knows what half of those numbers do
05:11marcanso best get it the same as macos
05:11Tolik2000Glad to know that this hw is not only mighty, but also rock solid, at least while speakers an
05:11Tolik2000*are muted
05:11marcantbh considering how pstates are handled for everything else by init in iBoot and locked as far as I know, I actually expect the GPU to be the same
05:11marcanso you probably can't actually overclock/overvolt it by messing with those tables either
05:11marcanand it's probably just for fancypants power estimates in the firmware
05:12marcanbut that's just a guess
05:12Tolik2000I believe speakersafetyd is first in class thing not tied to android?
05:12marcanandroid stuff is typically done in firmware anyway, at least partially
05:12marcanthough I've seen some of the code that shuttles IV data between the DSP firmware and the hardware in android
05:12marcan(when I was researching this stuff)
05:12martinr1 has quit [Ping timeout: 480 seconds]
05:13Tolik2000Well, GPU driver is to be trusted for those configs, it gets 100x the robustness thanks to Rust, so should make initdata decent anyway
05:14Tolik2000Okay, thanks for the great explanation of these cool machines!
05:14marcanI plan to help set up a CI at some point for this
05:14marcanshould get lina to write an initdata comparison test for it
05:14marcanthen we can automatically test that kernel versions keep correct initdata across all supported firmware/device combinations
05:15Tolik2000Just unit test? Or integration on hardware?
05:15marcanactual hardware
05:15marcanlike have known good macOS initdata dumps, run the linux kernel on the hypervisor, dump initdata and compare
05:16marcanI need to figure out if I'm repurposing some of the machines I have or buying dedicated CI machines :p
05:16marcanwill come along with some major home server revamp I have planned for the next few months
05:17Tolik2000Your security and robustness principles are as good to be taught to any teamlead
05:17marcanlast thing I want is to destroy users' hardware
05:18Tolik2000Yeah. I remember some macos update required DFUing machines which had had their main board replaced. What was QA doing lol
05:19marcanoh we actually have that problem
05:19marcanthe 12.3 we ship by default on M1 series is that version
05:19marcanbut since it's only a OS install, you don't need DFU to fix it
05:19marcanI have 12.3.1 in expert mode for the like 2-3 users who have hit this
05:19Tolik2000But DFU path helps a lot since MacBook can be flashed without special tooling
05:19marcannever bothered to promote it to default because we'll probably switch to 13.3 soon for everything
05:20Tolik2000Have they broke system-wide or only asahi is unbootable?
05:20marcanit's just the asahi os firmware so it just bootloops after the first reboot on install, but you can just let it eventually give up and it'll go into recovery
05:21Tolik2000How would 13.3 help older devices? Less maintenance burden, or some nice bug fixes?
05:21marcannewer features probably, alyssa wants some GPU stuff she thinks needs newer firmware
05:21Tolik2000What was the problem? iBoot bug?
05:21marcanre gpu, unclear yet which is why I probably won't ship 13.3 coincident with the M2 Pro/Max release for older devices
05:21marcanbut eventually it should be supported across the board
05:22Tolik2000M2X is planned right after you get time to add WiFi/BT support?
05:22marcanthere's also the risk that apple actually stops hosting old IPSWs for some reason which would really suck, or that they stop signing older OSes for security reasons
05:23marcanso it's best not to get stuck on one firmware version for older devices even if we don't strictly need to upgrade
05:23marcanno reason to upgrade frequently but every now and then, yeah
05:23Tolik2000Cool job on M2X, they're mostly ready in a month after you got time to work in that direction
05:24marcanyeah, it's usually about a month of actual time for new devices, sometimes less
05:24Tolik2000Well, and they likely fix bugs in GPU/DCP as well
05:24marcanthe Mac Minis are still a problem but I hope sven and jannau figure out the display stuff
05:24Tolik2000And at that moment other external displays should be available as well?
05:25marcanI mean no display works on the new Minis
05:25marcanbecause of the change in the primary display controller
05:25marcanso we'll release M2X for laptops only at first unless that gets fixed really soon
05:26Tolik2000 Laptops have main DCP unmuxed, thus impossible to reroute to thunderbolt?
05:26marcanbut it'll be available in expert mode for people who want to use them as headless servers and don't mind hacking around the boot process to work around not having an obvious console
05:26marcanthe hardware should support muxing, but iBoot initializes it and it's unclear whether DCP firmware allows re-routing, and either way it means our existing code works
05:26marcanit's just that isn't initialized on the new desktops
05:27marcanand it's even still unclear whether we can even init that with the iBoot protocol any more, or whether we need to go and implement full DCP in m1n1
05:27marcanwhich would kinda suck
05:27marcanbut we'll find out when that gets fixed on the Linux driver and we try to backport it to m1n1
05:28marcancrossing my fingers that in the end we only need to implement one or two EPIC/AFK endpoints and not the main dcpep
05:31Tolik2000Any chances basic m1 and m2 could reuse their dcp as a dcpext?
05:31Tolik2000Like using 2 screens in clamshell mode
05:31Tolik2000Or dcp internal doesn't have displayport encoder?
05:33Tolik2000 has quit [Remote host closed the connection]
05:34marcanm1, not as far as I know
05:34marcanm2 if the firmware supports itr
05:34marcanas far as we know m1 does not have the main DCP crossbared into the other ports
05:35marcanbut that still depends on the main DCP firmware being happy with the concept of having its internal screen replaced with an external port at runtime
05:35marcanpersonally I wouldn't consider it viable until macOS implements it
05:35marcansince if that works at all, not having it be a codepath tested in macOS is a sure fire way for explosions and bugs
05:35marcanDCP does a *lot* more things for internal panels so switching between that and ext mode is a major firmware state change
05:36Tolik2000 has joined #asahi
05:36Tolik2000What can go wrong?
05:36jamespmorgan has joined #asahi
05:36marcanI mean it does things like handle the backlight, including brokering storing backlight staging data (on some eeprom I think, I don't think the OS is involved)
05:36Tolik2000Like persistent harm or so
05:37marcanI'm worried about screwing up the persistent backlight aging stuff on the 14"/16" machines since that could cause aging effects over very long periods of time that are impossible to test
05:37marcananyway, we'll see
05:38martinr1 has joined #asahi
05:38Tolik2000MiniLED has some housekeeping inside the DCP?
05:38Tolik2000Yes, then better follow macOS way
05:38jannauI don't have high hopes for dptx + dcp_iboot on m2/m2 pro minis as long as apple doesn't init displays in iboot for the desktop systems
05:39Tolik2000But currently it should be fine, no time it asks OS to save stash data? All done inside DCP itself.
05:41jamespmo_ has quit [Ping timeout: 480 seconds]
05:41mexpr has quit [Remote host closed the connection]
05:41Tolik2000I mean is enabling dcp beneficial on M1 Pro or M2 Pro 14"? It should manage backlight properly at the current driver state? Does it also fully match traces under HV?
05:42mexpr has joined #asahi
05:44marcanyes, I'm not aware of the OS being involved and it wouldn't make sense since you can have multiple macOS installs
05:45marcanbut it does complain if you pause it for too long under the HV (both macOS and Linux)
05:45sjg has quit [Read error: Connection reset by peer]
05:45msteffen has quit [Read error: Connection reset by peer]
05:45loops has quit [Read error: Connection reset by peer]
05:45Illya has quit [Read error: Connection reset by peer]
05:45sjg has joined #asahi
05:45Nezteb has quit [Read error: Connection reset by peer]
05:45pipppero has quit [Read error: Connection reset by peer]
05:45risk has quit [Read error: Connection reset by peer]
05:45jbowen has quit [Write error: connection closed]
05:45Nezteb has joined #asahi
05:45pipppero has joined #asahi
05:45msteffen has joined #asahi
05:45loops has joined #asahi
05:45joshtaylor has quit [Read error: Connection reset by peer]
05:45risk has joined #asahi
05:45joshtaylor has joined #asahi
05:45Illya has joined #asahi
05:45jbowen has joined #asahi
05:45marcanactually on startup too, so it's possible this isn't being handled properly for non-dcp framebuffer mode in current non edge kernels
05:45Tolik2000I like how these machines are smart even though they don't have SMM firmware on the main cpu
05:45marcanbut DCP is going to be promoted to default real soon now anyway
05:46martinr1 has quit [Ping timeout: 480 seconds]
05:47Tolik2000SMC basically prevents any power/heat damage etc. DCP abstracts so much stuff inside. Great thing they're generous on those small AArch64 coprocessors
05:47Tolik2000What does complain? DCP oslog or so?
05:48Tolik2000What kind of interaction it needs from OS? Swaps? Should be buggy, but still fine on x11?
05:50marcandcp syslog
05:51marcanand I'm actually not sure, might just be callbacks? I don't remember those warnings under x11...
05:51marcanyou wouldn't expect absence of swaps to cause that
05:52Tolik2000Alright. So basically checks if kernel acks callbacks maybe
05:52marcanso maybe it just gets stuck sending random callbacks to the OS and if callback processing stops that stalls the backlight housekeeping
05:52julio7359 has quit [Ping timeout: 480 seconds]
05:54Tolik2000Nice thing it complains if caused to glitch. No way to miss erroneous behavior
05:54Tolik2000 has quit [Remote host closed the connection]
05:55jannauI don't remember seeing random dcp callbacks when tracing X11 but I would expect it to complain if you stopped the AP in an ongoing swap
05:59cylm_ has joined #asahi
06:09svenmarcan: i have no Mac Mini with the typec hdmi mess display, that’s all on jannau :>
06:10martinr1 has joined #asahi
06:13jannauif type-c/atc weren't such a mess we could start with dp-altmode support
06:16jannau13.3 (maybe earlier and I missed it) changes the dptx interface in an incompatible way. there's a DPTX_APCALL_GET_MAX_LANE_COUNT inserted before get_active_lane_count
06:18martinr1 has quit [Ping timeout: 480 seconds]
06:18jannauif that is already in 13.2 it would explain dptx not working in m1n1 on the m2 mini
06:25Tolik2000 has joined #asahi
06:26Tolik2000Oh, another question from the perspective of hw stuff. Is SMART data reported with smartctl preserved after DFU wipe and restore?
06:27Tolik2000It's interesting where the internal use region of the NVMe controller resides. Is it in one of the flash chips, or on-die within the SoC?
06:28Tolik2000I've seen some videos of people repairing M1 ssd with iPhone NAND chips, but no smartctl data in those
06:32Tolik2000I do think somebody has DFUed machines frequently for installer tests
06:33Tolik2000would be interesting to know how SMART changes during restore cycle
06:34Tolik2000it __is__ able of repairing NVMe service zone (or writing it from scratch into an empty supported NAND chip), but shouldn't wipe it while doing restore. Sure it doesn't touch that on revive
06:42martinr1 has joined #asahi
06:48tinstew has joined #asahi
06:48steven has quit [Quit: ZNC 1.8.2 - https://znc.in]
06:49steven has joined #asahi
06:51martinr1 has quit [Ping timeout: 480 seconds]
06:51Tolik2000 has quit [Quit: Page closed]
07:15rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
07:15Guest12357 has quit [Quit: Bridge terminating on SIGTERM]
07:18Jamie has joined #asahi
07:18rhysmdnz has joined #asahi
07:18Jamie is now known as Guest12394
07:18martinr1 has joined #asahi
07:24cylm_ has quit [Ping timeout: 480 seconds]
07:26martinr1 has quit [Ping timeout: 480 seconds]
07:30martinr1 has joined #asahi
07:40giskard has joined #asahi
07:40martinr1 has quit [Ping timeout: 480 seconds]
08:00martinr1 has joined #asahi
08:04marvin24 has joined #asahi
08:05guillaume_g has joined #asahi
08:06drubrkletern has quit [Remote host closed the connection]
08:07marvin24_ has quit [Ping timeout: 480 seconds]
08:09bps has joined #asahi
08:30martinr1 has quit [Ping timeout: 480 seconds]
08:35Zopolis4_ has quit []
08:37nsklaus has joined #asahi
08:52martinr1 has joined #asahi
09:00mattgirv has quit [Ping timeout: 480 seconds]
09:08martinr1 has quit [Ping timeout: 480 seconds]
09:10martinr1 has joined #asahi
09:17tsujpis it possible to start krfb from the commandline? trying to connect via tigervnc wont work (prompts for a password but no password I enter works)
09:17tsujpI have set a password in ~/.config/krfbrc
10:01tinstew has quit [Ping timeout: 480 seconds]
10:03hightower3 has joined #asahi
10:09hightower2 has quit [Ping timeout: 480 seconds]
10:10tinstew has joined #asahi
10:22tinstew has quit [Ping timeout: 480 seconds]
10:27tsujpIs it possible to do armhf on asahi currently?
10:28chadmedno the cores do not implement A32
10:28tsujpI assume my only chance at simulating a 32bit environment is to use something like FEX-emu then?
10:29j`eyqemu if you want 32-bit arm
10:38tsujpHow does one change the page size of the kernel currently? Lina did a change to get it to 4K but I don't know what she did
10:39j`eyyou have to rebuild the kernel
10:40jannauand you will lose PCIe devices (wlan, bt, sd card reader, usb-a ports, ethernet) until proper 4k support is ready
10:41jannauyou can use a vm with 4k kernel though
10:57maz has quit [Ping timeout: 480 seconds]
11:29gordonfreeman has joined #asahi
11:31gordonfreeman has quit [Remote host closed the connection]
11:56VinDuv has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
11:56VinDuv has joined #asahi
12:07cafebabe has quit [Quit: Connection closed for inactivity]
12:11possiblemeatball has joined #asahi
12:22tinstew has joined #asahi
12:42roxfan2 has joined #asahi
12:43roxfan has quit [Ping timeout: 480 seconds]
12:43maz has joined #asahi
13:04bps2 has joined #asahi
13:10bps has quit [Ping timeout: 480 seconds]
13:20abd has joined #asahi
13:20Agua has joined #asahi
13:36eroux has quit [Quit: Textual IRC Client: www.textualapp.com]
14:03Luj has quit [Quit: Ping timeout (120 seconds)]
14:03Luj has joined #asahi
14:08gladiac has joined #asahi
14:36unicordian has joined #asahi
14:45guillaume_g has quit []
15:00bps2 has quit [Ping timeout: 480 seconds]
15:12marcanTolik2000: no idea whether SMART data survives DFU restore but there is no mutable nonvolatile memory within the SoC (or any other modern SoC, the process does not allow it). the data must be in the NAND chips.
15:26cylm_ has joined #asahi
15:27tinstew has quit [Ping timeout: 480 seconds]
15:32balrog has quit [Quit: Bye]
15:34jbowen has quit []
15:34jbowen has joined #asahi
15:37patwid has joined #asahi
15:38balrog has joined #asahi
15:39tinstew has joined #asahi
15:39patwidi have difficulty finding info whether hdmi audio works on the mac mini m1?
15:39gordonfreeman has joined #asahi
15:40patwidhave been searching on the official wiki feature support page and via google in general
15:41ChaosPrincessit doesnt, but there are wip patches for that
15:41_jannau_it is under development, works but is not integrated
15:42patwidthank you for claryfing!
16:15gladiac has quit [Quit: k thx bye]
16:26Agua has quit [Ping timeout: 480 seconds]
16:34leahcl has quit [Remote host closed the connection]
16:35leahcl has joined #asahi
16:54unicordian has quit [Read error: Connection reset by peer]
16:55unicordian has joined #asahi
16:59crabbedhaloablut has quit []
17:01crabbedhaloablut has joined #asahi
17:03Agua has joined #asahi
17:28pthariensflame has joined #asahi
17:33pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
17:58brolin has joined #asahi
18:00Brainium has joined #asahi
18:18jadesoturi has quit [Ping timeout: 480 seconds]
18:20jadesoturi has joined #asahi
18:26gordonfreeman has quit [Remote host closed the connection]
18:42Agua has quit [Remote host closed the connection]
18:56unicordian has quit [Ping timeout: 480 seconds]
18:56unicordian has joined #asahi
19:17tinstew has quit [Ping timeout: 480 seconds]
19:25mspe has quit [Quit: WeeChat 3.0]
19:25mspe has joined #asahi
19:28brolin has quit [Ping timeout: 480 seconds]
19:29tinstew has joined #asahi
19:30brolin has joined #asahi
19:33unicordian has quit [Ping timeout: 480 seconds]
19:33unicordian has joined #asahi
19:39brolin has quit [Ping timeout: 480 seconds]
19:40brolin has joined #asahi
20:01brolin has quit [Ping timeout: 480 seconds]
20:08unicordian has quit [Read error: Connection reset by peer]
20:10unicordian has joined #asahi
20:12roxfan has joined #asahi
20:15roxfan2 has quit [Ping timeout: 480 seconds]
20:29bcrumb has joined #asahi
20:36abd has quit [Ping timeout: 480 seconds]
20:37bcrumb has quit [Quit: WeeChat 3.8]
20:37unicordian has quit [Ping timeout: 480 seconds]
20:37unicordian has joined #asahi
20:56unicordian has quit [Read error: Connection reset by peer]
20:57unicordian has joined #asahi
21:09abd has joined #asahi
21:23tinstew has quit [Ping timeout: 480 seconds]
21:34brolin has joined #asahi
21:47possiblemeatball has quit [Quit: Quit]
21:49unicordian has quit [Ping timeout: 480 seconds]
21:51unicordian has joined #asahi
21:55cylm_ has quit [Ping timeout: 480 seconds]
21:58unicordian has quit [Read error: Connection reset by peer]
21:59unicordian has joined #asahi
22:11unicordian has quit [Ping timeout: 480 seconds]
22:11unicordian has joined #asahi
22:17bcrumb has joined #asahi
22:17bcrumb has quit []
22:44julio7359 has joined #asahi
22:49unicordian has quit [Ping timeout: 480 seconds]
22:49unicordian has joined #asahi
22:58julio7359 has quit [Remote host closed the connection]
23:53martinr1 has quit [Ping timeout: 480 seconds]
…