On 26/2/18 1:12 am, Patrick O'Callaghan wrote:
On Sun, 2018-02-25 at 13:00 +1100, Stephen Morris wrote:
On 25/2/18 12:15 am, Patrick O'Callaghan wrote:
On Sat, 2018-02-24 at 15:43 +1100, Stephen Morris wrote:
Are all these taint messages, and all the reasons for a taint message
being produced saying that if we have to build our own drivers into the
kernel to be able to use our hardware, and hence put us into the
situation of potentially not getting support for kernel defects if any
are encountered, that we shouldn't be using linux?
If you encounter a kernel defect, how can it be debugged if part of the
kernel is not available? That's what tainting amounts to. IIRC you've
said that you compile the Nvidia modules. What you are actually doing
is compiling code (the dkms system) that enables Nvidia's binary blobs
to be linked as modules into the Linux kernel. You don't (unless you
work for Nvidia) have the source code of those blobs.
I can understand objects being linked together to build an executable
module, but what I don't understand, based on what you are saying, is
where the source code in the nvidia directory in /usr/src that dkms is
compiling has come from if it hasn't come from nvidia?
No-one is saying it doesn't come from Nvidia. What I'm saying is that
that code is *not* the entire Nvidia driver, it's simply linking code
that enables the use of the binary driver they supply.
IOW you don't have the *complete* source of the driver. That's why it's
tainted.
Thanks Patrick, I guess the link process after the compile is pulling in
modules from the libraries packages.
regards,
Steve
poc
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
