Blumenkrantz Flushes 17.1k Lines Of Old Mesa Code

[Quackdoc]

Are you sure? What about libcamera?

libcamera would sit above V4l2 or the new CAM api iirc

[Amaranth]

The only way V4L2 is going to be "replaced" is for something that takes its place that leaves the current V4L2 API in place unchanged. This means any new reworks of V4L2 would start by refactoring existing code and extending the API rather than altering the API already there. Linus is not going to allow user space breakage of that magnitude. (He generally doesn't allow any user space breakage into his kernel tree.) Any new drivers that wouldn't be able to exist inside the V4L2 will just add another user space API. Anything needing to make use of the new API calls would have to be written to do so, but no existing programs would be broken.

It wouldn't be breakage, it would just be a new API for new devices/capabilities. Eventually all the devices that use v4l2 would go away and v4l2 would get removed, probably in like 20 years.

[stormcrow]

It seems like v4l2 is about to get replaced too so doing anything to work with it doesn't seem like a good idea.

The only way V4L2 is going to be "replaced" is for something that takes its place that leaves the current V4L2 API in place unchanged. This means any new reworks of V4L2 would start by refactoring existing code and extending the API rather than altering the API already there. Linus is not going to allow user space breakage of that magnitude. (He generally doesn't allow any user space breakage into his kernel tree.) Any new drivers that wouldn't be able to exist inside the V4L2 will just add another user space API. Anything needing to make use of the new API calls would have to be written to do so, but no existing programs would be broken.

[browseria]

nah v4l2 isn't going anywhere. and even if this CAM api does replace it for cameras, I doubt it would cover hw encoding and decoding too

Are you sure? What about libcamera?

[Quackdoc]

It seems like v4l2 is about to get replaced too so doing anything to work with it doesn't seem like a good idea.

nah v4l2 isn't going anywhere. and even if this CAM api does replace it for cameras, I doubt it would cover hw encoding and decoding too

[Eirikr1848]

My pre-coffee brain saw XvMC as “XMBC” and wondered why the heck XBox Media Center was included in Mesa to begin with.

In all seriousness though, XvMC really was only applicable to a few specific GPUs that use the r600 driver, right? Maybe like the Radeon HD 2000 series?

Not really a big loss as… well… what in the modern world would be using MPEG1/2 anyway?

It’s great to have continued r600 driver support for OpenGL but to be fair I don’t see this specifically as a loss.

My iMac (2007, Radeon Pro 2600) running Ubuntu in my guest room relies on r600 Gallium drivers to act as media streaming machine for company when they are here / doubles as a TV. But everything is H264 at least so 🤷♂️

[Amaranth]

with xvmc gone, it has fgotten me thinking, as much as I like vaapi, I wish we had something that was more unified, specifically with v4l2. the v4l2->libva seems to be a dead project, and implementing v4l2 + vaapi or just use the sledge hammer approach and use ffmpeg or gstreamer is suboptimal IMO.

It seems like v4l2 is about to get replaced too so doing anything to work with it doesn't seem like a good idea.

[Quackdoc]

with xvmc gone, it has fgotten me thinking, as much as I like vaapi, I wish we had something that was more unified, specifically with v4l2. the v4l2->libva seems to be a dead project, and implementing v4l2 + vaapi or just use the sledge hammer approach and use ffmpeg or gstreamer is suboptimal IMO.

[CochainComplex]

I miss a blog post from him with an awesome story how his delete key got stuck and -17k lines of Mesa code were the result, with Mesa still running flawlessly afterwards.

In a Marie Kondo style blog post? If the code doestnt make vrooomm there is no emotional attachment so it can be thrown out

[ridge]

I miss a blog post from him with an awesome story how his delete key got stuck and -17k lines of Mesa code were the result, with Mesa still running flawlessly afterwards.

Beat me to it