ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
derzahl has joined #aarch64-laptops
<steev>
robclark: happen to know why there's no quirk to force rgb?
<steev>
(or if there is and i'm just not reading the names correctly)
<robclark>
-ECONTEXT? forcing rgb as opposed to?
<steev>
ycbcr
<robclark>
you mean on the connector end of things?
<steev>
i have that waveshare pictured a bit back
<steev>
it's an hdmi monitor and it gets ycbcr by default, and when it does, it has pink instead of black for... black; forcing rgb via editing the edid and saying it doesn't support ycbcr and the colors are proper
<robclark>
the input to the display controller will be rgb for fbcon, and whatever compositor picks
<robclark>
the output to (for ex) hdmi sink will be, IIRC, based on capabilities of the sink.. that isn't handled by core drm
<steev>
my understanding is that i'm getting MEDIA_BUS_FMT_YUV8_1X24 and i want MEDIA_BUS_FMT_RGB
<steev>
but i don't know of a way to just, pass that as a kernel command line thing
<robclark>
there isn't such a thing, that I know of
<steev>
edid hacking it is :)
<steev>
turns out, wxedid is kinda nice
<robclark>
if it is something involving dsi bridge, I think dsi controller expects it's downstream to want rgb
<robclark>
if it is pure dp then it might be a dp bug?
<steev>
i end up with this instead of the pinkly/purple
<robclark>
oh which device is this?
<steev>
it's hdmi... and amlogic... radxa zero
<robclark>
oh.. I don't know too much about that hw
<robclark>
but I guess it is display controller bug
<steev>
i had to hack the meson_venc in the first place because it says anything < h 640 or v 480 is invalid mode, and that "hdmi monitor" is 400x1280
<robclark>
yeah, maybe the sink wants hdmi and the display controller is sending it rgb or something like that
<steev>
i was kinda hoping maybe there was an EDID_QUIRK since it's not uncommon for edid to lie.... but you may be right
<robclark>
I guess you could try the panel on other hw to see if it is actually an edid bug needing quirking or a driver bug
<steev>
i'm gonna guess... driver bug
<steev>
it works fine as a secondary monitor to the x13s :D
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
SSJ_GZ has joined #aarch64-laptops
derzahl has quit [Ping timeout: 480 seconds]
Penguinpee_ has joined #aarch64-laptops
Penguinpee has quit [Ping timeout: 480 seconds]
Penguinpee_ is now known as Penguinpee
jhovold has joined #aarch64-laptops
Penguinpee has quit [Remote host closed the connection]
Penguinpee has joined #aarch64-laptops
Penguinpee has quit [Remote host closed the connection]
Penguinpee has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
<ndec>
hey steev , i am trying external monitor on x13s (for the first time), and I am getting a clutter crash. I think i remember you had a fix in gnome somewhere for something similar. can this log be the same issue?
<ndec>
steev: if i understand correctly, the 2nd fix is merged in main and planned for gnome 43. and it was backported to 3.38, but it is not backported to 42. so debian won't get it until 43?
<steev>
ndec: thats the fix that i have, and i backported it to 3.38 and 42, so it should be in 3.38, 42 and 43