what’s the use case for needing to support hardware that old on a modern kernel? only thing I can think of would be industrial, but theres no way 25 year old hardware is in use anywhere outside of a museum/retro-enthusiasts house, certainly not commercially.
On the flip side, why remove support if it is not causing major maintenance problems? I bet the code for these has not needed to be touched for a long time.
Removing very old stuff might make it easier to change other things that are still used by other drivers. Let’s say that both 3dfx and Geforce FX (2003 cards) call the same functions. Let’s say that the function to display a texture has 2 different sets of code, one to deal with the older 3dfx, another for the geforce. If you no longer need to support the 3dfx, you can also remove the whole set of code it needed, possibly making things slightly faster for the rest, as it’ll no longer have to check for a 3dfx card. You can also add something you couldn’t before, due to the limitations of the “minimal” card expected
Drivers are optionally compiled in Linux, if they default to off then they are not built or distributed to end users. Or if they are compiled as external modules they can be put in optional packages that most don’t need to download.
But yeah, eventually it can be good to remove old stuff. But ideally only after no one else is using it. Which isbwhy they leave things in for longer periods of time.
what’s the use case for needing to support hardware that old on a modern kernel? only thing I can think of would be industrial, but theres no way 25 year old hardware is in use anywhere outside of a museum/retro-enthusiasts house, certainly not commercially.
so… why wasnt support dropped 15 years ago?
On the flip side, why remove support if it is not causing major maintenance problems? I bet the code for these has not needed to be touched for a long time.
Removing very old stuff might make it easier to change other things that are still used by other drivers. Let’s say that both 3dfx and Geforce FX (2003 cards) call the same functions. Let’s say that the function to display a texture has 2 different sets of code, one to deal with the older 3dfx, another for the geforce. If you no longer need to support the 3dfx, you can also remove the whole set of code it needed, possibly making things slightly faster for the rest, as it’ll no longer have to check for a 3dfx card. You can also add something you couldn’t before, due to the limitations of the “minimal” card expected
that’s true, it’s probably very stable - but more code increases the total size of the package delivered.
Drivers are optionally compiled in Linux, if they default to off then they are not built or distributed to end users. Or if they are compiled as external modules they can be put in optional packages that most don’t need to download.
But yeah, eventually it can be good to remove old stuff. But ideally only after no one else is using it. Which isbwhy they leave things in for longer periods of time.