millenialhacker has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
as400_ has joined #asahi-dev
as400 has quit [Remote host closed the connection]
as400_ is now known as as400
<chadmed>
amarioguy: at least you didnt lead a maintainer on a wild goose chase over an ignored compiler warning :P
<chadmed>
in fairness, the function that was _actually_ failing because of it was doing so silently
<amarioguy>
chadmed: oof must've been rough
<amarioguy>
probably more for offtopic but dealing with FIQ timers with software (EDK2) that is clearly assuming a GIC controlled timer is pain...
<chadmed>
viresh was nice about it but my god i felt like an idiot
<chadmed>
at least EAS will work for us on 6.2 so its still a win
<amarioguy>
nice :)
<chadmed>
i wouldnt enable it until the GPU driver lands in asahi though since it absolutely slaughters sw rast performance
<chadmed>
probably both because our power values are wildly inaccurate and the added latency of swapping the render threads across clusters constantly to minmax for J/inst
<chadmed>
hard to A/B test with sw rendering too since its always going to wake up pcores to render stuff, but the clusters do seem to stay in lower pstates for longer now
as400_ has joined #asahi-dev
as400 has quit [Ping timeout: 480 seconds]
as400_ is now known as as400
millenialhacker has quit [Ping timeout: 480 seconds]
as400 has quit [Ping timeout: 480 seconds]
as400 has joined #asahi-dev
as400 has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
as400 has joined #asahi-dev
as400 has quit [Ping timeout: 480 seconds]
as400 has joined #asahi-dev
as400_ has joined #asahi-dev
as400 has quit [Remote host closed the connection]
as400_ is now known as as400
bpye has quit [Ping timeout: 480 seconds]
<marcan>
amarioguy: just send your patch first; it's already been tested and mine could hypothetically introduce regressions on other platforms (though I doubt it)
<marcan>
(considering I wrote it to the PASemi datasheet)
<marcan>
no rush to send both in
<marcan>
and yeah, just have the increased timeout in your patch, no need for authorship credit for that part
<marcan>
I'll send the whole error recovery thing later
Dcow has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
bpye has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
as400 has quit [Ping timeout: 480 seconds]
as400 has joined #asahi-dev
as400 has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
as400 has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
as400 has quit [Ping timeout: 480 seconds]
SSJ_GZ has joined #asahi-dev
as400 has joined #asahi-dev
millenialhacker has joined #asahi-dev
as400 has quit [Ping timeout: 480 seconds]
ccs1 has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
as400 has joined #asahi-dev
as400_ has joined #asahi-dev
as400 has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
Dcow has joined #asahi-dev
as400_ is now known as as400
millenialhacker has quit [Ping timeout: 480 seconds]
Dcow_ has joined #asahi-dev
Dcow has quit [Ping timeout: 480 seconds]
<jannau>
sigh. I do not understand how the brightness mapping is supposed to work. The backlight node in the ADT gives the following
<jannau>
two tables which give a linear index to brightness translation (one for 0 - 100 nits, the other one for 100 - 510 nits) milliAmps2DACTablePart1, milliAmps2DACTablePart2. brightness values as reported back by dcp
as400_ has joined #asahi-dev
as400 has quit [Remote host closed the connection]
<jannau>
in addition I have milliAmps2DACPart1MaxCurrent and milliAmps2DACPart2MaxCurrent and coefficients for a quadratic polynomial to convert nits to mAmps (nits2mAmps*OrderCoef)
<jannau>
the polynomial seems to expect normalized nits from 0 to 1 + x
as400_ is now known as as400
<jannau>
if I solve the polynomial for milliAmps2DACPart1MaxCurrent and milliAmps2DACPart2MaxCurrent I get conflicting results
<jannau>
0.1945 for milliAmps2DACPart1MaxCurrent means at the reported brightness of 99 nits a normalization by 514 nits
<jannau>
0.124 for milliAmps2DACPart2MaxCurrent means at the reported brightness of 510 nits a normalization by ~410 nits
ccs1 has quit [Ping timeout: 480 seconds]
<mps>
interesting. that means it is analog light control and not pwm, iiuc
<jannau>
if the ADT is not a lie. I find it a little suspicious that the tables and constants are the same over all devices
dottedmag has joined #asahi-dev
as400_ has joined #asahi-dev
as400 has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
as400_ is now known as as400
millenialhacker has quit [Ping timeout: 480 seconds]
r0ni has quit [Quit: Leaving]
cylm has joined #asahi-dev
as400_ has joined #asahi-dev
as400 has quit [Remote host closed the connection]
<sven>
3840x2160@60.00 with HBR2 works as well :>
as400_ is now known as as400
<jannau>
nice. can you test if it works with HBR3 and 2 lanes as well?
<sven>
I don't think I have a display that negotiates that mode
<sven>
but I'm cleaning up the mess a bit right now so that I can push it later
<sven>
sometimes I have to do modetest -M apple to get something to appear when I connect via this usb3/dp hub. but i have a feeling that this hub is a bit broken anyway
<sven>
I sometimes also only get a high-speed device when I connect it via this hub. not sure if that's an atcphy issue or just a broken hub though
sleber has joined #asahi-dev
<jannau>
dcp initialization might a little bit flaky too. I had a single occurance of some weirdness which was solved by turning the display off and on. unfortunately I didn't had time to investigate and now I've even forgotten what the issue was
* amarioguy
has sent v4 to mailing lists
* amarioguy
turns to SEP now
blazra has joined #asahi-dev
<sven>
yeah, it's probably gonna be a while before this is stable enough
<jannau>
it's ontop of an older dcp branch + commits to add dcpext/dcpext0/4. should rebase ontop of the current asahi-wip without too much conflicts (hopefully)
lachlan has joined #asahi-dev
lachlan has quit []
lachiefish has joined #asahi-dev
bgb has quit [Ping timeout: 480 seconds]
bgb has joined #asahi-dev
<sleber>
y<x ssqf
<lachiefish>
yes?
lewurm has joined #asahi-dev
<sven>
alright, now that jannau has volunteered to fix all the bugs I introduced to dcp (:P) let's see if I can bring up thunderbolt
millenialhacker has joined #asahi-dev
<jannau>
rebases cleanly except for the conflicting solutions for the uninitialized values in tipd's interrupt handlers
lewurm has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
<jannau>
sven: dptxep.h is missing
lewurm has joined #asahi-dev
<sven>
uh, let me fix that
<sven>
pushed
millenialhacker has quit [Ping timeout: 480 seconds]
bgb_ has joined #asahi-dev
bgb has quit [Ping timeout: 480 seconds]
<sven>
urgh… I know why usb3 in usb3/DP mode sometimes fails
<sven>
if the tps chip takes just a bit too long to recognize the altmode dwc3 is already up when it tries to reconfigure the lanes
<sven>
and the SS phy really doesn’t like that *sigh*
sleber has quit [Remote host closed the connection]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
ljs has joined #asahi-dev
<sven>
jannau: fwiw, another know race is during probe time: if drm probes after tipd it won’t get the first oob hotplug event
<sven>
also, lol, this display doesn’t work at all under macOS with one of my cables but it does work just fine in linux :D
<sven>
i bet that’s another hdcp fail
Cyrinux has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
ljs has quit [Quit: ERC 5.4 (IRC client for GNU Emacs 28.2)]
ljs has joined #asahi-dev
ljs has left #asahi-dev [#asahi-dev]
<jannau>
sven: no luck so far here with actually getting a picture out of dcptext
<sven>
:(
<sven>
t8103?
<jannau>
on dcpext side everything looks ok but the displays complain about a migging signal
<jannau>
yes
<sven>
huh
<jannau>
s/migging/missing/
<sven>
I only got that when dcpext couldn’t actually set the mode
<sven>
just to be sure, connected to atcphy1?
<sven>
i don’t think 0 makes a difference but I never tested it
<jannau>
yes, but I see one possible problem now: apple-dcp 271c00000.dcp: unexpected busy command channel
<sven>
and I guess you also tried to run modetest?
<sven>
huh
<sven>
don’t think I ever got that
<jannau>
are "DPTXPort: unhandled call" for 11, 13, 14, 20, 22 expected?
<sven>
yes
ljs has joined #asahi-dev
<sven>
Huh, not 22 though
<sven>
22 is “device busy timeout”
<sven>
so the most stable thing to prevent any races for me is to boot with nothing plugged in, then just plug in the typec->hdmi adapter and then finally plug in the display
ljs has left #asahi-dev [ERC 5.4 (IRC client for GNU Emacs 28.2)]
<jannau>
let me try that. I'm testing with an usb-c dp adapter and an usb-c display