Originally posted by Kivada
View Post
Announcement
Collapse
No announcement yet.
Legacy Mesa Drivers Receive Their Death Sentence
Collapse
X
-
Originally posted by libv View PostAnd now for some facts...
intel i810 was releast in 1999. ATI R100 was released in 2000. The first VIA unichrome was announced in 2002 and i got it in the summer of 2003. Actual age has absolutely nothing to do with it.
Apart from the concerns i raised (i still did not see an answer to my questions about which criteria make a driver suitable for continued inclusion, nor about which drivers then actually remain -- both are questions to which apparently the answers are not helpful to the proposal)
where does this leave the X drivers or the drm drivers for these mesa drivers? Are they really thinking about _just_ the mesa bits, or is this the start of something bigger (it is of course something bigger, but they do not want to own up to it yet).
And where will this end: will we only have 3 manufacturers cards supported in future across the board, only for linux, and only if the hardware is just old enough to have support, but not old enough to have its support broken again?
Comment
-
-
Originally posted by Kivada View PostBut this is just the opinion of a non coding heathen, so as usual my opinion will be completely ignored.
OSS is *NOT* a democracy, its a meritocracy - as in, those who are willing to do the actual work, get to make the decisions.
As long as no-one jumps in and offer to maintain the old drivers himself, these drivers will simply die. Period. End-of-story.
So in short, yes, unless you are willing to pitch in, you opinions don't really matter. (Nor do mine )
- GilboaoVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.
Comment
-
Originally posted by gilboa View PostYou are missing the main point of OSS.
OSS is *NOT* a democracy, its a meritocracy - as in, those who are willing to do the actual work, get to make the decisions.
As long as no-one jumps in and offer to maintain the old drivers himself, these drivers will simply die. Period. End-of-story.
So in short, yes, unless you are willing to pitch in, you opinions don't really matter. (Nor do mine )
- Gilboa
It's almost as bad as the coder that wanted to drop support for the ISA bus, when tons of devices in current gen hardware still uses it.
Maybe they can't possibly fathom why someone would be using old hardware, perhaps they've forgotten that the vast majority of people out there that are using a computer are using one that is more then 5 years old, that Linux has long been the champion of old tech users since Windows EOLs and newer versions run like crap on old hardware.
I thought the game plan was to gain more market share, so as to make these OSS coder's skills more in demand allowing them to ask for more money when being picked up by an Intel or AMD. Isn't that the end goal? To get paid to write OSS code?
Comment
-
Originally posted by Kivada View PostWhile that may be the case many coders make it sound like these kinds of things can be kept going in less then 5 lines of code that they could do in their sleep, if that is in fact the case then how much time could it possibly take them just keep gimping it along?
It's almost as bad as the coder that wanted to drop support for the ISA bus, when tons of devices in current gen hardware still uses it.
Maybe they can't possibly fathom why someone would be using old hardware, perhaps they've forgotten that the vast majority of people out there that are using a computer are using one that is more then 5 years old, that Linux has long been the champion of old tech users since Windows EOLs and newer versions run like crap on old hardware.
I thought the game plan was to gain more market share, so as to make these OSS coder's skills more in demand allowing them to ask for more money when being picked up by an Intel or AMD. Isn't that the end goal? To get paid to write OSS code?
In the end, the Mesa devs needs to decide where their collective resources are better spent: Maintaining old (very, very) old hardware or better supporting new hardware.
Needless to say which one gets my vote.
However, again, if you really, really need old hardware support, why don't *you* do something about it?
- GilboaoVirt-HV1: Intel S2600C0, 2xE5-2658V2, 128GB, 8x2TB, 4x480GB SSD, GTX1080 (to-VM), Dell U3219Q, U2415, U2412M.
oVirt-HV2: Intel S2400GP2, 2xE5-2448L, 120GB, 8x2TB, 4x480GB SSD, GTX730 (to-VM).
oVirt-HV3: Gigabyte B85M-HD3, E3-1245V3, 32GB, 4x1TB, 2x480GB SSD, GTX980 (to-VM).
Devel-2: Asus H110M-K, i5-6500, 16GB, 3x1TB + 128GB-SSD, F33.
Comment
-
Originally posted by Kivada View PostWhile that may be the case many coders make it sound like these kinds of things can be kept going in less then 5 lines of code that they could do in their sleep, if that is in fact the case then how much time could it possibly take them just keep gimping it along?
Maybe they can't possibly fathom why someone would be using old hardware, perhaps they've forgotten that the vast majority of people out there that are using a computer are using one that is more then 5 years old, that Linux has long been the champion of old tech users since Windows EOLs and newer versions run like crap on old hardware.
I thought the game plan was to gain more market share, so as to make these OSS coder's skills more in demand allowing them to ask for more money when being picked up by an Intel or AMD. Isn't that the end goal? To get paid to write OSS code?
Comment
Comment