2023-12-03
00:14Moprius has joined #asahi
00:20povik has quit [Remote host closed the connection]
00:23Brainium has joined #asahi
00:40chadmed has quit [Ping timeout: 480 seconds]
00:48crabbedhaloablut has quit []
01:26Moprius has quit [Quit: bye]
01:31Brainium has quit [Read error: No route to host]
01:36john-cabaj has quit [Ping timeout: 480 seconds]
01:48kidplayer666 has quit [Quit: Connection closed for inactivity]
01:54cow123 has joined #asahi
02:13chadmed has joined #asahi
02:15as400 has quit [Remote host closed the connection]
02:24as400 has joined #asahi
02:58deflax59 has quit []
02:59deflax59 has joined #asahi
02:59grange_c688 has quit [Quit: Ping timeout (120 seconds)]
02:59grange_c688 has joined #asahi
02:59FLHerne has quit [Quit: There's a real world out here!]
02:59FLHerne has joined #asahi
03:46gspbirel56 has quit [Quit: Ping timeout (120 seconds)]
03:47gspbirel56 has joined #asahi
04:51marvin24 has joined #asahi
04:54marvin24_ has quit [Ping timeout: 480 seconds]
06:07dikiaap has joined #asahi
06:08nicolas17 has quit [Read error: Connection reset by peer]
06:09nicolas17 has joined #asahi
07:29dikiaap has left #asahi [Leaving]
07:51veebop has left #asahi [The Lounge - https://thelounge.chat]
07:57veebop has joined #asahi
08:01Ashbir has joined #asahi
08:01Ashbir has left #asahi [#asahi]
08:06IEF has quit [Quit: Bai!]
08:20Ashbir has joined #asahi
08:26crabbedhaloablut has joined #asahi
08:30Ashbir has quit [Quit: Leaving]
08:33al3xtjames has joined #asahi
08:37chadmed has quit [Ping timeout: 480 seconds]
08:38chadmed_ has joined #asahi
08:49al3xtjames has quit [Quit: al3xtjames]
08:50al3xtjames has joined #asahi
08:53kidplayer666 has joined #asahi
08:54kidplayer666i saw the release of hdmi support!! real nice! (guessing that dp alt is cooking too)
09:10luna has joined #asahi
09:12luna has left #asahi [#asahi]
09:14MichaelLongkidplayer666, where and how it hdmi support released?
09:15kidplayer666Apparently with the new kernel, for laptops with an hdmi port
09:17MichaelLongkidplayer666, I'm only aware of this post: https://social.treehouse.systems/@marcan/111435705255320195
09:17MichaelLongwhich is really nice!
09:17holiday has joined #asahi
09:18kidplayer666I saw this one
09:18MichaelLongkidplayer666, ohh
09:19MichaelLongI'll have to test immediately :> thx
09:19kidplayer666You’re welcome
09:19kidplayer666MichaelLong: tell us the results
09:32MichaelLonggreat it works for me! There was one minor kosmetic irritation: I'm using a LG 38WN95C-W display that has a resolution of 3840x1600, after pluging in KDE however selected 3840x2160. Probably an EDID issue? But great work really :)
10:08IEF has joined #asahi
10:18ydalton has joined #asahi
10:26i509vcb has quit [Quit: Connection closed for inactivity]
10:26PaulFertserMichaelLong: a resolution higher than the display supports was selected and it still works? Something doesn't sound right there.
10:27IEF has quit [Quit: Bai!]
10:27IEF has joined #asahi
10:28MichaelLongPaulFertser, not sure how that worked but the displayed screen was cropped and blurred on the 2160p resolution. But I could easily select the correct resolution from the kscreen menu.
10:31MichaelLongcould be a one off issue, was not able to reproduce it when pluggin the hdmi a couple of times
10:42ydalton has quit [Remote host closed the connection]
10:44ydalton has joined #asahi
10:44ydaltonrebooting into the new kernel, i see the addition of the dcpext DT node, but it's disabled, as expected
10:52svenaltmode will probably take a while longer. the bigger issues are still inside atcphy and typec/tipd, but we're slowly making progress there
11:07Moprius has joined #asahi
11:17Brainium has joined #asahi
11:25ydalton has quit [Remote host closed the connection]
11:31jannegdp only mode on atc-phy3 of 14-/16-inch macbook pros worked so far without issue. so that part might avoided the usb curse somehow
11:33jannegMichaelLong: interesting. can you still select 3840x2160 in kde's display settings? we only forward modes reported by the dcp firmware
11:42sventhere’s still something strange with the pipehandler vs. dwc3 vs. atcphy bringup though in my current tree :/
11:46PaulFertserHm, so there's no direct access to EDID data via dcp?
11:53ydalton has joined #asahi
11:58SalimTerryLi has quit [Ping timeout: 480 seconds]
11:58PaulFertserAlso information about manufacturer and model, and physical size (needed to get DPI right)
12:00PaulFertserAnd information related to colour capabilities, gamma etc.
12:03PaulFertserI'm kind of surprised you do not trust the common software layers to do the right thing with the EDID info. But knowing how much you care about visual aspects I conclude you have some veryy valid reasons for that.
12:03PaulFertserydalton: yes, plain Xorg.
12:04PaulFertserydalton: but that's Xorg running on an SBC, so not really related to Asahi. I just wanted to give an example of EDID to show what's there available inside.
12:06ydaltonjanneg, PaulFertser: ah thanks! i always wondered how the GPUs got the modes from the monitors connected to them
12:08jannegPaulFertser: I do not trust the common software layers to arrive at the same results as the dcp firmware and that might cause issues in the form of failing to modeset at all
12:13PaulFertserbtw, can someone probably explain what the deal with all that fractional scaling issues really is? I was assuming that it doesn't concern text at all as most applications are using vector fonts and they're scaled automatically correctly (taking DPI into account) for very long time, and the problem is only with bitmap graphics of UI elements, they become too tiny? Is it still common to use bitmaps
12:13PaulFertserfor icons etc?
12:14PaulFertserjanneg: ah, I see, if the modesetting is basically all outsourced to DCP firmware then no wonder.
12:15PaulFertserydalton: for the reference, it's basically just an EEPROM connected via I2C.
12:20SalimTerryLi has joined #asahi
12:20Moprius has quit [Quit: bye]
12:38chadmed_ has quit [Ping timeout: 480 seconds]
12:54chadmed_ has joined #asahi
12:54chadmed_ is now known as chadmed
12:59thelounge986 has quit [Quit: Ping timeout (120 seconds)]
12:59thelounge986 has joined #asahi
13:36ten157237743246 has joined #asahi
13:42ten15723774324 has quit [Remote host closed the connection]
13:43ten15723774324 has joined #asahi
13:49ten157237743246 has quit [Ping timeout: 480 seconds]
13:49___nick___ has joined #asahi
13:56kidplayer666PaulFertser: i think it’s mainly on gnome where it’s still experimental, and while most of the desktop appears ok, anytbing x11 gets horribly grainy
13:56kidplayer666KDE is fine on that regard though
14:00Brainium has quit [Quit: Konversation terminated!]
14:03fugi has quit [Ping timeout: 480 seconds]
14:07fugi has joined #asahi
14:27tobhe has joined #asahi
14:28ydalton has quit [Remote host closed the connection]
14:30tobhe_ has quit [Ping timeout: 480 seconds]
14:39PaulFertserkidplayer666: I've read the post about it but I'm not understanding the basics. Why is scaling of any kind is involved at all when all the fonts used are vector (OpenType/TTF etc)?
14:40PaulFertserI remember issues with very old apps which were built without "layouts"/"flexible containers" where the UI element positions were hardcoded in pixels, yes, but all the modern toolkits have dynamic layout, so, again, they're always fractionally scaled. So what's left, the UI icons?
14:40kidplayer666PaulFertser: I am not qualified or knowlegable to know the specifics, but x11 does not support fractional scaling properly. KDE gets around this on wayland by just letting x11 apps apply their own scaling. Gnome tries to apply the scaling to the whole thing and it goes wack
14:43PaulFertserkidplayer666: all vector fonts in X11 are scaled to provide the right size in "pt" (physical dimensions), and layouts are dynamic, so what exactly is missing?
14:43kidplayer666no idea. As i said, all i know is that it goes wack
14:45PaulFertserkidplayer666: do you mean wayland forces rescaling of all rootless Xwayland windows?
14:45kidplayer666i do not know. i think gnome tries to force scaling while kde is chill about it
14:45PaulFertserI'd be grateful for someone to unconfuse me.
14:47PaulFertserYou mean Wayland compositor that's part of gnome is telling wayland to rescale Xwayland regions and there's no way to have it not to?
14:50kidplayer666PaulFertser: I'd be grateful too, I am just repeating some bits i heard here and there
14:50kidplayer666no idea how mutter and the kde compositor actually work
15:01possiblemeatball has joined #asahi
15:06MichaelLongjanneg, sorry I was only able to check it just now: I can still see the wrong resolution. But I have totally forgotten I'm running a cheap chinese KVM-switch in between. The wrong resolution is also advertised on at least one other system currently connected. I'll see if I can find another HDMI cable to connect it directly to the display....
15:33jannegMichaelLong: ah, it's probably in the EDID from the KVM then. does the wrong resolution get's advertized in macOS as well?
15:34MichaelLongjanneg, most likely I'll check next time, sorry for the noise :)
16:17jeisom has quit [Quit: Leaving]
16:19jeisom has joined #asahi
16:28bsandro has quit [Read error: Connection reset by peer]
16:54Brainium has joined #asahi
17:17mohit815822 has joined #asahi
17:22mohit81582 has quit [Ping timeout: 480 seconds]
17:22mohit815822 is now known as mohit81582
17:29tobhe_ has joined #asahi
17:31tobhe has quit [Ping timeout: 480 seconds]
17:57florolf has quit [Remote host closed the connection]
18:04rootbeerdan has quit [Quit: rootbeerdan]
18:04rootbeerdan has joined #asahi
18:04i509vcb has joined #asahi
18:20unixpoet has quit [Quit: leaving]
18:20Pykee has joined #asahi
18:21unixpoet has joined #asahi
18:27kidplayer666 has quit [Quit: Connection closed for inactivity]
18:41Pykee has quit [Quit: Lost terminal]
19:14holiday has quit [Quit: WeeChat 4.1.1]
19:16kidplayer666 has joined #asahi
19:19malte has quit [Ping timeout: 480 seconds]
19:24florolf has joined #asahi
19:33holiday has joined #asahi
19:34holiday has quit []
19:48Nefsen402I tried using HDMI and it worked for my display. It litup 4k at 60Hz. I also discovered that you guys are handling clam shell mode! That was a surprise. But then I manually hit the suspend button. The display did come offline, but refused to ever come back online. Even after a hotplug, it's dead jim. journalctl -k logs: https://ozal.ski/dcp-log.txt
20:10tel1 has quit [Remote host closed the connection]
20:32tel1 has joined #asahi
21:04crabbedhaloablut has quit []
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:34arekm has quit [Remote host closed the connection]
21:49arekm has joined #asahi
22:44Brainium has quit [Remote host closed the connection]
22:44cow123 has quit [Remote host closed the connection]
22:48pthariensflame has joined #asahi
22:48Dominika has joined #asahi
22:50ellyq has quit [Remote host closed the connection]
22:50alka has joined #asahi
22:50pthariensflame has quit []
22:50sdomi has quit [Read error: Connection reset by peer]
22:50leahcl has left #asahi [#asahi]
22:55Moprius has joined #asahi
22:59delroth has quit [Remote host closed the connection]
23:00delroth has joined #asahi
23:02qyliss has quit [Quit: bye]
23:03delroth has quit [Remote host closed the connection]
23:04qyliss has joined #asahi
23:05delroth has joined #asahi
23:14Brainium has joined #asahi
23:28eroc1990 has quit [Quit: The Lounge - https://thelounge.chat]
23:31eroc1990 has joined #asahi
23:39Moprius has quit [Quit: bye]