Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > muc.lists.freebsd.multimedia > #13407
| From | bugzilla-noreply@freebsd.org |
|---|---|
| Newsgroups | muc.lists.freebsd.multimedia |
| Subject | [Bug 297450] New video(4) framework conflicts with multimedia/v4l_compat |
| Date | 2026-08-12 16:42 +0000 |
| Organization | Newsgate at muc.de e.V. |
| Message-ID | <bug-297450-12827-Uf73hUCi2S@https.bugs.freebsd.org/bugzilla/> (permalink) |
| References | <bug-297450-12827@https.bugs.freebsd.org/bugzilla/> |
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297450
Ed Maste <emaste@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |emaste@freebsd.org
--- Comment #2 from Ed Maste <emaste@freebsd.org> ---
> Are FreeBSD video(4) headers and definitions expected to be compatible with v4l
> ones? In this case, we can just drop multimedia/v4l_compat in affected ports and let
> them build against native headers?
I believe that is the path that we should take (and have multimedia/v4l_compat
IGNOREd on 16.x and later), but we will have to iteratively find what
functionality is missing and implement it.
--
You are receiving this mail because:
You are the assignee for the bug.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
Back to muc.lists.freebsd.multimedia | Previous | Next | Find similar | Unroll thread
[Bug 297450] New video(4) framework conflicts with multimedia/v4l_compat bugzilla-noreply@freebsd.org - 2026-08-12 16:42 +0000
csiph-web