14:40 KitsuWhooa: Does the i2c implementation (over DP at least) on the 6900XT not retry on failure?
14:40 KitsuWhooa: I control a (presumably buggy) monitor via ddcutil, and perhaps 9/10 times I get rc=EREMOTEIO(-121): Remote I/O error
14:41 KitsuWhooa: On my RX580, most of the time it'd work (but it'd take longer before ddcutil returned)
16:43 glehmann: markeo: agd5f: not sure if you are the right people to ping for this, but it looks like amd has removed all pre gfx8 documentation from their websites
16:45 glehmann: all the old links lead to https://www.amd.com/en/developer.html not, which only links gpuopen. and gpuopen only has gfx8+ isa docs
16:46 glehmann: this also means there no public register reference anymore, since the last version was for gfx7
19:29 haasn: uh-oh https://0x1.st/fj.txt
20:31 motogangsters: https://github.com/victronenergy/venus/issues/536 those things are above my comprehension, they have some system for controlling 3-30 cell batteries, i have no clue how they manage to do that, but kernel really seems to get the info with wrapping up the buses.
20:32 motogangsters: Some dutch company victron energy
20:33 haasn: dmesg error seems to be gone after reboot
20:33 haasn: seems some mismatch between drivers and kernel
20:34 haasn: shrug
20:59 motogangsters: Tapping on the buses likely, something that logic analyser would do, but those do it somehow on beaglebone and rasbperry, so as it was an embedded controller
21:00 motogangsters: seems like something i have been looking for to revive batteries, but i have idea how to use this yet, how is that even possible dunno
21:33 Venemo: motogangsters: this channel is for discussion of radeon gpu drivers, you may have better luck asking about those things some place else