ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
RAOF has joined #dri-devel
keithboltzman has joined #dri-devel
yrlf has quit [Ping timeout: 480 seconds]
yrlf has joined #dri-devel
<keithboltzman>
if the order reliability will succeed, than division by two is both data bank assembly and access time well avoidable. cause the division by two is just half the index of the access appended to double value and that subtracted from 128. for example 256-144=112/2=56 so 256-144-56=56 128-56=72, so on access there are two values fetched 72 and 27 aka 144 and 56 after access was successful,
<keithboltzman>
but i am not sure if the access order reliability succeeds. I am starting to fire up the compiler over long time, calculator age is over now.
amarsh04 has quit []
u-amarsh04 has joined #dri-devel
u-amarsh04 has quit []
amarsh04 has joined #dri-devel
pcercuei has quit [Quit: dodo]
amarsh04 has quit []
keithboltzman has quit [Ping timeout: 480 seconds]
heat has quit [Read error: Connection reset by peer]
codingkoopa3218 has quit []
alanc has quit [Remote host closed the connection]
codingkoopa3218 has joined #dri-devel
alanc has joined #dri-devel
davispuh has quit [Ping timeout: 480 seconds]
yrlf has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
yrlf has joined #dri-devel
codingkoopa3218 has quit []
codingkoopa3218 has joined #dri-devel
The_Company has joined #dri-devel
Company has quit [Ping timeout: 480 seconds]
alane has quit []
alane has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
BILL_GATES_SUCKS_C0CK has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
BILL_GATES_SUCKS_C0CK has quit []
dsimic is now known as Guest11011
dsimic has joined #dri-devel
Guest11011 has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
QbY has joined #dri-devel
<QbY>
Hey everyone, Apologies for the off-topic message, but this is critical. Please download and save a copy of https://Histwo.github.io/lostOne.txt. Emailing a copy to yourself or others will create timestamped proof that it was in the public domain before the event described within. This file helps expose a political conspiracy that has already taken far too many lives and is about to escalate on a massive scale. Every saved copy
<QbY>
matters. Please don’t ignore this—your action could help save thousands. I'm literally surrounded by cloaked (invisible) gov and CIA. They are actively killing any of my communications, served Microsoft with an NSL for my email. The NSA folks watching me, do not know what I'm using. So.... Please help me and Atlanta. Thank you.
QbY has quit [Quit: Konversation terminated!]
NiGaR has quit [Remote host closed the connection]
NiGaR has joined #dri-devel
kts has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
Sid127 has quit [Ping timeout: 480 seconds]
caitcatdev has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
diego2 has left #dri-devel [#dri-devel]
Duke`` has joined #dri-devel
dviola has joined #dri-devel
Jeremy_Rand_Talos_ has quit [Remote host closed the connection]
Jeremy_Rand_Talos_ has joined #dri-devel
fab has joined #dri-devel
<llyyr>
why does this channel attract so many people like this
<airlied>
one of the largest channels on oftc
itoral has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
mehdi-djait3397165695212282475 has joined #dri-devel
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
jsa1 has joined #dri-devel
cascardo has joined #dri-devel
cascardo_ has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
glennk has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
<tarocards_for>
seems my manic episodes are never ending, i would not be surprised if the order never works out, why would not anyone else expose more memory alike otherwise? The depchain earlier giving some success, i do not think it does anything to preserve the correct order of those elements, it would need more work which might as well fail altogether in the end. I am doing stupid things.
tarocards_for has quit [Remote host closed the connection]
Low_Orbit_Michelson-Morley has quit []
KAL9000 has quit [Quit: KAL9000]
ircusernine has joined #dri-devel
<ircusernine>
i filtered out that only two solutions were ever doing something. nannybusiness and tramandtroll in logs, i lost my energy to test them for bigger order preserving sequences.
guludo has joined #dri-devel
ircusernine has quit [Remote host closed the connection]
kts has joined #dri-devel
sima has joined #dri-devel
nandersalis has joined #dri-devel
vjaquez has quit [Read error: Connection reset by peer]
vjaquez has joined #dri-devel
vjaquez has quit [Remote host closed the connection]
vjaquez has joined #dri-devel
<nandersalis>
I do not understand how to get more indexes without stretching the base very high, and hence have way higher inputs without collisions. so indexes start to go tremendously big going towards the max mem location storage capacity aka word length. One way is to access in tiles but that would add latency. so you access several 115 indexes, but one has base slightly higher , which would
<nandersalis>
translate the index more to 116 instead, and next iteration you access 115 from the tile etc. It's getting too complex, i will lose the battle on data compression i think, but i am getting some momentum, as i have more money to use next months.
kts has quit [Ping timeout: 480 seconds]
warpme has quit []
u-amarsh04 has joined #dri-devel
nandersalis has quit [Remote host closed the connection]
mehdi-djait3397165695212282475 has quit [Ping timeout: 480 seconds]
mszyprow has quit []
u-amarsh04 has quit []
nerdopolis has joined #dri-devel
warpme has joined #dri-devel
itoral has quit [Remote host closed the connection]
u-amarsh04 has joined #dri-devel
kts has joined #dri-devel
cheako has quit [Quit: Connection closed for inactivity]
tobiasjakobi has joined #dri-devel
FireBurn has quit [Remote host closed the connection]
kts has quit [Ping timeout: 480 seconds]
kts has joined #dri-devel
kts has quit []
The_Company has quit []
mripard has joined #dri-devel
cheako has joined #dri-devel
mehdi-djait3397165695212282475 has joined #dri-devel
mehdi-djait3397165695212282475 has quit []
mehdi-djait3397165695212282475 has joined #dri-devel
warpme has quit []
Sid127 has joined #dri-devel
caitcatdev has joined #dri-devel
fab has quit [Quit: fab]
Mangix has quit [Read error: Connection reset by peer]
accessgrantmeth has joined #dri-devel
Mangix has joined #dri-devel
<accessgrantmeth>
in calculator i got 64registers compressed into one memory location, rest of the testing needs to be compilation based, and the testing to stuff more into hash goes more complex.
<accessgrantmeth>
i just do not seem to understand how to address more yet entirely.
mripard_ has joined #dri-devel
mripard has quit [Ping timeout: 480 seconds]
frieder has quit [Remote host closed the connection]
<accessgrantmeth>
but another way to think is when one has collision, it would be the same value anyhow that one gets (so it appears in case of tramandtroll), another view is how many accesses is wanted to be done, so all elements or one should be stable in very high compression rates, but anything in between might get anomalies., cause the order that they would appear needs handling. the obvious thing
<accessgrantmeth>
what most do is to keep some os like supporting structures per hash. so if you would access sequential the thing you already accessed might be removed, depending on what access pattern or methology you chose.
epoch101 has joined #dri-devel
fab has joined #dri-devel
siak has quit []
vedm has joined #dri-devel
hexa- has quit [Quit: WeeChat 4.4.3]
hexa- has joined #dri-devel
epoch101 has quit [Ping timeout: 480 seconds]
tzimmermann has quit [Quit: Leaving]
davispuh has joined #dri-devel
Duke`` has joined #dri-devel
accessgrantmeth has quit [Remote host closed the connection]
accessgrantmeth has joined #dri-devel
accessgrantmeth has quit [Remote host closed the connection]
<alyssa>
hmm, so the v1 asahi uapi has a submit ioctl containing a command count and points to an array of command structs, and each command struct has a payload size and points to a payload
<alyssa>
wondering if it would make sense to flatten that?
<alyssa>
instead have submit point to a little "kernel command stream", where each command has a fixed size header followed by variable payload
<alyssa>
less pointer chasing (and just 1 big copy_from_user instead of N for N commands)
<alyssa>
although idk if it's precedented
guludo has quit [Quit: WeeChat 4.5.2]
guludo has joined #dri-devel
jsa1 has quit [Ping timeout: 480 seconds]
<pac85>
Looking at your code it seems like you need to pass a lot more stuff to the kernel than other drivers so I guess it makes sense it needs unique design?
<alyssa>
pac85: Yep
<alyssa>
Imaginapple is uniquely annoying here
<alyssa>
and Apple doubly so because we don't control the firmware
<alyssa>
(Imagination made a bunch of firmware changes to hide this in their mainline uapi. their downstream one is similar to ours.)
<alyssa>
frankbinns: ^
<alyssa>
cc
<pac85>
Uhm wonder what IMG does upstream. Do they just not need all the info anymore?
phasta has quit [Quit: Leaving]
<alyssa>
it's plumbed straight from userspace -> firmware
<alyssa>
which relies on a stable firmware abi
<alyssa>
which apple does not give us
<pac85>
uh I see makes sense, so kmd needs to hide the instability for asahi
<alyssa>
bingo
coldfeet has joined #dri-devel
warpme has joined #dri-devel
coldfeet has quit []
epoch101 has joined #dri-devel
checkfoc_us9 has quit []
checkfoc_us9 has joined #dri-devel
<zmike>
I've started working to flatten out pipe_surface pointers, in pipe_framebuffer_state and I'm starting to wonder whether this is actually feasible
<zmike>
it's a lot more work than I expected
mehdi-djait3397165695212282475 has quit []
mehdi-djait3397165695212282475 has joined #dri-devel
warpme has quit []
jhli has quit [Remote host closed the connection]
epoch101 has quit [Ping timeout: 480 seconds]
<mareko>
oh definitely
<alyssa>
since when has zmike ever backed down from a challenge
<zmike>
sweatytowelguy
lampswitchedon has joined #dri-devel
lynxeye has quit [Quit: Leaving.]
<zmike>
I got zink to build with it as a test
<lampswitchedon>
likely yeah i am severely ill in all ways, but this table i talked about which gives me results, nannybusiness gives similar results in shorter procedures, so this is tramandtroll that i paste here. 89+89+210-420=-32 -32+210+89+89=356 -32+210+89+89+210=566 566-356-356=-146 566-420=146
<zmike>
it was non-trivial but I think maybe there's a path to getting everyone using the same basic formula
<zmike>
and then everyone can clean up their drivers from there to whatever is more optimal
<alyssa>
yay!
jsa1 has joined #dri-devel
lampswitchedon has quit [Remote host closed the connection]
rasterman has quit [Quit: Gettin' stinky!]
MrCooper has quit [Remote host closed the connection]
goldinpocketX has joined #dri-devel
MrCooper has joined #dri-devel
rasterman has joined #dri-devel
<goldinpocketX>
so how that get's to results 86 is index 120 so 136-61-61=14+max72 in pseudo, so 89 is similarly 115 so 141-62-62=17+72=89 so for 120 index 200, comes as 256-72+16 and for 210 for 115 as 256-72+26, and you start to piece and puzzle those into those procedures consistently, and gives back the filtered selection bitshifted by four places. 14 if 72 is removed and 17 if 72 is similarly
<goldinpocketX>
removed. so 61+61=122 which comes as 136-14 and 62+62=124 which comes as 141-17. now there is a need for more work to address deeper than some one bank.
mehdi-djait3397165695212282475 has quit []
jkrzyszt has quit [Ping timeout: 480 seconds]
unerlige has joined #dri-devel
kj2 has quit [Quit: Connection closed for inactivity]
goldinpocketX has quit [Remote host closed the connection]
protestenviron has joined #dri-devel
<protestenviron>
now there are some combinations and we can get onto logics, if base is incrementing, the value max per bank is larger, hence the distance subtraced from max remains the same result, as before, however the 210 or 200 coeff would enlarge, which seems like perfect way of filtering, and if there is collision, that is going to be the very same value , there is some magic behind that
<protestenviron>
accidental fluke imo, it seems crazy efficient but requires a whole lot of testing yet more, maybe after years of testing we could release something but at the moment i can not guarantee anything, but would say it looks very interesting.
yrlf has quit [Ping timeout: 480 seconds]
yrlf has joined #dri-devel
unerlige has quit [Ping timeout: 480 seconds]
protestenviron has quit [Ping timeout: 480 seconds]
sumeriangod has joined #dri-devel
coldfeet has joined #dri-devel
haaninjo has joined #dri-devel
<sumeriangod>
yeah maybe both would rise, which is yet bit more logical as per example 115+72+257=444 514-444=70+257+115=885-768=117 70+72=142 4*257=1028-885=143-62-62=19 so 256-72+28=212 where 28 is 885+115=1000 1028-1000=28 but i do not understand why 257-230 now yields 27, some core programming issue, that next power is -1 of last so likely 27 is more correct so 256-72+27=211 whatever.
Kayden has quit [Quit: -> JF]
gouchi has joined #dri-devel
sumeriangod has quit [Remote host closed the connection]
fab has quit [Quit: fab]
jrayhawk has quit [Ping timeout: 480 seconds]
arkadiandevil has joined #dri-devel
<arkadiandevil>
the whole point is that when some testing is yet landed it could address so much memory that it makes everyone sick at best :D. The procedure reminds hardware gates to some degree, and appears to take care of things by filtering some bitshifted cancel outs, which is why it might even be reliable to some degree.
<arkadiandevil>
but the operating system access methology read write, reindex, read sequential and all such patterns i do not know well, which is where some more knowledged person could help us by commenting on something.
jrayhawk has joined #dri-devel
<airlied>
zmike: I've tried that before and given up
<airlied>
that TODO in pipe_surface was written in simpler times :-)
<zmike>
airlied: which todo?
<airlied>
whatever the one that says width/height will go away
<zmike>
oh
<zmike>
I already did that though
<airlied>
yeah I know, now I'm worried :-)
<zmike>
that one wasn't too bad
<airlied>
I thought those were use for non-fb rendering or whatever that thing is called
<zmike>
near as I can tell they're mainly used for shortcutting having to manually call u_minify
<airlied>
I assume you've ran this locally and resized a window a bunch of times :-)
<airlied>
because CI will not cover that I don't think
<zmike>
yeah seemed fine to me
<zmike>
there's no functional changes here
coldfeet has quit [Quit: Lost terminal]
<airlied>
I just pointed out one actual functional change on the MR
<airlied>
otherwise it seems fine
<zmike>
hm
<zmike>
technically those checks were invalid anyway since it's legal for drivers to adjust for e.g., blocksize
<zmike>
this MR effectively says "geometry is not a property of pipe_surface"
<zmike>
so you create one surface for a resource on a given format/mip/layer and that's it
<airlied>
there are also cases in lavapipe that smell iffy
<airlied>
the surface w/h do not come from the resource
<airlied>
they come from the API
<zmike>
right, they're based on the additional params
<airlied>
I kinda feel adding the pipe_surface_sizes then adding a bunch of asserts all over first and seeing if something explodes might be a better way to stage this
<airlied>
I think a full VK CTS run might catch something on lvp
arkadiandevil has quit [Remote host closed the connection]
Kayden has joined #dri-devel
<zmike>
I'm skeptical of your skepticism considering those values aren't actually used, and the zink job would surely have failed if there was an issue with something as simple as framebuffer ops
<zmike>
but I'm also not planning to land it until later in the week, so there's ample time to test
realdroneoperator has joined #dri-devel
rasterman has quit [Quit: Gettin' stinky!]
<realdroneoperator>
I do not think anyone was ever having interest in what i tried to prove either. But if i follow the current memory management code correctly
<airlied>
zmike: at least remove all the dead code in lavapipe in the patch series so you can see the fallout
Kayden has quit [Quit: Leaving]
<zmike>
which dead code are you referring to
<airlied>
those functions that take width/height and do nothing with them
<zmike>
ah
<zmike>
well sure, I can delete some params
hansg has joined #dri-devel
Leftmost has quit []
<zmike>
but you can see that llvmpipe never even used these struct members
<zmike>
mostly they just get pointlessly propagated
<zmike>
the real values are taken from the fb state
realdroneoperator has quit [Remote host closed the connection]
jsa1 has quit [Ping timeout: 480 seconds]
<airlied>
indeed maybe we just don't care what the frontend passes in (which is probably a bug somewhere)
<airlied>
I think u_blitter is where it matters if it does
epoch101 has joined #dri-devel
<zmike>
there was one function there where I had to manually add width/height params
<zmike>
but otherwise it was the same
<airlied>
no where it matters that the values from the frontend are passed in
<airlied>
and they won't match the resource
<zmike>
right, I'm saying I had to manually pass values through
epoch101_ has joined #dri-devel
epoch101 has quit [Ping timeout: 480 seconds]
YuGiOhJCJ has joined #dri-devel
gouchi has quit [Remote host closed the connection]
hansg has quit [Quit: Leaving]
bestpeanutbutter has joined #dri-devel
<bestpeanutbutter>
was that even consistent enough? mattst88: if you fire up a calclulator or some c/c++ code and get me some feedback on the thing or minor discussion about the procedures, I might and probably will leave from those channels. Though i am incredibly lonely and need to talk or write to avoid going around the country to start killing terrorists, but if i get some feedback that might help
<bestpeanutbutter>
me to stay quiet, so far out of series of hundreds of attempts 2methods have materialized and seem to be giving results, i got the nannybusiness method also to work. but those are the only ones, and i'd be shocked if someone found that those do not function like needed, cause all the series of proofs materialized into those, and i would currently bet theyd be a great start, but
<bestpeanutbutter>
indeed i have been so sick that maybe the chip deluded me out, but i hope not. I have not been able to find a mistake from those two.
tobiasjakobi has quit []
bestpeanutbutter has quit [Remote host closed the connection]
Duke`` has quit [Ping timeout: 480 seconds]
epoch101 has joined #dri-devel
epoch101_ has quit [Read error: Connection reset by peer]
epoch101_ has joined #dri-devel
epoch101 has quit [Ping timeout: 480 seconds]
feaneron has quit [Ping timeout: 480 seconds]
Company has joined #dri-devel
epoch101_ has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
ifeelunentire has joined #dri-devel
haaninjo has quit [Quit: Ex-Chat]
<ifeelunentire>
now you want stupidest guy on earth to stay or what? Mood fluctuation, well there is easily spottable mistake in the table, you can not eliminate this way, i end up eliminating both that way or have unknown unmanageable value in the hash. I offered the my deal to matt. But there might be a way to cause a pure distance multiplies subtracted from values manipulated, so i remember it
<ifeelunentire>
should come out as 32 and 64, which yet more subtracted from 210 and 420 would yield twice and four times the stuff needed. But this is very likely called wavelet transform. And is probably known in the art, it's little bit similar to fourier transform.