#
…

2021-11-01

00:12user982492 has joined #asahi
00:22Augur[m] has joined #asahi
00:39goldsoultheory_ has joined #asahi
00:44goldsoultheory has quit [Ping timeout: 480 seconds]
01:15nobodynada has quit [Ping timeout: 480 seconds]
01:24nobodynada has joined #asahi
01:34nobodynada has quit [Ping timeout: 480 seconds]
01:37user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
01:43nobodynada has joined #asahi
01:44user982492 has joined #asahi
01:56rohin2 has quit [Ping timeout: 480 seconds]
02:05user982492_ has joined #asahi
02:05user982492 has quit [Read error: Connection reset by peer]
02:16nobodynada has quit [Ping timeout: 480 seconds]
02:18robinp[m] has joined #asahi
02:19rohin2 has joined #asahi
02:25nobodynada has joined #asahi
02:33nobodynada has quit [Ping timeout: 480 seconds]
02:39nobodynada has joined #asahi
03:09l3k has joined #asahi
03:24l3k has quit [Quit: leaving]
03:27tertu2 has joined #asahi
03:31tertu has quit [Ping timeout: 480 seconds]
03:34robinp[m] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:44nobodynada has quit [Ping timeout: 480 seconds]
03:48nobodynada has joined #asahi
03:59mika_ has joined #asahi
04:00kov has quit [Quit: Coyote finally caught me]
04:00kov has joined #asahi
04:01phiologe has joined #asahi
04:01mika_ has quit []
04:02mika_ has joined #asahi
04:02robinp[m] has joined #asahi
04:04PhilippvK has quit [Ping timeout: 480 seconds]
04:05marvin24_ has joined #asahi
04:08marvin24 has quit [Ping timeout: 480 seconds]
04:15user982492_ has quit [Remote host closed the connection]
04:17robinp[m] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:19user982492 has joined #asahi
04:36mika_ has quit [Quit: mika_]
04:43robinp[m] has joined #asahi
04:44robinp[m] has quit []
04:47robinp[m] has joined #asahi
05:01robinp[m] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:03marvin24 has joined #asahi
05:06marvin24_ has quit [Ping timeout: 480 seconds]
05:12rohin2 has quit [Ping timeout: 480 seconds]
05:22robinp[m] has joined #asahi
06:48user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:55user982492 has joined #asahi
07:33goldsoultheory_ has quit [Quit: Leaving]
07:47nobodynada has quit [Quit: leaving]
08:39kettenisjmr2: you could try booting linux from an external USB drive
08:45everslick_ has quit [Remote host closed the connection]
08:45everslick_ has joined #asahi
08:46FireFox317 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
08:48FireFox317 has joined #asahi
08:56nsklaus_listening to the stream, i'm happy to hear asahi won't have the notch and will set resulutions to not use the area on the upper screen where the notch is.
08:57nsklaus_*upper part of the screen
08:58nsklaus_apple itself will probably will do the same, when it come to its sense in two years or so
09:17darkapex1 has joined #asahi
09:18gabuscus has quit [Remote host closed the connection]
09:19darkapex has quit [Ping timeout: 480 seconds]
09:22gabuscus has joined #asahi
09:25bps2 has joined #asahi
09:36user982492 has quit [Remote host closed the connection]
09:36user982492_ has joined #asahi
09:40user982492_ has quit []
10:04svenlooks like the mailbox driver finally hit linux-next as well :-)
10:05j_eygreat1
10:07j_eysven: seems like subpage protection is always on for the t6000 dart
10:07j_ey(according2markan)
10:08svenchecking if we can somehow make use of that instead of swiotlb is somewhere on my TODO list :D
10:09svenbut first usb2 then rtkit and then finally nvme!
10:43aleasto has joined #asahi
10:51VinDuv_ has joined #asahi
10:52VinDuv has quit [Ping timeout: 480 seconds]
10:52VinDuv_ is now known as VinDuv
11:17kovnsklaus_, could you tell me a bit more about the notch bit? is it some hardware configuration? I got told KMS couldn't do that by itself (well, I was told it could not ignore a part of the screen, I guess it can set a default resolution...)
11:18dottedmagkov: Pretend that the resolution is smaller than native, only display that on the screen.
11:20kovdottedmag, that something the display controller will do?
11:24dottedmagkov: Frankly I'm not sure. First I thought it's not hard to just manipulate framebuffer offsets a bit, but that means framebuffers have to be allocated for the whole screen and then returned to userspace with some unused bits before the the "start" pointer, but now I'm not sure DRM can do that.
11:25kovyeah, daniels told me that wasn't how kms worked, but I guess advertising the highest 16x10 resolution as native sounds doable?
11:28darkapex1 has quit [Ping timeout: 480 seconds]
11:34nsklaus_kov: i have no idea how asahi team plan to do it, i'm not hardware dev, i'm just linux user, i was just reacting to marcan's stream where at the beginning he said what he intended to do (if possible). but, seeing macos does just that when running an app in fullscreen mode (not using the upper part of the screen where the notch is, rendering everything below that Y point) i suppose
11:34nsklaus_linux will try to do the same, just, all the time rather than just when some app goes fullscreen. but for the technical details, it's best to ask people will real qualifications to answer properly
11:36kovyeah, that's definitely something the compositors can do, like gnome-shell and kwin can decide what part of the screen apps will use, I was hoping we can have a solution at the kernel level though to save us the trouble ;D
11:37jixno idea what happens under the hood, but on xorg with xrandr you can almost add a black bar using --transform .. you can get a smaller framebuffer by scaling and you can shift the output to get a black bar... problem is it's still stretched and it moves parts offscreen
11:37nsklaus_i think it can be done at gfx driver level rather than in software configuration mode
11:38kovI think I may do some of the work on gnome-shell/mutter, my idea was to start with just ignoring the notch, then iterating on adding that screen space back - detecting it, moving the clock (the notch will cover it), and doing the fullscreen ignores the notch area
11:38nsklaus_what i mean is that linux would always avoid using the upper part of the screen, not just in X session, but in tty too, just everywhere
11:39kovyeah, that was what I was hoping, but I was being told KMS doesn't do that
11:39nsklaus_to me gnome is an abomination
11:39kovI respect your opinion
11:40nsklaus_i mean, i tend to avoid it like plague, so i wouldn't know the first thing about it, last time i touched gnome was in the early 2000s
11:40nsklaus_gnome2 era
11:41kettenisfor a plain framebuffer this is trivial
11:42kovnsklaus_, don't worry, I know about the gnome part =)
11:42nsklaus_kettenis: i might be wrong but, it seemed to me that, every gfx driver (kms, gpu, framebuffer,..) would take an x and a y axis coordinate to start rendering at said location, so it would be as simple as passing an offset to it ?
11:42kovI just don't know about the kernel bits, thus why I'm wondering, because I was told by people who know what they are talking about KMS could not ignore the area, it can however tell us where the dead space is
11:43kovhowever, if it's just a matter of changing the resolution to the highest 16x10 one, then maybe it's not that hard to get no notch by default
11:44kovwe'll see
11:45chadmedwell the screen itself is 70px taller than a normal 16:10 res, so you would just give the framebuffer a 16:10 res and then shift it down by 35px, assuming it spawns in the middle of the screen
11:48chadmedthis _might_ be something you can do with the display controller, just have it present a screen space of "normal" dimensions. userspace wouldnt even have to know about the 70px above 16:10 where the notch is
11:49kovthat'd be great
11:49nsklaus_all i can say is that i was glad to hear marcan acknowledge that it didn't make any sense in linux world to support that, and it would require lots of big projects (desktop environments, apps , etc) to support it and probably noone would bother, so best to bypass that 'notch' altogether.
11:50kovI think eventually we'd want to recover the space for people who really want it, but it would be a nice place to start
11:50j_ey^ he said that too
11:50nsklaus_i'd be happy to loose 70px in top of the screen and be done with this 'notch' nonsense
11:50j_eyso you keep saying!
11:51chadmedthe only problem i can see wrt the notch is fullscreen things like games, but in that case youd probably just give the game a 16:9 res and put up with it being letterboxed
11:51kovnsklaus_, yeah but linux is about choice™
11:52minidepends if other manufacturers follow the design choice ro not
11:52kovchadmed, yeah, that seems to be what mac os does
11:52kovand that'd need to be the compositor's job
11:52chadmedother than that, all the major DEs have ways to "accommodate" it. kde's menu bar equivalent has spacer widgets, so you can just put one under the notch and nothing will collide with it
11:52kovyeah, and we'd ideally do those things by default when we detect the dead space
11:53chadmedkov: dont most linux games just deal with SDL directly instead of going through the DE?
11:53nsklaus_j_ey: yes, well sorry about that. i didn't want to spam the channel, i'll keep quiet about it now
11:54chadmednsklaus_: cat's out of the bag :P
11:54kovchadmed, but if they're running on wayland they'll need to go through the compositor anyway, unless the compositor enables a bypass mode
11:55kov(I'm not so sure about X, but I think if a compositor is running they'd have to go through the compositor as well)
11:56kovas in, SDL just opens an X window (or wayland surface, has it been ported?), it doesn't write directly to the framebuffer, unless you're using a fb/kms backend and running on a console
11:56chadmedSDL can apparently draw surfaces directly to wayland
11:56kovyeah, when it creates a surface it's talking to the compositor (wayland is just a protocol), the compositor will decide what to do wit it
11:57chadmedright yeah
11:57klangePlease don't make me relive my memories of the days when GLX would use overlays and laugh at your puny compositor...
11:58kovyeah, X is a more special beast
11:58chadmed"special" is right
11:58kovbut I think even those tricks won't work if you're running XWayland, it'll end up as a surface controlled by the wayland compositor anyway ;D
11:59chadmedyeah i know csgo does this, havent experimented with scaling though. its a good test case because the game has hardcoded limits for resolution/aspect scaling to prevent people gaining competitive advantages with wide or tall screens
12:00chadmedperformance is generally terrible via XWayland though sadly, at least it is on nvidia
12:01chadmedand kwin_x11 is not getting any new features as of a few weeks ago
12:01kovI haven't used it for much more than chrome (under gnome), I don't really feel that much overhead
12:02chadmedyeah i just mean for games. csgo specifically.
12:02kovmakes sense
12:02kovso I guess for games you really want to stay on X for now
12:02chadmedthat said, that could just be an nvidia thing. im still running a gtx780 because i refuse to spend any more money on the PC ecosystem
12:03kovright, I use it with intel graphics, so you know, not gaming haha
12:03chadmedintel's wayland support is pretty good too. ive had some issues on my macbook but that might be related to nvme power management or something else quirky on the later intel macs
12:04kovwell tbf I did play a few steam games, but not the kind that requires that much of the GPU, things like Invisible Inc., FTL
12:05chadmedapparently you can pass an environment variable to SDL to tell it to hook wayland directly. ill need to see if this works with any of my source engine games at some point
12:05kovfor WoW and HotS I've been using either a PC or the mac mini
12:05chadmedby directly i mean without XWayland
12:05kova PC as in a windows PC with a 1080, and moonlight
12:06kov(but looking forward to playing WoW with quality 10 on the macbook pro 14" m1 max 32 gpu cores xD)
12:07darkapex has joined #asahi
12:07chadmedim slowly coming around to the idea of buying a macbook, but i dont want all my desktop hardware to be useless until the thunderbolt/usb-c drivers are done and i am far too stupid to be of any help with either given how complex they are
12:08chadmedbut my vibe analysis tells me we wont get M1 pro/max mac minis until Q2 next year so i might have to bite the bullet
12:09kovyeah... that's more or less my thinking, I think they may even skip pro/max for minis
12:09kovand keep it at the base M models, so the next one would be M2
12:10kovI guess they want to keep that segment for the iMac Pro
12:10chadmednah theyre definitely coming, we have schematics and renders for the chassis
12:11chadmedtheyve just been delayed because of how rooted global supply chains are. word is theyve barely enough chips for the macbooks even
12:19kovI've seen the renders, but do the schematics confirm it's M1 Pro/max?
12:19kovbecause if not I'm still betting on A15-based M2
12:37kaprests_ has joined #asahi
12:38kaprests_ has quit [Quit: leaving]
12:51chadmedi dont think theyll release the M2 so close to the M1P/M
12:52chadmedplus theyll want to start being seen as a legitimate contender in the workstation/server space. thus, they will release manycore mac minis/mac pros based on the M1 design before they will come with an M2
12:53chadmedim sure someones got that infographic link lying around somewhere, but it looks like we will be getting minis/pros with M1 Pro/Max based multi-chip packages.
13:02kovI won't complain for being wrong tbh =D
13:56coderobe has joined #asahi
14:00gpanders[m] has joined #asahi
14:46jbowen has joined #asahi
14:54gpanders[m]1 has joined #asahi
15:35rohin2 has joined #asahi
15:55bps2 has quit [Ping timeout: 480 seconds]
15:55daniels has joined #asahi
15:59danielsfwiw on the notch, the thing to do is:
15:59daniels* expose the 16:10 mode as the default to userspace, and offset the primary plane in Y when it's in use so the notch is avoided (there have been patches for a CRTC background-colour property if DCP supports this, but they never landed due to lack of open userspace for them)
15:59daniels* similar to 3D modes, add a new mode flag for notchful modes, which are not shown to userspace unless they opt in to a new DRM client cap for it
15:59daniels* create a new CRTC property for the notch area
15:59daniels* smart userspace can set the client cap, see the notchful modes and the CRTC property, and render around it
16:00daniels(you'd have to do the equivalent for Wayland, where fullscreen only meant 16:10 unless you opted in to notch awareness)
16:02marcan#1 was my idea, yeah
16:02marcangood to hear about the right way to implement notch-awareness
16:03marcando you have any good ideas about how to represent the notch shape itself?
16:03marcanultimately it's a bitmap mask; I don't know how it is on these machines, but at least on Androids I've seen software is expected to antialias/mask the edge
16:04danielshuh, TIL about Android ... I mean you could certainly just expose a bitmask as a blob property, but rect would be easier for now and almost certainly sufficient?
16:04marcan*memsets the framebuffer*
16:04rohin2 has quit [Ping timeout: 480 seconds]
16:04marcanoh wow, the antialiased edges are done in hardware
16:04marcanwell, that makes software's life easier
16:04marcanwonder if this is display controller magic, or in the TCON
16:05danielsimpressive
16:08marcanshitty phonecam shot, but you get the idea
16:08marcanalso, it's not just the notch
16:08marcanthere are also rounded corners on the top left and right
16:08marcanthat also needs to be exposed to userspace
16:08ari'm kinda surprised notch information isn't present in DT
16:08marcanit only has a boolean flag, yeah
16:08marcanbut it's probably because they couldn't figure out a good way to represent the particulars generically...
16:09danielsis the grey/black split your doing (i.e. literally what's in the fb), or can you program a background colour for areas not covered by a plane?
16:09rohin2 has joined #asahi
16:09marcanjust what's in the fb
16:09marcanI memset 1MiB and it landed there :p
16:09ar(also, i wonder how long it'll take for them to switch to under-display cameras ;) )
16:09j_ey1MiB .. is not a lot of screen is it
16:10marcannot on these retina ones, no...
16:10marcanand this is why they use framebuffer compression for macos/agx
16:30bps2 has joined #asahi
16:43jbowen has quit [Ping timeout: 480 seconds]
16:44rohin2 has quit [Ping timeout: 480 seconds]
16:45Bey0ndB1nary has joined #asahi
16:52Bey0ndB1nary has quit []
16:59pipcet[m] has left #asahi [#asahi]
17:02jbowen has joined #asahi
17:24bps2 has quit [Ping timeout: 480 seconds]
17:49jbowen has quit [Ping timeout: 480 seconds]
17:56kenjigashu has joined #asahi
17:57kenjigashu has quit [Remote host closed the connection]
18:00jbowen has joined #asahi
18:17___nick___ has joined #asahi
18:18___nick___ has quit []
18:20___nick___ has joined #asahi
18:29user982492 has joined #asahi
18:50quentin[m] has joined #asahi
19:45kenjigashu has joined #asahi
19:45kenjigashu has quit [Remote host closed the connection]
19:48kenjigashu has joined #asahi
19:50kenjigashu has quit []
19:51mika_ has joined #asahi
19:51mika_ has quit [Remote host closed the connection]
20:03jacoxon has joined #asahi
20:26aleasto has quit [Remote host closed the connection]
20:29jbowen has quit [Ping timeout: 480 seconds]
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:33kenjigashu has joined #asahi
21:34kenjigashu has quit [Remote host closed the connection]
21:44user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:57jacoxon has quit []
22:00bps2 has joined #asahi
22:08kenjigashu has joined #asahi
22:09bps2 has quit [Ping timeout: 480 seconds]
22:12bps2 has joined #asahi
22:23bps2 has quit [Ping timeout: 480 seconds]
22:26kenjigashu has quit []
22:30bps2 has joined #asahi
23:02user982492 has joined #asahi
23:06phire"<marcan> oh wow, the antialiased edges are done in hardware" I'm curious if that's done in the LCD controller, or if it's a physical property of the panel itself.
23:53X-Scale has joined #asahi
23:59X-Scale` has quit [Ping timeout: 480 seconds]
…