I'm sure if bridgman wasn't in the way all the time, r600g would be in a much better state. I wish this kid would just go away..
Announcement
Collapse
No announcement yet.
Radeon Gallium3D Still Long Shot From Catalyst
Collapse
X
-
Originally posted by bridgman View PostThat's like putting my pickup truck in my pocket so it's always there when I need it
if you don't use analogies if you use "Bit" it just doesn’t mater the PLACE of the bits doesn’t matter because they are there anyway!
in other words you just use rhetorical tricks to don't admit my argument.
Originally posted by bridgman View PostThe open source userspace stack is >10x the size of the kernel driver,
after this "Fix" the linux kernel is 10x larger really who cares? no one cares !
the bit size of the kernel source doesn't care!
the bits are in the system anyway!
you save ZERO!
Originally posted by bridgman View Postand the proprietary userspace stack is >50x and approaching the size of the entire Linux kernel.
Originally posted by bridgman View PostI don't think there would be a lot of joy among the kernel developers if we tried to move all that into kernel space.
if he say no then its no.. but your speculations is just FUD!
Originally posted by bridgman View PostThe multimedia API framework is quite different between Android and X/Wayland. They may converge over time but right now they are very different.
you can also work to get a long time run.
over long time this is the best way to fix the linux fragmentation.Last edited by Qaridarium; 03-25-2012, 03:20 PM.Phantom circuit Sequence Reducer Dyslexia
Comment
-
I figured out how to make radeon better than catalyst: every time quaridarium writes some bullshit, instead of wasting your time replying you should write a couples of lines of code. At such a pace I'm pretty sure radeon will double catalyst's performance in no more than a month.## VGA ##
AMD: X1950XTX, HD3870, HD5870
Intel: GMA45, HD3000 (Core i5 2500K)
Comment
-
Originally posted by bridgman View PostThat is a *great* idea !
20 years ago the kernel source was so much smaller maybe we should use a time travelling engine to go back in time to be sure the kernel source is smaller...
this is just bullshit!
and hey don't write code this makes the kernel source bigger ans we all know this is "bad" LOL
Bridgman bullshit logic at work..Phantom circuit Sequence Reducer Dyslexia
Comment
-
Originally posted by Qaridarium View Postsure but your argument about the kernel source size is still bullshit.
20 years ago the kernel source was so much smaller maybe we should use a time travelling engine to go back in time to be sure the kernel source is smaller...
this is just bullshit!
and hey don't write code this makes the kernel source bigger ans we all know this is "bad" LOL
Bridgman bullshit logic at work..
I think what you're suggesting is to move all of the 3D stack into the kernel. This would include the GLSL compiler and a lot of other core-Mesa components. The GLSL compiler, for instance, is C++ which is a no-go for the kernel. Then there's that you can't do floating-point operations in the kernel, which are obviously quite important for OpenGL.
Also there's the issue of security -- moving thousands of lines of code into kernel space...
Comment
-
Originally posted by mattst88 View PostSize isn't the only factor to consider in something like this.
I think what you're suggesting is to move all of the 3D stack into the kernel. This would include the GLSL compiler and a lot of other core-Mesa components. The GLSL compiler, for instance, is C++ which is a no-go for the kernel. Then there's that you can't do floating-point operations in the kernel, which are obviously quite important for OpenGL.
Also there's the issue of security -- moving thousands of lines of code into kernel space...
LOL there is no real GLSL compiler. you can rewrite this sad piece .
the status for the GLSL compilers for the r600 are "Sad" and yes maybe we will never get a good VLIW compiler. this means its a death horse.
"Then there's that you can't do floating-point operations in the kernel, which are obviously quite important for OpenGL."
you miss an important step in your argument why should this be a no go?
or do i have to ask linus ? LOLPhantom circuit Sequence Reducer Dyslexia
Comment
-
There's a serious inability on your part to participate in a reasonable discussion. I probably shouldn't bother responding, but I'll do it only once more given the lack of meaningful response.
Originally posted by Qaridarium View Post"The GLSL compiler, for instance, is C++ which is a no-go for the kernel."
LOL there is no real GLSL compiler. you can rewrite this sad piece .
the status for the GLSL compilers for the r600 are "Sad" and yes maybe we will never get a good VLIW compiler. this means its a death horse.
It's C++.
You're incorrectly thinking about the piece of r600g that translates some IR to hardware instructions.
Originally posted by Qaridarium View Post"Then there's that you can't do floating-point operations in the kernel, which are obviously quite important for OpenGL."
you miss an important step in your argument why should this be a no go?
or do i have to ask linus ? LOL
I'll assume it's the latter and waste a bit more of my time explaining it to you.
From the kernel documentation (http://git.kernel.org/?p=linux/kerne...g.tmpl;hb=HEAD)
Code:No floating point or MMX The FPU context is not saved; even in user context the FPU state probably won't correspond with the current process: you would mess with some user process' FPU state. If you really want to do this, you would have to explicitly save/restore the full FPU state (and avoid context switches). It is generally a bad idea; use fixed point arithmetic first.
Comment
-
Originally posted by bridgman View Postfor the next generation we are starting sufficiently early that we should be able to hide both development and review in the pre-launch window where it doesn't impact users or community developers
Comment
-
Originally posted by mattst88 View PostThere's a serious inability on your part to participate in a reasonable discussion. I probably shouldn't bother responding, but I'll do it only once more given the lack of meaningful response.
Originally posted by mattst88 View PostThe GLSL compiler, you know, the one that Intel wrote? http://cgit.freedesktop.org/mesa/mesa/tree/src/glsl
It's C++.
the solution is easy just put the intel shit into the garbage.
we need a AMD/VLIW compiler ! and not a intel JOKE.
the intel compiler is not VLIW ! you only get 1/5 of the speed with amd hardware this is just an FUD attack from intel on AMD!
Originally posted by mattst88 View PostI can't tell if that's a particularly sad attempt to dodge a very real difficulty of moving user space code into the kernel, or if you actually don't understand.
I'll assume it's the latter and waste a bit more of my time explaining it to you.
From the kernel documentation (http://git.kernel.org/?p=linux/kerne...g.tmpl;hb=HEAD)
Code:No floating point or MMX The FPU context is not saved; even in user context the FPU state probably won't correspond with the current process: you would mess with some user process' FPU state. If you really want to do this, you would have to explicitly save/restore the full FPU state (and avoid context switches). It is generally a bad idea; use fixed point arithmetic first.
now what? more FUD from your side?Phantom circuit Sequence Reducer Dyslexia
Comment
Comment