Shrinking the kernel with gcc
Posted Jan 23, 2004 8:34 UTC (Fri) by Duncan
In reply to: Shrinking the kernel with gcc
Parent article: Shrinking the kernel with gcc
> Now not only must you match up your kernel major version,
> but now you have to match up procedure calling strategies too.
> Do you think the average desktop user cares about this?
The practical effect on the NVidias of the world will be small, in any case. I
recently changed out an NVidia card for an ATI, because the libre ATI driver
does multiple video-outs per card, while the libre NVidia (NV) driver does not,
and I was tired of the hassle of having to recompile their driver every time I
recompiled the kernel, and of warnings about using an incompatible GCC, when
I compiled both with the SAME GCC, because of their stupid binary only stuff,
compiled with some GCC lagging the bleeding edge I'm accustomed to running.
I've vowed never to go back to hardware requiring binary only driver solutions.
Anyway, due to running NVidia's proprietary-ware solution for some time, I
know they release binary editions for each of the release versions of the major
distributions, often several for each, one for each kernel of each release. This
wouldn't change. They'd still end up having to make a different binary kernel
driver available for each kernel of each release, or force users to do their own
compiling. Nothing different there. The only difference would be one more
thing they'd have to check when doing their own compiling, behind the publicly
available drivers, and many of the kernel developers appear to be with me in not
caring about that. They are making their own boat, let them have to deal with
their own sea-worthiness!
I like the stricter controls on calls available to GPLed vs. non-GPLed modules in
the 2.6 kernel, as well, and am looking forward to 2.7 and beyond making
proprietary-ware driver suppliers lives even harder. By the time 2.7 goes stable
as 2.8 or 3.0, ideally, Linux will be used by a large enough percentage of the
computing world that hardware manufacturers will begin to have to think twice
about passing up the Linux segment, and open source will be driving the bargain
according to open source terms. That day is coming. Hardware suppliers have
been used to marching to the tune of MS. I can't believe they'll find it any
MORE difficult marching to the libre tune!
(Not a kernel hacker either, just a user that does his own kernel compiling, and
got tired of having to do a separate compile for all the hardware that wants to
force me to.. there's other hardware out there, and that's what I'll buy with
**MY** few $$!)
to post comments)