ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
mani_s has joined #aarch64-laptops
<steev> ah, no idea about the zip files and such, i always do git clones (but i don't use JensGlathe[m]'s repo :(
<valpackett> git clone or not shouldn't affect include paths inside of a dpkg-buildpackage build 0.o
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
agl has quit [Ping timeout: 480 seconds]
agl has joined #aarch64-laptops
tobhe has joined #aarch64-laptops
zetam has quit [Quit: going out!]
hexdump02 has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has quit [Ping timeout: 480 seconds]
sally_ is now known as sally
mani_s has quit [Quit: Connection closed for inactivity]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
zetam has joined #aarch64-laptops
zetam has quit []
<JensGlathe[m]> after failed build, just try to invoke sudo apt-get build-dep . to install whats missing. Additionally, I install devscripts llvm clang lld
<JensGlathe[m]> also, just pushed jg/ubuntu-qcom-x1e-6.16.0-rc4-jg-0 to my repo, with a slightly modified rebuild.sh which avoids cross-compile on the arm64 box
<steev> valpackett: i just don't trust github's tarballs/zipballs
cenunix[m] has joined #aarch64-laptops
<cenunix[m]> Does x13s have issues with ipv6 enabled routers for home WiFi
<cenunix[m]> Or is it wpa3 that’s giving me issues, hmm
SpieringsAE has joined #aarch64-laptops
xroumegue has joined #aarch64-laptops
croissant has joined #aarch64-laptops
<steev> probably wpa3, but what sort of issues?
ektor5 has quit [Quit: WeeChat 4.3.4]
ektor5 has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
anthony25 has quit [Quit: Quit]
anthony25 has joined #aarch64-laptops
reng_ has quit [Ping timeout: 480 seconds]
reng has joined #aarch64-laptops
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
ungeskriptet has quit [Ping timeout: 480 seconds]
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
pabs has quit [Ping timeout: 480 seconds]
pabs has joined #aarch64-laptops
ungeskriptet has joined #aarch64-laptops
sally has quit [Quit: ZNC 1.9.1+deb2+b3 - https://znc.in]
<kuruczgy_> lumag: do you know anything about whether drm color ops is going to be supported on x1e?
sally has joined #aarch64-laptops
ravikant_ has quit []
minecrell has quit [Quit: Ping timeout (120 seconds)]
sgerhold has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #aarch64-laptops
sgerhold has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet has joined #aarch64-laptops
enyalios has quit [Remote host closed the connection]
enyalios has joined #aarch64-laptops
sally has quit []
sally has joined #aarch64-laptops
zetam has joined #aarch64-laptops
sally has quit []
sally has joined #aarch64-laptops
mani_s has joined #aarch64-laptops
zetam has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
mani_s has quit [Quit: Connection closed for inactivity]
<lumag> kuruczgy_: not in the close future
<kuruczgy_> lumag: I see. So for now CTM is the only realistic option for color temperature adjustment? (In #wlroots I was told that they plan to focus on drm color ops for the next gamma adjustment wayland protocol, and they are not planning on supporting CTM soon.)
<robclark> compositor should be able to do color processing on GPU, in shader
<robclark> I guess there probably isn't much measurable cost.. the main reason to do it in dpu is to avoid powering up the GPU when display is composited w/ overlays, but most wl compositors aren't doing much of that
<lumag> kuruczgy_: there are several complications with color ops for DPU. So, yes, we are stuck with CTM for now. We might get gamma/degamma, if I get enough pressure to do it.
<kuruczgy_> robclark: Yeah, I think they are planning a shader based fallback, I just wanted to know what it would take to do a "proper" solution. But it's good to know that you think the perf cost is negligible.
patrickm has quit [Read error: Network is unreachable]
<robclark> lumag: maybe kuruczgy_ could confirm, but I think when hdr isn't in the picture, gamma/degamma is the main thing needed?
<kuruczgy_> For my personal use-case I care about color temperature adjustment (for "night light" functionality, so it doesn't have to be color accurate or anything)
<kuruczgy_> I have no idea what the interface of color ops looks like though, if some resource available on it I would like to learn more. (Are you talking about a partial support of color ops with gamma/degamma?)
<robclark> I think it is mostly https://www.kernel.org/doc/html/v4.10/gpu/drm-kms.html#color-management-properties ? But tbh I've not paid too much attention to it.. the gpu side of things keeps me plenty busy ;-)
<lumag> no, gamma/degamma is an old interface, drm_crtc_enable_color_mgmt().
<lumag> robclark: yes
patrickm has joined #aarch64-laptops
<robclark> wasn't there some plane level color processing? IIRC that was the fancy parts?
<kuruczgy_> this gamma/degamma LUT looks suspiciously like the stuff in wlr-gamma-control, is this the current kernel interface used by compositors for this? Because in that case that would actually be the best one for me, all the userspace support is already there.
<robclark> so the CRTC gamma/degamma props have been around forever.. so probably what compositors use
<robclark> there is more fancy things needed if blending hdr and sdr layers, but that is maybe more niche
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]