Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README: Add notice of driver being legacy #542

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

martin-kokos
Copy link

Add notice of intel media driver

Add notice of intel media driver
@martin-kokos martin-kokos changed the title Update README Update README: ADd notice of driver being legacy Dec 28, 2022
@martin-kokos martin-kokos changed the title Update README: ADd notice of driver being legacy Update README: Add notice of driver being legacy Dec 28, 2022
@mirh
Copy link

mirh commented Aug 22, 2023

Maintenance mode is probably more correct?
Like.. it's not that they stopped development per se (like perhaps intel-hybrid-driver). It's more that there's nothing left to add/expand.

p.s. intel's own mailing lists are no more, at most the readme should point to the archive thereof

@martin-kokos
Copy link
Author

martin-kokos commented Aug 22, 2023

Maintenance mode is probably more correct? Like.. it's not that they stopped development per se (like perhaps intel-hybrid-driver). It's more that there's nothing left to add/expand.

p.s. intel's own mailing lists are no more, at most the readme should point to the archive thereof

That's what I meant. People looking for vaapi support on intel shouldn't be installing it and rather look at https://github.com/intel/media-driver instead if they can.

@mirh
Copy link

mirh commented Aug 22, 2023

Right, I forgot the part where you do actually have a choice to push ahead since non-Atom Gen8 hardware. For as much as I don't think <Gen12 is seeing much love there either (except perhaps in the common bits for HDR or whatever other fancier new modernity)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants