ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
<mps>
marcan: I see list of merges in last minutes in asahi-wip branch. do you plan to make tagged tarball soon
<marcan>
maybe tomorrow
<mps>
aha, ok. could wait till it
<marcan>
are you in a rush? :p
<mps>
marcan: no, just wanted to test last merges
<mps>
i can build with git archive commit id if I'm in rush
<ChaosPrincess>
while im still poking at touchbar digitizer, any recommendations on what experiments to perform to figure out remaining bits.
<jannau>
marcan: can you send me the incomplete runtime pm patches. I'm working on the component changes and wanted to see if I can get module unload and reload to work
<mps>
at least it boots fine on m1pro macbook
<mps>
I see two new files in /sys/class/power_supply/macsmc-battery, charge_control_start_threshold and charge_control_end_threshold
<mps>
oh and capacity_level
bcrumb has joined #asahi-dev
bcrumb has quit []
nicolas17 has joined #asahi-dev
bcrumb has joined #asahi-dev
<nicolas17>
marcan: "pushed the DCP 10-bit fix + switch to native colorspace (also for 8bit) to bits/200-dcp" what is that about? was it in the wrong colorspace before? did it only affect DCP?
bcrumb has quit []
bcrumb has joined #asahi-dev
bcrumb has quit []
bcrumb has joined #asahi-dev
WindowPa- has joined #asahi-dev
WindowPain has quit [Ping timeout: 480 seconds]
<jannau>
dcp only, nothing has changed except that DCP now reportes {A,X}RGB2101010 as supported. It wasn't previously because it was obvioulsly broken
<nicolas17>
pre-DCP it *seemed* like red color was too saturated compared to my non-Mac monitors, but I don't have an objective comparison
amarioguy has quit [Remote host closed the connection]
bluetail8 has joined #asahi-dev
amarioguy has joined #asahi-dev
yuyichao has joined #asahi-dev
yuyichao_ has quit [Ping timeout: 480 seconds]
SSJ_GZ has quit [Ping timeout: 480 seconds]
<jannau>
marcan: I've just re-read the problem description I'm trying to solve with components and in it self they won't solve the problem
<jannau>
the probe functions are just registering the componennts and exit quickly. not sure how/when the devices are actually bound
<jannau>
it would make sense that it happens when the last missing component is registered. so that would be still be called from some probe function
yrlf has quit []
yrlf has joined #asahi-dev
<jannau>
yes, that's of course what happens so it should fix that issue and avoids deferred probing and device links
<jannau>
but it doesn't solve the problem. the problem is that dcp startup is asynchronous. we need to wait for timing/color modes before finishing the drm device registration
<jannau>
the component change is good nevertheless and I'll keep it