Skip to content

imx: update multimedia packages to 4.9.88_2.0.0_ga

Gary Bisson buildroot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest0 of 8 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 8 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Buildroot] [PATCH 0/8] imx: update multimedia packages to 4.9.88_2.0.0_ga

Hi,

Quoted 9 lines · Thomas Petazzoni

Hello,

Quoted 5 lines · Arnout Vandecappelle

I'm sorry for all the work that you did, but I don't really agree that this is
a good idea. The upstream package really is called imx-vpu, so we prefer to keep that name. We changed the name for openssl because there really was no other way, but I do prefer to avoid that.

Quoted 5 lines
Quoted 2 lines

So I think it's just a matter of finding a better name for the virtual package.
What about imx-vpu-provider?

I have not reviewed the patch series carefully enough yet, but a question is: do we need a virtual package at all?

Up to you, I'm ok either way, just thought it'd be cleaner this way.

Quoted 3 lines

I guess the imx-vpu API is not going to be used by gazillions of packages. If I read PATCH 5/8 correctly, it's in fact only used by two packages, right ?

Yes, libimxvpuapi and imx-vpuwrap are the only 2 users of imx-vpu right now.

Quoted 9 lines

Can't we simply have those two packages do:

ifeq ($(BR2_PACKAGE_FREESCALE_IMX_PLATFORM_IMX8M),y) use the new imx-vpu package
else
use the old imx-vpu package
endif

And ditto in their Config.in ?

Ok.

Quoted 10 lines

Virtual packages are great when there is really an arbitrary number of providers and/or an arbitrary number of users.

OpenSSL for examples has only two providers, but it has a very large number of users. Ditto jpeg. MySQL does not have a lot of users, but it might potentially have.

Also, the i.MX VPU stuff is highly platform-specific, it provides a very specialized API, it's very unlikely that we will see gazillions of packages depending on the i.MX VPU API.

Ok, I'll make a v3 like this then.

Regards,
Gary