On 22.05.22 19:26, Suse User wrote:
So, a month since the latest message in this thread, the summary is:
1. There is a binary blob in the form of "table" which Larry somehow separated in a binary file and there is no way around this obfuscated code/data.
2. The upstream version of the driver is quite old and there is something which can be improved.
Well, it is not like the driver is unmaintained upstream. It has not yet made it from staging into the "good" drivers section, but it is worked on in regular intervals. Just look at the git changes. The version number does not mean anything as I tried to explain to you several times. It was just never updated after the driver was incorporated in the upstream kernel in 2013.
I hope someone (Larry?) can have a look at the newer version and consider to update the driver upstream (if it is better), because building it manually on each system update is a time consuming process:
If you want this to happen, it would probably be useful to state what works with the "newer" driver that does not work with the in-kernel driver. Just the updated version number does not provide anything useful. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman