El jue, 8 ago 2024 a la(s) 3:49 a.m., Robert Nagy (rob...@openbsd.org) escribió: > > On 07/08/24 17:46 GMT, José Maldonado wrote: > > El mié, 7 ago 2024 a la(s) 5:39 p.m., Theo de Raadt > > (dera...@openbsd.org) escribió: > > > > > > This is so backwards. > > > > > > What do you expect to happen? Oh robert will commit it, without any > > > testing. Oh and only he should work on it, right? Noone else needs > > > to, they can just sit on the mailing list and ask "when?" > > > > > > Yes there is a reason. It is one guy doing it all, and asking is > > > NOT ACTUALLY HELPING. Think about it. > > > > > > > > > José Maldonado <josemal...@gmail.com> wrote: > > > > > > > Hi everyone! > > > > > > > > Seeing the progress of VAAPI support in OpenBSD + Firefox, yesterday I > > > > wanted to take a look at VAAPI support in Chromium. Checking the > > > > Chromium dev site, I see that there are a couple of options that need > > > > to be enabled to achieve this, and checking the port I see that they > > > > are currently disabled. > > > > > > > > More precisely the option in question is: > > > > > > > > GN_ARGS+= use_vaapi=false > > > > > > > > Is there a reason that blocks VAAPI activation in Chromium at this > > > > point? Thanks for your response. > > > > > > > > -- > > > > "Dios en su Cielo, todo bien en la Tierra" > > > > *********************************************** > > > > > > > > I agree with that Theo, but that's exactly why I'm asking, to find out > > if there are any known issues, not to put pressure on it. > > > > I understand that Robert is the only one working on that port, in > > fact, I CC'd him so he can respond if there's any problem with it. > > > > Anyway, right now I'm compiling the port with use_vaapi=true to test > > and report any issues. > > It will fail quiet early in the configure stage. > > We are using an external libvpx from ports and not the bundled one > because we have patches for BTI and it only makes sense to use that > instead of copying the patches all over. > > vaapi needs the internal copy of to build the vp8-9 encoders and decoders > and that is broken at the moment. > > I will look into this once I am back from holidays. >
I just saw this (as Theo predicted, the problem blew up in my face). Thanks for your reply Robert. -- "Dios en su Cielo, todo bien en la Tierra" ***********************************************