<passimoto>
construct lists; it takes as arguments a function from X to Y and a
<passimoto>
list over X in that order. The value that is returned is a list of
<passimoto>
values in Y. The argument list may be a set or an integer_interval.""" ;
<passimoto>
math-meta:example _:n421
<passimoto>
that function seems to read out as very interesting for the earlier offered compressor
<passimoto>
I've been looking into rdf and w3 docs in this weekend, gotta say its very large set of languages .
warpme has joined #dri-devel
<passimoto>
in other words you can add a function to all of the list, and can select the interval of interest, it's very succinct but very expressive language but it is beneficial to get into some IR from that.
passimoto has quit [Quit: Leaving]
warpme has quit []
warpme has joined #dri-devel
Leopold__ has quit [Remote host closed the connection]
kugel is now known as Guest2343
kugel has joined #dri-devel
Leopold_ has joined #dri-devel
Guest2343 has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
Kayden has quit [Ping timeout: 480 seconds]
bolson has quit [Remote host closed the connection]
Duke`` has joined #dri-devel
davispuh has joined #dri-devel
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
gouchi has joined #dri-devel
gouchi has quit []
hansg has joined #dri-devel
sima has joined #dri-devel
glennk has joined #dri-devel
kts has quit [Quit: Leaving]
kts has joined #dri-devel
warpme has quit []
warpme has joined #dri-devel
amarsh04 has quit []
warpme has quit []
u-amarsh04 has joined #dri-devel
warpme has joined #dri-devel
warpme has quit []
chaos_princess has quit [Quit: chaos_princess]
chaos_princess has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
sukuna has quit [Remote host closed the connection]
junaid has quit [Remote host closed the connection]
fab has joined #dri-devel
zxrom has joined #dri-devel
warpme has joined #dri-devel
kts has joined #dri-devel
warpme has quit []
warpme has joined #dri-devel
warpme has quit []
warpme has joined #dri-devel
warpme has quit []
u-amarsh04 has quit []
simondnnsn has quit [Read error: Connection reset by peer]
ninjaaaaa has quit [Write error: connection closed]
simondnnsn has joined #dri-devel
a1batross has joined #dri-devel
ninjaaaaa has joined #dri-devel
warpme has joined #dri-devel
glennk has quit [Ping timeout: 480 seconds]
Arsen has quit [Quit: Quit.]
Arsen has joined #dri-devel
Arsen has quit []
Arsen has joined #dri-devel
warpme has quit []
warpme has joined #dri-devel
kts has quit [Quit: Leaving]
ghishadow has joined #dri-devel
warpme has quit []
kts has joined #dri-devel
rasterman has joined #dri-devel
ghishadow has left #dri-devel [#dri-devel]
glennk has joined #dri-devel
kzd has joined #dri-devel
hansg has quit [Quit: Leaving]
warpme has joined #dri-devel
Company has joined #dri-devel
junaid has joined #dri-devel
illwieckz has quit [Ping timeout: 480 seconds]
anujp has joined #dri-devel
illwieckz has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
cheako has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
junaid has quit [Remote host closed the connection]
<ity>
Hi, I am a bit confused about the architecture of gallium, is there docs somewhere I can read about what does what? Just like, a high level overview of what's what in src/gallium/
atipls has quit [Remote host closed the connection]
atipls has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
atipls has quit []
KDDLB0 has quit []
KDDLB0 has joined #dri-devel
warpme has quit []
atipls has joined #dri-devel
heat is now known as Guest2373
heat has joined #dri-devel
Guest2373 has quit [Read error: Connection reset by peer]
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
Haaninjo has joined #dri-devel
<FLHerne>
airlied/ity: the first section of that being a long section on TGSI doesn't bode well for up-to-dateness
<ccr>
:) "TGSI is the only intermediate representation used by all drivers."
<ity>
That seems to mostly be for some specific parts...? Unless I am misreading... It doesn't seem to describe eg what frontends or targets are
Marcand has joined #dri-devel
simon-perretta-img has quit [Read error: Connection reset by peer]
simon-perretta-img has joined #dri-devel
<Company>
gallium feels like one of those abstractions that drifts rather quickly in its semantics - because it's an abstraction inside Mesa for common things in drivers - and the moment you add a new driver or even just a new generation of hardware to an existing driver, things that were common suddenly aren't anymore or vice versa
<alyssa>
this is a feature
<Company>
yeah
<Company>
I'm pointing that out because it's hard to document
<alyssa>
ah yes well
<Company>
and documentation quickly ends up out of tdate
<alyssa>
"just copy iris"
<Company>
like, a blog post from 2022 might describe a gallium feature that doesn't exist anymore
* Company
far from an expert, he just tried to understand the YUV handling/GLES external texture stuff once
macromorgan has joined #dri-devel
kawaiidoscope has joined #dri-devel
kawaiidoscope has quit []
<Ristovski>
Huh, why are {MC,SDMA,VCN,JPEG,IH} clock gatings disabled on gfx90c/renoir when they are clearly enabled for GC 9.3.0 (which is present)? Peculiar
<Ristovski>
Unless of course they are enabled but the mechanism that enables them isn't even present :) (ala `soc15_common_set_powergating_state` being "todo")
i509vcb has joined #dri-devel
<airlied>
ity: yeah stuff has move around since then, but what's in src/gallium vs what is src/gallium/frontends are different questions
<airlied>
you might need to figure out a bit more specific questions to ask
<airlied>
I doubt anyone understands what is src/gallium in its entirety and nobody should need to know that to work on t
<airlied>
on it
Marcand has quit [Ping timeout: 480 seconds]
<ity>
I am not really sure what I am looking at there effectively. Like, for example, what about OpenGL drivers? What's the path there? There's also a software rasterizer, and also Zink, right...? I am really confused as to like, what's the structure, where to look for what. I don't have specific questions rn, I am just trying to orient myself
<airlied>
ity: opengl is under src/mesa
<airlied>
ity: otherwise gallium has frontends and drivers and the include files bind them together
<airlied>
and targets are the final linkage off the pieces
<airlied>
winsys is part of drivers that connect to the kernel drivers and is meant to be an abstraction (but not every driver does it)
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
crabbedhaloablut has quit []
tristianc6704 has quit []
crabbedhaloablut has joined #dri-devel
tristianc6704 has joined #dri-devel
junaid has quit [Remote host closed the connection]
Kayden has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
tristianc6704 has quit []
tristianc6704 has joined #dri-devel
sima has quit [Ping timeout: 480 seconds]
tanty has quit [Quit: Ciao!]
tanty has joined #dri-devel
tanty has quit []
tanty has joined #dri-devel
<jenatali>
ity: Right, GL is split into two pieces. The main bits are not under src/gallium since until recently, they weren't strictly a gallium frontend. The other GL bits are in the frontends folder and are for GLX/EGL/WGL
<jenatali>
But yeah specific question about "what is..." or "where is..." are easier. Gallium is really just an interface which looks a lot like D3D10 (or at least used to) which frontends translate to, and drivers translate from
karolherbst_ has joined #dri-devel
apinheiro has quit [Quit: Leaving]
kzd has quit [Quit: kzd]
karolherbst has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
karolherbst has joined #dri-devel
karolherbst_ has quit [Ping timeout: 480 seconds]
<mareko>
do you remember when we called frontends "state trackers"