ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
stuart has quit []
ybogdano has quit [Ping timeout: 480 seconds]
LexSfX has joined #dri-devel
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
macromorgan has joined #dri-devel
sravn_ has quit [Remote host closed the connection]
sravn_ has joined #dri-devel
adavy has quit [Remote host closed the connection]
adavy has joined #dri-devel
dakr has quit [Ping timeout: 480 seconds]
Guest580 is now known as bluepenquin
bcheng has quit [Remote host closed the connection]
bcheng has joined #dri-devel
mbrost has joined #dri-devel
mbrost_ has joined #dri-devel
mbrost has quit [Ping timeout: 480 seconds]
tonyk has quit [Quit: Ping timeout (120 seconds)]
sergi has quit [Quit: Ping timeout (120 seconds)]
tonyk has joined #dri-devel
sergi3 has joined #dri-devel
saurabhg has joined #dri-devel
mbrost__ has joined #dri-devel
mbrost_ has quit [Ping timeout: 480 seconds]
mairacanal[m] has quit []
MatrixTravelerbot[m]1 has quit []
dafna33[m] has quit []
colemickens has quit []
LaughingMan[m] has quit []
cleverca22[m] has quit []
tintou has quit []
arisu has quit []
Guest581 has quit []
bylaws has quit []
chema has quit []
dcbaker has quit []
aravind has joined #dri-devel
saurabhg has quit [Ping timeout: 480 seconds]
heat has quit [Ping timeout: 480 seconds]
saurabhg has joined #dri-devel
nchery has quit [Remote host closed the connection]
nchery has joined #dri-devel
nchery has quit [Read error: Connection reset by peer]
nchery has joined #dri-devel
nchery has quit [Remote host closed the connection]
nchery has joined #dri-devel
nchery has quit [Remote host closed the connection]
nchery has joined #dri-devel
pallavim has joined #dri-devel
nchery has quit [Remote host closed the connection]
nchery has joined #dri-devel
nehsou^ has joined #dri-devel
saurabhg has quit [Ping timeout: 480 seconds]
sravn has joined #dri-devel
nchery has quit [Ping timeout: 480 seconds]
bluepenquin has quit [Quit: issued !quit command]
sravn_ has quit [Ping timeout: 480 seconds]
nchery has joined #dri-devel
srslypascal is now known as Guest664
srslypascal has joined #dri-devel
nchery has quit [Read error: Connection reset by peer]
Guest664 has quit [Ping timeout: 480 seconds]
bluepenquin has joined #dri-devel
saurabhg has joined #dri-devel
<lina> jekstrand: Thank you! Please let me know when you have some time!
<jekstrand> lina: I should be free most of next week. I'm on US central time. IDK how that maps to where you are.
<jekstrand> lina: We can chat via IRC or do a conference call and we can pull alyssa in too, or not. Whatever you want.
<lina> I'll ask her if she wants to join, IRC probably works!
srslypascal is now known as Guest667
srslypascal has joined #dri-devel
<jekstrand> Cool. Find a few times that you think will work and I can probably make one of them work. Just best to avoid Mondays.
Guest667 has quit [Ping timeout: 480 seconds]
saurabhg has quit [Ping timeout: 480 seconds]
saurabhg has joined #dri-devel
mbrost__ has quit [Read error: Connection reset by peer]
<jekstrand> lina: You can ping me here or e-mail at either jason@jlekstrand.net or jason.ekstrand@collabora.com
* ccr fetches lasagna.
Duke`` has joined #dri-devel
slattann has joined #dri-devel
jewins has quit [Ping timeout: 480 seconds]
fxkamd has quit []
slattann has quit [Read error: Connection reset by peer]
tzimmermann has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
srslypascal has quit [Remote host closed the connection]
fab has joined #dri-devel
srslypascal has joined #dri-devel
itoral has joined #dri-devel
JohnnyonFlame has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
bmodem has joined #dri-devel
bmodem has quit []
gio has joined #dri-devel
sravn has quit [Remote host closed the connection]
sravn has joined #dri-devel
danvet has joined #dri-devel
garrison has joined #dri-devel
i-garrison has quit [Remote host closed the connection]
garrison has quit []
kts has joined #dri-devel
i-garrison has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
sdutt has quit [Read error: Connection reset by peer]
warpme___ has joined #dri-devel
fab has quit [Quit: fab]
mvlad has joined #dri-devel
slattann has joined #dri-devel
nchery has joined #dri-devel
tursulin has joined #dri-devel
vliaskov has joined #dri-devel
jkrzyszt has joined #dri-devel
rgallaispou has joined #dri-devel
<pq> emersion, HDR_OUTPUT_METADATA particularly has no checks agains monitor claimed support, because userspace parses the raw edid and could legitimately use a HDR mode the kernel does not know about. The kernel only passes the metadata on.
<emersion> i see
<emersion> i was mostly concerned about HDR_OUTPUT_METADATA set when a DP->VGA adapter is being used or something
<pq> mdnavare, vsyrjala, if one CRTC is drivign multiple connectors, and one of those monitors is not VRR-capable, what (should) happens?
Daanct12 has joined #dri-devel
lynxeye has joined #dri-devel
<pq> emersion, hmm, good question, attaching a HDR monitor through a link that cannot send metadata at all... (how) should userspace figure out the actual link type and infer metadata cannot be sent?
<pq> I think there is lots of color stuff that could be metadata, so many KMS properties would be affected.
<pq> OTOH, it's impossible to know if a monitor actually handles any metadata (or even pixels) as expected, so if checking is difficult, could just punt that to the end user "doctor it hurts to connect a HDR monitor via VGA".
<pq> If the monitor manufacturer could bother, they'd have a different EDID via VGA than HDMI/DP... haa haa ha.
<airlied> does VGA HDR monitors even exist?
<airlied> most monitors with vga and hdmi return different EDIDs
<airlied> never seen one that returned the same thing
rasterman has joined #dri-devel
jkrzyszt has quit [Remote host closed the connection]
jkrzyszt has joined #dri-devel
DemiMarieObenour[m] is now known as DemiMarie
pcercuei has joined #dri-devel
saurabhg has quit [Ping timeout: 480 seconds]
<pq> airlied, oh wow, manufacturers exceeding my expectations :-)
KunalAgarwal[m] has quit []
<emersion> i recall some monitor with the same EDID served on all ports
<pq> HDR metadata is not the only kind of metadata, just the most glaring to get wrong
<emersion> but yeah it's just buggy, and it's the exception rather than the norm
<vsyrjala> hmm. i guess we might need some capability props on connectors to deal with dongle restrictions
sravn has quit [Remote host closed the connection]
sravn has joined #dri-devel
<emersion> we have a "subconnector" prop already
guru_ has joined #dri-devel
MajorBiscuit has joined #dri-devel
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
oneforall2 has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
<vsyrjala> that part should mostly be handled by the monitor when it report the edid
Daanct12 has quit [Remote host closed the connection]
<vsyrjala> i;m more worrie3d about stuff like dp 1.4 optional cta sdp stuff for transmitting large amounts of metadata
<vsyrjala> i think that might be needed for some dynamic hdr metadata stuff
Daanct12 has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
sarahwalker has joined #dri-devel
Newbyte has quit []
kallisti5[m] has quit []
cmeissl[m] has quit []
kusma has quit [Quit: Bridge terminating on SIGTERM]
neobrain[m] has quit []
DemiMarie has quit [Quit: Bridge terminating on SIGTERM]
heftig has quit [Quit: Bridge terminating on SIGTERM]
mripard has quit []
danylo has quit []
frytaped[m] has quit []
DavidHeidelberg[m] has quit []
r[m] has quit []
martijnbraam has quit [Quit: Bridge terminating on SIGTERM]
michael5050[m] has quit []
ralf1307[theythem][m] has quit []
Tooniis[m] has quit []
ramacassis[m] has quit []
PiGLDN[m] has quit []
jacobcrypusa[m] has quit []
tomba has quit [Quit: Bridge terminating on SIGTERM]
Mis012[m] has quit []
nielsdg has quit []
hasebastian[m] has quit []
unrelentingtech has quit []
Dylanger has quit []
robertfoss[m] has quit []
Soroush has quit []
Strit[m] has quit []
jekstrand[m] has quit []
cwfitzgerald[m] has quit []
sjfricke[m] has quit []
Andy[m] has quit []
ambasta[m] has quit []
kunal_10185[m] has quit []
masush5[m] has quit []
Mershl[m] has quit []
pushqrdx[m] has quit []
knr has quit []
robertmader[m] has quit []
undvasistas[m] has quit []
gnustomp[m] has quit []
KunalAgarwal[m][m] has quit []
reactormonk[m] has quit []
GeorgesStavracasfeaneron[m] has quit []
AlexisHernndezGuzmn[m] has quit []
egalli has quit []
tleydxdy has quit [Quit: Bridge terminating on SIGTERM]
Anson[m] has quit []
onox[m] has quit []
pac85[m] has quit []
gagallo7[m] has quit []
ella-0[m] has quit []
JosExpsito[m] has quit []
Vin[m] has quit []
jenatali has quit []
Guest601 has quit []
sigmoidfunc[m] has quit []
yshui` has quit []
kunal10710[m] has quit []
YaLTeR[m] has quit []
doras has quit []
halfline[m] has quit []
T_UNIX has quit []
Sumera[m] has quit []
xerpi[m] has quit []
Guest588 has quit []
viciouss[m] has quit []
x512[m] has quit []
eyearesee has quit []
zzoon[m] has quit []
RAOF has quit [Quit: Bridge terminating on SIGTERM]
gdevi has quit []
hch12907 has quit []
moben[m] has quit []
naheemsays[m] has quit []
znullptr[m] has quit []
Ella[m] has quit []
kunal_1072002[m] has quit []
zamundaaa[m] has quit []
jasuarez has quit []
nyorain[m] has quit []
bluepenquin has quit [Quit: Bridge terminating on SIGTERM]
apinheiro has joined #dri-devel
kts has joined #dri-devel
arisu has joined #dri-devel
fab has joined #dri-devel
MajorBiscuit has quit [Quit: WeeChat 3.5]
MajorBiscuit has joined #dri-devel
heat has joined #dri-devel
fab has quit [Ping timeout: 480 seconds]
ppascher has quit [Quit: Gateway shutdown]
fab has joined #dri-devel
fab has quit []
macromorgan is now known as Guest691
macromorgan has joined #dri-devel
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #dri-devel
Guest691 has quit [Ping timeout: 480 seconds]
<tomeu> I'm trying to use the android binaries we build in Mesa CI, and finding this problem:
<tomeu> vsoc_x86_64:/data # LD_LIBRARY_PATH=/data/install/lib ./deqp-egl
<tomeu> CANNOT LINK EXECUTABLE "./deqp-egl": cannot locate symbol "eglDestroySyncKHR" referenced by "/system/lib64/libgui.so"...
<tomeu> guess the Android system libs are linking directly to eglDestroySyncKHR instead of going through eglGetProcAddress, and wonder what do people do about it
devilhorns has joined #dri-devel
fahien has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
pcercuei has quit [Read error: Connection reset by peer]
pcercuei has joined #dri-devel
<tzimmermann> javierm, if you have a minute, could you look at https://patchwork.freedesktop.org/series/108360/ ?
<javierm> tzimmermann: sure
<javierm> tzimmermann: btw, about mgag200 G200ER not supporting 24-bit color depth, maybe you could use a dmi match table for this ?
<javierm> instead of forcing 32 bpp for all mgag200 variants ?
<tzimmermann> javierm, dmi match table?
Haaninjo has joined #dri-devel
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #dri-devel
<javierm> using the DMI table information to determine whether the quirk has to be applied or not
<javierm> tzimmermann: or maybe the PCI device ID from mgag200_pciidlist would be enough to figure out that ?
<tzimmermann> a good idea. i don't know if the problem only happens on this dell machine. i wish i'd have someone else with that chips
dakr has joined #dri-devel
<javierm> tzimmermann: yeah, I would just do it for that particular dell machine. Unless someone reports for another G200_ER, then in mgag200_pci_probe() for case G200_ER you can set 24 bpp
<javierm> err, I meant 32 bpp. But you get the idea
<javierm> tzimmermann: in other words, I think that would be a good idea to constraint the workaround as much as possible
<tzimmermann> sure. the current fix is for mainline only and restores the old behavior. in the drm-tip, we have split the driver into per-chip codepaths. on that particular g200er, we could simply not anounce rgb888 at all
<tzimmermann> thanks for the tip
<Ristovski> here's one for the intel folks: After some time, I can observe micro stutters that go away when you either 1) start moving the mouse (this only works for the duration if you moving the mouse) 2) Switch to a tty and back (this fixes it for a couple of minutes). I've had this happen more rarely, but now that I have a second output active, it appears to happen more frequently
<Ristovski> thought it might be related to FBC but its not :/
<javierm> tzimmermann: I see. Makes sense
<tzimmermann> javierm, we can use the dmi match table in that particular codepath
<javierm> tzimmermann: yup, because it may be an issue only in that particular dell machines but not in all g200er
<javierm> tzimmermann: although I know nothing about this driver, just noticed your partial revert patch and thought about it
tobiasjakobi has joined #dri-devel
ambasta[m] has joined #dri-devel
Andy[m] has joined #dri-devel
bluepenquin has joined #dri-devel
bylaws has joined #dri-devel
chema has joined #dri-devel
RAOF has joined #dri-devel
cleverca22[m] has joined #dri-devel
cmeissl[m] has joined #dri-devel
colemickens has joined #dri-devel
cwfitzgerald[m] has joined #dri-devel
dafna33[m] has joined #dri-devel
dcbaker has joined #dri-devel
DemiMarieObenour[m] has joined #dri-devel
Anson[m] has joined #dri-devel
Guest683 has joined #dri-devel
doras has joined #dri-devel
danylo has joined #dri-devel
Dylanger has joined #dri-devel
egalli has joined #dri-devel
ella-0[m] has joined #dri-devel
Ella[m] has joined #dri-devel
AlexisHernndezGuzmn[m] has joined #dri-devel
GeorgesStavracasfeaneron[m] has joined #dri-devel
frytaped[m] has joined #dri-devel
gagallo7[m] has joined #dri-devel
gdevi has joined #dri-devel
gnustomp[m] has joined #dri-devel
Guest694 has joined #dri-devel
halfline[m] has joined #dri-devel
hasebastian[m] has joined #dri-devel
hch12907 has joined #dri-devel
heftig has joined #dri-devel
zzoon[m] has joined #dri-devel
jacobcrypusa[m] has joined #dri-devel
jasuarez has joined #dri-devel
jekstrand[m] has joined #dri-devel
jenatali has joined #dri-devel
JosExpsito[m] has joined #dri-devel
kallisti5[m] has joined #dri-devel
kunal10710[m] has joined #dri-devel
kunal_10185[m] has joined #dri-devel
kunal_1072002[m] has joined #dri-devel
KunalAgarwal[m][m] has joined #dri-devel
kusma has joined #dri-devel
LaughingMan[m] has joined #dri-devel
mairacanal[m] has joined #dri-devel
martijnbraam has joined #dri-devel
masush5[m] has joined #dri-devel
Mershl[m] has joined #dri-devel
michael5050[m] has joined #dri-devel
Mis012[m] has joined #dri-devel
moben[m] has joined #dri-devel
mripard has joined #dri-devel
Vin[m] has joined #dri-devel
naheemsays[m] has joined #dri-devel
neobrain[m] has joined #dri-devel
Newbyte has joined #dri-devel
eyearesee has joined #dri-devel
nielsdg has joined #dri-devel
nyorain[m] has joined #dri-devel
DavidHeidelberg[m] has joined #dri-devel
onox[m] has joined #dri-devel
pac85[m] has joined #dri-devel
PiGLDN[m] has joined #dri-devel
pmoreau has joined #dri-devel
pushqrdx[m] has joined #dri-devel
r[m] has joined #dri-devel
ralf1307[theythem][m] has joined #dri-devel
ramacassis[m] has joined #dri-devel
reactormonk[m] has joined #dri-devel
robertmader[m] has joined #dri-devel
robertfoss[m] has joined #dri-devel
sigmoidfunc[m] has joined #dri-devel
sjfricke[m] has joined #dri-devel
Strit[m] has joined #dri-devel
Sumera[m] has joined #dri-devel
knr has joined #dri-devel
T_UNIX has joined #dri-devel
tintou has joined #dri-devel
tleydxdy has joined #dri-devel
tomba has joined #dri-devel
Tooniis[m] has joined #dri-devel
undvasistas[m] has joined #dri-devel
Soroush has joined #dri-devel
unrelentingtech has joined #dri-devel
viciouss[m] has joined #dri-devel
MatrixTravelerbot[m]1 has joined #dri-devel
x512[m] has joined #dri-devel
xerpi[m] has joined #dri-devel
YaLTeR[m] has joined #dri-devel
yshui` has joined #dri-devel
zamundaaa[m] has joined #dri-devel
znullptr[m] has joined #dri-devel
pmoreau is now known as Guest703
tobiasjakobi has quit []
ella-0_ has joined #dri-devel
ella-0 has quit [Read error: Connection reset by peer]
fab has joined #dri-devel
Daanct12 has quit [Remote host closed the connection]
paulk has quit [Quit: WeeChat 3.0]
paulk has joined #dri-devel
paulk has quit []
paulk has joined #dri-devel
fahien has quit [Quit: fahien]
kts has joined #dri-devel
fab has quit [Quit: fab]
<javierm> daniels: I tried boot fedora with a kernel with CONFIG_VT disabled and so many components are not happy about it :)
<javierm> daniels: at least gdm, mutter, systemd-logind
<javierm> also tried with weston but also didn't like not having a VT
cengiz_io has joined #dri-devel
<pq> javierm, weston/DRM is happy without VTs at least on secondary physical seats.
kts_ has joined #dri-devel
<javierm> pq: it seems fedora ships an ancient weston version... weston-8.0.0-11.fc36.x86_64
<javierm> pq: I'm building now latest from main
<pq> yeah, I think main could work, even on the primary physcial seat. We had someone fixing it up when there are no ttys.
<javierm> pq: cool
<javierm> thanks for the pointer
kts has quit [Ping timeout: 480 seconds]
<pq> Looks like Weston 10.0.0 was the first release after some commits tested to run with CONFIG_VT=n.
<pq> not sure anyone tested it since
<javierm> pq: yeah, I had having an error before about no VT found. It seems was fixed by https://gitlab.freedesktop.org/wayland/weston/-/commit/72db3ac694c0f84f3c193df42e81be8329e52b61
<javierm> pq: I see. How can I start a seat0? Do I need seatd to be running?
<javierm> sorry if my questions are silly, I know nothing about weston :)
<pq> seat0 is the default unnamed seat
<javierm> pq: I see. But then probably systemd-logind didn't create it because it is complaining about missing VTs
<pq> possible, yeah
<javierm> Sep 16 13:36:40 fedora systemd-logind[620]: Failed to restore VT, ignoring: Bad file descriptor
<javierm> hmmm
<pq> also, it's really good question on *how* start something so that logind agrees to give access to seat0
<javierm> so I would have to fix that first then
<javierm> pq: right, so just running weston from a serial console wouldn't fly, right ?
<pq> you might have to have a systemd service unit for weston...
<pq> yeah, it wouldn't, because the serial console is not seat0
<javierm> pq: gotcha. Thanks for the info again, I'll investigate more
<pq> the same problem with ssh
<javierm> pq: the motivation here is to see how bad things go if we disable VT, so that we could just have a weston+terminal in the initrd to use it as a "VT"
<pq> and without root privileges, you can't commandeer "someone else's" physical seat
<javierm> right
<pq> cool
<pq> although it's all geared for running weston as a normal user
<pq> javierm, in Weston 10.0 series, the so called "launcher-direct" still exists, which was essentially means as a way to run weston as root without any helping daemons or weston-launch. We've removed it, because one shouldn't run as root.
<pq> *meant
<javierm> pq: Ok. Is https://git.sr.ht/~kennylevinsen/seatd the canonical repo for seatd ?
<javierm> I may use it instead of systemd-logind in the meantime since that's supposed to work
<pq> IIRC yes...
<javierm> pq: perfect, thanks again
<javierm> today is "learning day" at work so I thought that could give it a try to this :)
<pq> awesome :-)
<javierm> also wanted to try the drmlog patch that forwared ported to latest drm-misc-next
<javierm> but that's still missing a panic handler, is only the output part it seems
<pq> somehow I'm not surprised :-)
<javierm> :)
<pq> try setting SEATD_VTBOUDN=0 in env first
<pq> err...
<pq> try setting SEATD_VTBOUND=0 in env first
<pq> I need to use that too with my secondary phys.seat
<javierm> pq: ohhh, that was it!
<javierm> pq: this is so cool, I've weston + a terminal now running on seat0 without VT
<javierm> pq: thanks a lot for your help
<pq> \o/
<emersion> maybe seatd could detect that VTs are disabled, and automatically do the right thing in that case?
<pq> that would be nice
<emersion> would that be fragile? is there a good way to detect CONFIG_VT?
<pq> the existence of /dev/tty0 maybe?
itoral has quit []
<emersion> i've sent some doc improvements https://lists.sr.ht/~kennylevinsen/seatd-devel/patches/35360
<javierm> yes, I was about to say the same. If /dev/tty? doesn't exist, then VTs are not available to bound
<javierm> and can be assumed that SEATD_VTBOUND=0
<javierm> I may try to write a patch for seatd that does that
<emersion> is it possible for /dev/tty0 to not exist but /dev/tty1 to exist?
<javierm> emersion: I believe so yes, device number in Linux are not deterministic
<javierm> many user-space programs asume there are, but that's not really true
<pq> I don't think so. tty0 is the special "currently active tty, which ever it is".
<emersion> then we need to scan all of /dev?
<pq> tty1 is the first real tty
<emersion> can ttys be hot-plugged?
<emersion> so there could be no /dev/ttyN at all, but later on /dev/tty1 is created, or something
<pq> I wouldn't expect them to be hotpluggable, but who knows. You cannot CONFIG_VT=m, can you?
<javierm> emersion, pq: I believe that seatd can just use https://manpages.debian.org/stretch-backports/libsystemd-dev/sd_seat_can_tty.3.en.html
<javierm> and not really care about the details of tty?
<pq> ttys are not devices, so the device numbering races do not apply
<emersion> javierm: seatd does VT stuff on its own, it doesn't talk to logind
<emersion> libseat can talk to logind
<emersion> if you start seatd, libseat will use seatd instead of logind
<javierm> emersion: ah, Ok
<emersion> but, we can still look at the implementation of sd_seat_can_tty in systemd
<javierm> emersion: Ok
fahien has joined #dri-devel
<vsyrjala> allocating a new vt doesn't count as a hotplug?
<pq> javierm, btw. how do you do a serial console with CONFIG_VT=n? Does ttyS* still exist as usual?
<javierm> pq: yes, because CONFIG_VT is only about virtual terminals, not realy terminals like UARTs
<javierm> *real
<pq> vsyrjala, the question is more like, can tty0 appear or disappear at runtime.
<javierm> pq: I still have e.g: CONFIG_SERIAL_8250_CONSOLE=y
<pq> cool
<javierm> pq, emersion: have to leave for a while, thanks a lot for your help folks!
<javierm> I certainly learned a lot of things on my learning day :)
<emersion> i've asked kenny for advice
<pq> cool!
<emersion> :)
aravind has quit [Ping timeout: 480 seconds]
<vsyrjala> i guess just the presence of the devnode isn't a great test, if someone is using static /dev. i guess you'd have to poke it gently
<vsyrjala> and hope it has the right major/minor :P
kennylevinsen has joined #dri-devel
<pq> oh, indeed
<pq> try to open, try to query current VT number
* kennylevinsen sneaks into the chat
jfalempe has quit [Remote host closed the connection]
<emersion> vsyrjala: a static /dev?
jfalempe has joined #dri-devel
<jannau> emersion: no devtmpfs but device nodes created with mknod (potentially a long time ago and not tailored to the current system)
<emersion> hm
apinheiro has quit [Ping timeout: 480 seconds]
<kennylevinsen> Well, a check for /dev/tty0 and then an attempt to get VT mode would probably be a fine heuristic
hansg has joined #dri-devel
nehsou^ has quit [Remote host closed the connection]
<kennylevinsen> hmm, not sure actually: tty0 seems to only be special with CONFIG_VT=y: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/tty/tty_io.c#n1924
<kennylevinsen> might require some experimentation with a CONFIG_VT=n kernel
<pq> of course it is, right?
<pq> you mean some driver could register tty0 as something completely different than what tty0 is with VTs?
chipxxx has joined #dri-devel
kts_ has quit [Ping timeout: 480 seconds]
<vsyrjala> with mknod you can point anything anywhere. but i'm thinking if the user does that then they deserve whatever is going to happen next
<kennylevinsen> yeah, one might be able to register a tty driver that gets the /dev/tty0 spot, where tty_lookup_driver otherwise special-cases /dev/tty0 (rather, MKDEV(TTY_MAJOR, 0)) and always returns the `console_driver`
<kennylevinsen> haven't dug that far into this infrastructure before, so not sure
<vsyrjala> isn't the major/minor all fixed for the ancient stuff? so nothing else should legitimately appear there i think
<pq> vsyrjala, I mean, a kernel driver taking over the major,minor reserved for tty0 for something completely different.
<pq> I would say that's a driver bug if any driver did that.
<kennylevinsen> I don't think another non-tty driver taking over the major/minor would be allowed upstream, but the tty infrastructure is pluggable through tty_driver instances
<vsyrjala> well, the other case of user fumbling around with mknod is one of those "don't do that then" situations imo
chipxxx has quit [Ping timeout: 480 seconds]
chipxxx has joined #dri-devel
kts_ has joined #dri-devel
<pq> vsyrjala, yes, it is, but was not the issue here.
kts_ has quit []
chipxxx has quit [Read error: Network is unreachable]
bmodem has joined #dri-devel
bmodem has quit []
<kennylevinsen> okay, only console_driver uses /dev/ttyN. That's set up in vty_init (form tty_init) which is never called with CONFIG_VT=n. So just testing the path should be sufficient if we ignore people having fun with mknod.
<kennylevinsen> *from
<hansg> mripard, tzimmermann, I'm preparing a set of (acked) gma500 patches to merge into drm-misc-next but some of them will cause conflict with 1 of the gma500 fixes recently added to drm-misc-fixes. How do I resolve this? Can I just cherry-pick the fix from drm-misc-fixes in drm-misc-next before "dim apply-branch"-ing the new patches ?
<hansg> Note the patches as I send them out where based on top of the fixes, so cherry-picking the fix will also avoid me having to fix things up while applying (which potentially introduces errors which I would like to avoid too)
sravn has quit [Remote host closed the connection]
sravn has joined #dri-devel
kts has joined #dri-devel
Lucretia has quit []
mszyprow has joined #dri-devel
Lucretia has joined #dri-devel
<tzimmermann> hansg, cherrypicking should work. 'dim cherrypick' is the preferred way to do so
fxkamd has joined #dri-devel
cengiz_io has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
sdutt has joined #dri-devel
<daniels> javierm: btw it’s weston —shell=kiosk-shell.so, then the terminal emulator you want is foot
<ajax> patch to make getopt recognize em-dashes as --
<hansg> tzimmermann, thanks
Jeremy_Rand_Talos__ has quit [Remote host closed the connection]
Jeremy_Rand_Talos__ has joined #dri-devel
jewins has joined #dri-devel
JohnnyonFlame has joined #dri-devel
Guest694 is now known as frytaped
fxkamd has quit []
fxkamd has joined #dri-devel
saurabhg has joined #dri-devel
MajorBiscuit has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
tursulin has quit [Ping timeout: 480 seconds]
mszyprow has quit [Ping timeout: 480 seconds]
Company has joined #dri-devel
pa- has joined #dri-devel
saurabhg has quit [Ping timeout: 481 seconds]
pa has quit [Ping timeout: 481 seconds]
tzimmermann has quit [Quit: Leaving]
MrCooper has quit [Quit: Leaving]
nchery_ has joined #dri-devel
<ajax> is there a drm-shim for virgl?
<ajax> and/or some other way to use it without needing a whole qemu guest
nchery_ has quit [Remote host closed the connection]
nchery_ has joined #dri-devel
<bl4ckb0ne> is there a helper function whithin mesa to check the availability of any ext?
<bl4ckb0ne> i see theres _mesa_has_EXT_XXX but not for the one i want
<bl4ckb0ne> oh wait those are generated
<ajax> bl4ckb0ne: there should be one of those for everything that's optional
<ajax> right
chipxxx has joined #dri-devel
ybogdano has joined #dri-devel
nchery has quit [Ping timeout: 480 seconds]
fxkamd has quit []
MrCooper has joined #dri-devel
fxkamd has joined #dri-devel
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #dri-devel
Duke`` has joined #dri-devel
saurabhg has joined #dri-devel
<ajax> the answer is virglrenderer/build/test/virgl_test_server and GALLIUM_DRIVER=virpipe
<ajax> that could be better documented.
nchery_ has quit []
<airlied> ajax: just fyi the test protocol would need a fair bit work to be "production" ready :-P
nchery has joined #dri-devel
<ajax> killjoy
nchery has quit []
nchery has joined #dri-devel
pallavim has quit [Ping timeout: 480 seconds]
saurabhg has quit [Ping timeout: 480 seconds]
lemonzest has quit [Quit: WeeChat 3.5]
saurabhg has joined #dri-devel
<airlied> ajax: not sure how large a truck you could drive out of container through it
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
Dr_Who has joined #dri-devel
sdutt has quit []
sdutt has joined #dri-devel
MoeIcenowy has joined #dri-devel
<ajax> pigs fly just fine, given enough thrust
JohnnyonFlame has joined #dri-devel
<javierm> daniels: thanks for the info. I'll try to poke a little bit more next week
saurabhg has quit [Ping timeout: 480 seconds]
<Ristovski> I managed to capture the microstuttering in slowmo - https://pybin.pw/BFiV.mp4, notice how it becomes smooth once I start moving the mouse. If I switch to a tty and back the stuttering will be gone for some time, but eventually returns. any ideas? It happens both the active screens - one eDP and one HDMI
<Ristovski> i915/crocus on Gen75
mbrost has joined #dri-devel
<daniels> javierm: np!
sravn has quit [Ping timeout: 480 seconds]
sarahwalker has quit [Remote host closed the connection]
iive has joined #dri-devel
lemonzest has joined #dri-devel
mlankhorst has joined #dri-devel
ceyusa has joined #dri-devel
<ajax> airlied: anyone been insane enough to try a drm-cuse bridge? and teach it the virgl ioctls?
lynxeye has quit [Quit: Leaving.]
<ajax> are there any non-trivial cuse apps, one wonders
pa has joined #dri-devel
pa- has quit [Ping timeout: 480 seconds]
<MrCooper> ajax: osspd comes to mind
DemiMarieObenour[m] is now known as DemiMarie
mszyprow has joined #dri-devel
guru_ has quit []
rasterman has quit [Quit: Gettin' stinky!]
oneforall2 has joined #dri-devel
sravn has joined #dri-devel
devilhorns has quit []
DottorLeo has joined #dri-devel
<DottorLeo> hi!
slattann has quit [Quit: Leaving.]
jkrzyszt has quit [Ping timeout: 480 seconds]
slattann has joined #dri-devel
fahien has quit [Quit: fahien]
sravn has quit [Ping timeout: 480 seconds]
macromorgan is now known as Guest752
macromorgan has joined #dri-devel
macromorgan is now known as Guest753
macromorgan has joined #dri-devel
Guest752 has quit [Ping timeout: 480 seconds]
Dr_Who has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dv_ has quit [Quit: WeeChat 2.8]
Guest753 has quit [Ping timeout: 480 seconds]
jewins has quit [Ping timeout: 480 seconds]
<robclark> ajax: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16519 is kinda what you want.. although not sure if it is enough for virgl.. I had freedreno + drm native ctx working with it at least
jewins has joined #dri-devel
mszyprow has quit [Ping timeout: 480 seconds]
Dr_Who has joined #dri-devel
Dr_Who has quit []
Dr_Who has joined #dri-devel
DottorLeo has quit [Quit: Leaving]
Dr_Who has quit []
Dr_Who has joined #dri-devel
Dr_Who has quit []
Dr_Who has joined #dri-devel
Dr_Who has quit []
rasterman has joined #dri-devel
ngcortes has joined #dri-devel
ppascher has joined #dri-devel
Dr_Who has joined #dri-devel
kts has quit [Remote host closed the connection]
kem has quit [Ping timeout: 480 seconds]
Dr_Who has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mvlad has quit [Remote host closed the connection]
kem has joined #dri-devel
Dr_Who has joined #dri-devel
mbrost_ has joined #dri-devel
Dr_Who has quit []
mbrost has quit [Ping timeout: 480 seconds]
Dr_Who has joined #dri-devel
Dr_Who has quit []
Dr_Who has joined #dri-devel
<mdnavare> pq: vsyrjala:emersion: Currently I dont think we support VRR on DP MST so we havent handled the case where one CRTC is driving multiple monitors and one of them doesnt support VRR
<mdnavare> vsyrjala: But to answer my question about failing modeset if userspace requests VRR on a non VRR capable connector, is that an acceptable solution?
Dr_Who has quit []
Dr_Who has joined #dri-devel
Dr_Who has quit []
<turol> zmike: if you're profiling on an intel cpu you really should be using toplev from https://github.com/andikleen/pmu-tools/
Dr_Who has joined #dri-devel
slattann has quit []
DottorLeo has joined #dri-devel
chipxxx has quit [Read error: No route to host]
<DottorLeo> zmike, i've seen the new optimization for draw on Radv (now 44k) and ANV (now 71k). I'm curious, why there is such difference between them? GPU Architecture?
<DottorLeo> also your ANV will also affect the <Gen11+? I have a kabylake laptop :)
mszyprow has joined #dri-devel
Dr_Who has quit []
Dr_Who has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
<ajax> MrCooper: hadn't heard of that one, thanks
fab has joined #dri-devel
<vsyrjala> mdnavare: one crtc never drives multiple monitors on any platform since hsw. and no, i don't think we want to use the monitor caps when acceptint/rejecting properties. just opens up too many ways for things to fail
mszyprow has quit [Ping timeout: 480 seconds]
sravn has joined #dri-devel
DottorLeo has quit [Quit: Leaving]
hansg has quit [Quit: Leaving]
Dr_Who has quit []
fab has quit [Ping timeout: 480 seconds]
Dr_Who has joined #dri-devel
Dr_Who has quit []
jewins has quit [Ping timeout: 480 seconds]
Dr_Who has joined #dri-devel
jewins has joined #dri-devel
Dr_Who has quit []
lemonzest has quit [Quit: WeeChat 3.5]
LexSfX has quit []
LexSfX has joined #dri-devel
Dr_Who has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
Dr_Who has quit []
Dr_Who has joined #dri-devel
apinheiro has joined #dri-devel
Dr_Who has quit []
Dr_Who has joined #dri-devel
Dr_Who has quit []
vliaskov has quit [Remote host closed the connection]
warpme___ has quit []
Surkow|laptop has quit [Ping timeout: 480 seconds]
apinheiro has quit [Remote host closed the connection]
MajorBiscuit has joined #dri-devel
danvet has quit [Ping timeout: 480 seconds]
nchery has quit [Ping timeout: 480 seconds]
mbrost_ has quit [Ping timeout: 480 seconds]
nchery has joined #dri-devel
jfalempe has quit [Quit: Leaving]
MajorBiscuit has quit [Ping timeout: 480 seconds]
iive has quit [Quit: They came for me...]
RAOF has quit [Quit: Reconnecting]
RAOF has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
FireBurn has quit [Quit: Konversation terminated!]
<mdnavare> vsyrjala: Not while accepting properties, but should we reject this modeset in kernel if VRR requested on a non VRR cap monitor?
pcercuei has quit [Quit: dodo]