But that's not a hardware driver.
> It is not true in practice meaning there is utility in having a stable ABI.
That would benefit the people who are doing the wrong thing, at the expense of people who are doing the right thing.
It is still a kernel module.
>That would benefit the people who are doing the wrong thing, at the expense of people who are doing the right thing.
People are going to make out of tree kernel modules regardless. It is only the wrong way because there is not a stable ABI for doing it.
That's not really a good basis for defending closed drivers.
Yes it happens, but it is a scenario we should be trying to avoid.
Murder is going to happen, I would say we should try and prevent it, not just accept that it is going to happen. Yes, that attempt will never be 100% successful, but that isn't a reason not to try and prevent murders to start with.
I gave you an example of OpenZFS where this is not the case. The code in hardware drivers may not be owned entirely by the company. It could have even been done entirely by a third party which may not even still be in business. Even if they were willing to license there would be extra costs in making the code into a state that can be upstreamed. Even then it might just never be accepted.
>A company that asserts the existence of "trade secrets" in kernel modules deserves to have to do the extra work.
This is an unreasonable stance that hurts end users. If no one exists to maintain the kernel module end users will get stuck on old, insecure, kernel versions. Even if they get updated it prevents people from upgrading until there is a version all drivers support.
>All kernel modules should be open source.
That is your opinion. It is not true in practice meaning there is utility in having a stable ABI.