On Tue, 10 Jul 2018 11:38:21 +0200 Per Jessen email@example.com wrote:
Carlos E. R. wrote:
On 2018-07-10 11:10, Per Jessen wrote:
And mind, do all this every time there is a kernel update. Not nice.
When you are bleeding edge, there will always be blood :-)
Not in Leap...
Leap isn't bleeding edge though. Leap is bit further behind on the adaption curve. Dave is gingerly trying out the bleeding edge when he needs to use drivers yet to make it into the kernel. Having to rebuild after a kernel update is good practice :-)
Hmm, such niceties escape me, and I suspect also escape the developers involved. Is there a readable explanation anywhere of how the V4L project is supposed to work, from the point of view of a hardware manufacturer's programmers?
They're saying I need to use the latest version of the media subsystem. That sounds like it might be a fairly normal situation, and if so, is there an 'approved' way in openSUSE to do that?
What makes it more awkward in my case is that they use their own media-build repository, which while open source, appears to contain lots of scripts and potentially code that have been hacked about with somewhat. Plus they develop using ubuntu and centos, not opensuse. So the scripts don't run.
And I bought this card because I had read that TBS linux support was good ...