<ishitatsuyuki>
Since the change involves the fs subtree, do I need to split the patch and send it to the fs-devel mailing list too? New to kernel dev process so would appreciate any advice.
<emersion>
ishitatsuyuki: i'd probably split the patch in two (one for fs, one for drm) then cc both lists
<ishitatsuyuki>
I see, thanks
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
alyssa has joined #dri-devel
<alyssa>
ccr: NIR!
<ccr>
oh, what sad times are these when passing developers can say "NIR" at will on IRC channels. there is a pestilence upon this land, nothing is sacred. even those who arrange and design open source graphics libraries are under considerable economic stress period in history.
* ccr
should've put some more thought and effort in that paraphrasing pun.
<alyssa>
....did anyone get into Mesa dev for the money? :-p
<ccr>
what, it isn't the rockstar life I've imagined it to be? @__@
<alyssa>
you're looking for #asahi over yonder -->
<ccr>
:)
Daanct12 is now known as Danct12
gouchi has quit [Remote host closed the connection]
MajorBiscuit has joined #dri-devel
mszyprow has joined #dri-devel
cworth has quit [Quit: Leaving]
lstrano has quit [Read error: Connection reset by peer]
Akari has quit [Quit: segmentation fault (core dumped)]
rasterman has joined #dri-devel
Akari has joined #dri-devel
Akari has quit [Quit: segmentation fault (core dumped)]
Akari has joined #dri-devel
mszyprow has quit [Ping timeout: 480 seconds]
Company has joined #dri-devel
JohnnyonFlame has quit [Ping timeout: 480 seconds]
Lyude has quit [Quit: WeeChat 3.3]
sdutt has joined #dri-devel
utf16 has quit []
Lyude has joined #dri-devel
agd5f has quit [Ping timeout: 480 seconds]
Wally has joined #dri-devel
Wally has quit [Remote host closed the connection]
boistordu_ex has quit [Ping timeout: 480 seconds]
boistordu has joined #dri-devel
eukara has quit [Read error: No route to host]
Haaninjo has quit [Quit: Ex-Chat]
ella-0 has joined #dri-devel
xlei has quit [Remote host closed the connection]
xlei has joined #dri-devel
ella-0 has quit [Read error: Connection reset by peer]
ella-0 has joined #dri-devel
JohnnyonFlame has joined #dri-devel
Akari has quit [Quit: segmentation fault (core dumped)]
Akari has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
JohnnyonFlame has quit [Ping timeout: 480 seconds]
xxmitsu_ has quit [Remote host closed the connection]
xxmitsu has joined #dri-devel
xxmitsu_ has joined #dri-devel
xxmitsu has quit []
xxmitsu_ has quit []
xxmitsu has joined #dri-devel
gouchi has joined #dri-devel
gouchi has quit [Remote host closed the connection]
Wally has joined #dri-devel
<Wally>
Will Mesa continue to support GCN?
<FLHerne>
Definitely
<FLHerne>
Mesa still supports R300 cards from 2002
<FLHerne>
(or R100 cards from 2000, but those are being relegated to the 'amber' maintenance-only branch from next release)
<FLHerne>
even GCN 1.0 is supported by the same `radeonsi` and `radv` drivers as the latest AMD cards, so there's no prospect of it being dropped any time soon
<kisak>
Wally: is there any particular reason why you thought it was going away?
cki has joined #dri-devel
<Wally>
kisak: AMD dropped support for it
<kisak>
the Proprietary driver may have, which is unrelated to the open source driver stack.
<Wally>
So my 7950 will still get support for the latest vulkan apis while the proprietary drivers wont?
<Wally>
or it it just bug fixes?
<kisak>
whatever the mesa/RADV developers can figure out for that generation.
<Wally>
oh
<imirkin>
Wally: there's a difference between "drop support" and "don't develop new support"
<imirkin>
the former will happen only very rarely, and generally _way_ after the "best by" date of the hardware
heat has joined #dri-devel
<imirkin>
the latter can happen very easily. these things don't write themselves.
<Wally>
I mean the latter
<imirkin>
the deal with vulkan is that you must use the 'amdgpu' kernel driver. the 'radeon' driver does not have a UAPI which allows vulkan to be implemented.
<imirkin>
iirc there was some confusion around which GPUs are supported by what. iirc the GCN1 GPUs were better supported by 'radeon'
<imirkin>
but then that means no vk.
<FLHerne>
So far I don't think there's much difference in feature support in radv for GCN vs RDNA cards?
<FLHerne>
there's even raytracing for the GCN cards, even though it's ludicrously slow because there's no dedicated hardware
<Wally>
So on my vega laptop I can enable rt in games that support it?!?!?
<FLHerne>
but it will be unplayably slow for absolutely everything
<Wally>
Im playing quake 2 rn
<FLHerne>
You have to export some env var
<FLHerne>
RADV_PERFTEST=rt I think
<FLHerne>
It works on Quake 2 RTX according to the MR comments
<FLHerne>
but as above, there's 0 chance of it working at a playable framerate
<FLHerne>
it's useful for testing shaders
<Wally>
Anyway, back to GCN,for vulkan imirkin seems to imply I need the amdgpu kernel driver
<FLHerne>
Ye
<jekstrand>
Wally: It depends on what features the hardware support and what kind of feature it is.
<Wally>
is that a proprietary kernel driver?
<FLHerne>
*Yes
<FLHerne>
No
<FLHerne>
You do need it, it isn't proprietary
<jekstrand>
Even the latest Vulkan versions can run on the same hardware as Vulkan 1.0.
<FLHerne>
It's default for GCN 1.2 and up
<Wally>
Oh, does it come with the kernel?
<jekstrand>
So it will probably get 1.3, 1.4, etc. until RADV forks off a stable branch.
<FLHerne>
For GCN 1.0 and 1.1, it's not the default because it doesn't support VGA [or analogue DVI which is the same] output and some of those cards have that
<jekstrand>
But whether or not it will get feature X depends on hardware, the feature, and how much effort it is.