ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
<bnieuwenhuizen> but I dunno ...
<bnieuwenhuizen> can always fallback to a kernel submit if userspace submit fails?
<airlied> yeah that's what I was wondering does it need to do that etc
the_sea_peoples has quit [Quit: WeeChat 2.8]
sarnex has quit [Read error: Connection reset by peer]
sarnex has joined #dri-devel
sarnex has quit [Quit: Quit]
sarnex has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
iive has quit [Quit: They came for me...]
X512 has joined #dri-devel
<X512> jekstrand: I feel that direct-to-FW submission would be beneficial for non Linux open source operating systems such as FreeBSD and Haiku.
<X512> It allow to implement drivers fully in userspace without submission overhead.
<X512> And need less driver code.
<jekstrand> heh.... Not so much. :)
<jekstrand> It really doesn't reduce the size of the kernel implementation that much.
<bnieuwenhuizen> should implement it all in the GSP. That'll help other OSes :P
<jekstrand> You still have to do memory management, eviction, fault handling, pause/resume of contexts when you get over-subscribed, etc.
<X512> But 3D rendering hot path will not require calling kernel driver. So it can be used with microkernel OSes without performance loss.
pcercuei has quit [Quit: dodo]
<jekstrand> Yeah, it probably is better for microkernels
<airlied> but really there's 0 hope of them implementing all the other bits
<airlied> even with GSP there is a sizeable driver
<airlied> and that is probably the smallest x86 gpu kernel driver footprint you could achieve with any vendor
<HdkR> BO eviction and me aren't on good terms
<X512> nVidia open GPU driver have large benefit for other OSes that it is portable and can be easily compiled. The only thing need to be done is writing specific OS kernel interfacing code.
<X512> Unfortuneately other open source GPU kernel driver are hard coded to Linux private unstable kernel API.
<X512> Very bad that Linux don't want to use nVidia open GPU drivers as is and plan to reinvent the wheel with Linux hard coded driver.
<psykose> which ones are you referring to
nuh^ has joined #dri-devel
<X512> Yes.
<X512> nv-kernel.o and nv-modeset-kernel.o compiles on Haiku without problem.
<X512> Haiku may get better nVidia support that Linux because it have no DRM/GBM/implicit sync legacy :)
<psykose> the entire userspace that is usable for those is completely proprietary
<psykose> and it only supports new gpus
<psykose> very open yes
<X512> Recevnt open Vulkan nVidia VNK driver probably can be easily adapted to nVidia open GPU driver ioctl interface.
lemonzest has joined #dri-devel
<X512> Supporting older nVidia GPUs by open source seems hopeless because of unability to control power settings and GPU run at lowest performance.
<DavidHeidelberg[m]> X512: but by running older nvidia GPU you save the planet. It always run 100% ecologically on low gpu and mem freq :D
<DavidHeidelberg[m]> Also won't die because it won't overheat!
columbarius has joined #dri-devel
co1umbarius has quit [Ping timeout: 480 seconds]
alatiera5 has joined #dri-devel
<X512> Is it possble to know to which GPU dma_buf FD belong to?
Leopold__ has quit [Remote host closed the connection]
alatiera has quit [Ping timeout: 480 seconds]
jdavies_ has joined #dri-devel
Guest1992 has quit [Remote host closed the connection]
X512 has quit [Quit: Vision[]: i've been blurred!]
Jeremy_Rand_Talos has quit [Remote host closed the connection]
Jeremy_Rand_Talos has joined #dri-devel
Leopold has joined #dri-devel
alatiera5 has quit [Ping timeout: 480 seconds]
Company has quit [Read error: Connection reset by peer]
heat has quit [Ping timeout: 480 seconds]
sarnex has quit [Quit: Quit]
sarnex has joined #dri-devel
sarnex has quit [Remote host closed the connection]
sarnex has joined #dri-devel
Leopold has quit [Remote host closed the connection]
sarnex has quit []
sarnex has joined #dri-devel
sarnex has quit []
sarnex has joined #dri-devel
Leopold has joined #dri-devel
sarnex_ has joined #dri-devel
sarnex has quit [Read error: Connection reset by peer]
jdavies__ has joined #dri-devel
jdavies_ has quit [Ping timeout: 480 seconds]
sarnex_ has quit [Read error: Connection reset by peer]
sarnex has joined #dri-devel
sarnex_ has joined #dri-devel
sarnex has quit [Read error: Connection reset by peer]
sarnex_ has quit [Read error: Connection reset by peer]
sarnex has joined #dri-devel
sarnex has quit [Read error: Connection reset by peer]
sarnex has joined #dri-devel
sarnex has quit [Remote host closed the connection]
sarnex has joined #dri-devel
Hi-Angel has joined #dri-devel
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
Hi-Angel has quit [Ping timeout: 480 seconds]
gbelgurr has quit [Ping timeout: 480 seconds]
Hi-Angel has joined #dri-devel
kts has joined #dri-devel
alarumbe has quit [Read error: Connection reset by peer]
alarumbe has joined #dri-devel
cphealy has quit [Quit: Leaving]
pret7 has quit []
gbelgurr has joined #dri-devel
agd5f_ has joined #dri-devel
agd5f has quit [Ping timeout: 480 seconds]
dviola has left #dri-devel [#dri-devel]
dviola has joined #dri-devel
kts has quit [Quit: Leaving]
ice99 has joined #dri-devel
agd5f has joined #dri-devel
pret7 has joined #dri-devel
agd5f_ has quit [Ping timeout: 480 seconds]
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
agd5f_ has joined #dri-devel
agd5f has quit [Ping timeout: 480 seconds]
pret7 has quit [Ping timeout: 480 seconds]
pret7 has joined #dri-devel
Hi-Angel has quit [Ping timeout: 480 seconds]
Hi-Angel has joined #dri-devel
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
sghuge has quit [Remote host closed the connection]
ice99 has quit [Ping timeout: 480 seconds]
Duke`` has joined #dri-devel
Hi-Angel has quit [Ping timeout: 480 seconds]
agd5f has joined #dri-devel
agd5f_ has quit [Ping timeout: 480 seconds]
fab has joined #dri-devel
agd5f_ has joined #dri-devel
agd5f has quit [Ping timeout: 480 seconds]
kzd has quit [Quit: kzd]
YuGiOhJCJ has joined #dri-devel
alatiera5 has joined #dri-devel
<emersion> no
YuGiOhJCJ has quit [Remote host closed the connection]
YuGiOhJCJ has joined #dri-devel
Leopold has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
Company has joined #dri-devel
gouchi has joined #dri-devel
rasterman has joined #dri-devel
gekret005 has quit [Remote host closed the connection]
gekret005 has joined #dri-devel
srslypascal is now known as Guest2102
srslypascal has joined #dri-devel
Guest2102 has quit [Ping timeout: 480 seconds]
Dr_Who has quit [Read error: Connection reset by peer]
alatiera5 is now known as alatiera
rasterman has quit [Quit: Gettin' stinky!]
Hi-Angel has joined #dri-devel
Leopold_ has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
FireBurn has joined #dri-devel
pcercuei has joined #dri-devel
kts has joined #dri-devel
leo60228 has joined #dri-devel
leo60228- has quit [Ping timeout: 480 seconds]
FireBurn has quit [Ping timeout: 480 seconds]
genpaku has quit [Remote host closed the connection]
genpaku has joined #dri-devel
ppascher has quit [Ping timeout: 480 seconds]
danvet has joined #dri-devel
shsrfud has joined #dri-devel
heat has joined #dri-devel
djbw has quit [Read error: Connection reset by peer]
kts has quit [Quit: Leaving]
heat_ has joined #dri-devel
kts has joined #dri-devel
kts has quit [Remote host closed the connection]
sarnex has quit [Ping timeout: 480 seconds]
heat has quit [Ping timeout: 480 seconds]
fodasso has joined #dri-devel
sarnex has joined #dri-devel
<fodasso> Hello, sway/wayfire segfault here with any mesa higher than 22.2.3. Error message is: nvc0_screen_create:1093 - Base screen init failed: -19
<fodasso> Found this link: https://github.com/swaywm/sway/issues/7335 Why would my RTX 2060 not be compatible with newer mesa? There is even this new NVK driver that should be compatible?
FireBurn has joined #dri-devel
FireBurn has quit [Remote host closed the connection]
kts has joined #dri-devel
<fodasso> Indeed. Odd that it also affects the nvk/main branch by the nouveau team.
pendingchaos has quit [Ping timeout: 480 seconds]
Leopold___ has joined #dri-devel
Leopold_ has quit [Ping timeout: 480 seconds]
iive has joined #dri-devel
ice99 has joined #dri-devel
kts has quit [Quit: Leaving]
<pinchartl> airlied: danvet: how does drm-misc handle base branches that need to be merged through multiple trees ? tomba has a series that touches both media and drm, with a base branch on top of v6.2-rc1 with the common commits. can it be merged as-is in drm-misc-next, with additional patches applied on top with dim, or is there a different process ?
<danvet> pinchartl, coordinate with drm-misc maintainers, either they do the topic branch and send pull to the other tree, or they merge the topic branch
<danvet> and yes that sounds reasonable
<danvet> that = shared topic branch for the baseline commits and then the drm stuff in dim on top or something like that
<pinchartl> Mauro has acked all the patches in the base branch for merge through drm. there's a high chance the branch won't need to be merged in the media tree this time as I don't foresee any conflict, but in case last minute changes need to go there, it's good to be prepared
FireBurn has joined #dri-devel
kts has joined #dri-devel
shsrfud has quit [Read error: Connection reset by peer]
shsrfud has joined #dri-devel
kts has quit []
Leopold___ has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
Haaninjo has joined #dri-devel
Haaninjo has quit [Remote host closed the connection]
Haaninjo has joined #dri-devel
shsrfud has quit [Remote host closed the connection]
shsrfud has joined #dri-devel
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
sarnex_ has joined #dri-devel
sarnex has quit [Ping timeout: 480 seconds]
kzd has joined #dri-devel
pendingchaos has joined #dri-devel
freemin has quit [Remote host closed the connection]
Lucretia has quit [Read error: Connection reset by peer]
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
shsrfud has quit [Read error: Connection reset by peer]
nchery has quit [Remote host closed the connection]
nchery has joined #dri-devel
srslypascal has quit [Ping timeout: 480 seconds]
jluthra has quit [Remote host closed the connection]
jluthra has joined #dri-devel
nchery has quit [Ping timeout: 480 seconds]
nchery has joined #dri-devel
Leopold_ has quit [Ping timeout: 480 seconds]
pret7 has quit []
ice99 has quit [Ping timeout: 480 seconds]
gouchi has quit [Remote host closed the connection]
tobiasjakobi has joined #dri-devel
Leopold_ has joined #dri-devel
Hi-Angel has quit [Remote host closed the connection]
srslypascal has joined #dri-devel
tobiasjakobi has quit []
pret7 has joined #dri-devel
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
jewins has joined #dri-devel
Duke`` has joined #dri-devel
jewins1 has joined #dri-devel
jewins has quit [Ping timeout: 480 seconds]
Lucretia has joined #dri-devel
Leopold_ has quit [Ping timeout: 480 seconds]
jewins1 has quit [Ping timeout: 480 seconds]
Leopold_ has joined #dri-devel
jewins has joined #dri-devel
pcercuei has quit [Quit: dodo]
<DemiMarie> bnieuwenhuizen jekstrand: can direct-to-fw please be made optional, even when virtualizing? Because the lack of input validation is going to be a serious problem for those who are virtualizing for security.
<DemiMarie> X512: direct-to-FW will prevent microkernels from losing performance, but only if they trust the FW to properly validate its inputs. I have seen no evidence that the FW is trustworthy.
<DemiMarie> To quote alyssa: “I don't and you shouldn't”
fab has quit [Quit: fab]
<bnieuwenhuizen> if you don't trust the FW then non-direct-to-fw should be an issue since cmdbuffers are still interpreted by FW?
<bnieuwenhuizen> looks like direct-to-fw is not that different from existing paths to call secondary cmdbuffers
<jenatali> Demi: I think you might have an expectation that the kernel is doing validation. AFAIK it isn't. I don't think direct-to-fw changes anything from a validation/security perspective
Haaninjo has quit [Quit: Ex-Chat]
kts has joined #dri-devel