Hi Tom, Is there any plan to rename that package to match what is done for hantro? imx-vpu-<ip provider name>
Wouldn't it be clearer to people to have virtual/imxvpu being backed by either imx-vpu-hantro or imx-vpu-cnm (or chipsnmedia)? Regards, Gary Bisson Boundary Devices, LLC www.boundarydevices.com On Mon, Aug 6, 2018 at 10:05 PM, Tom Hochstein <[email protected]> wrote: > Signed-off-by: Tom Hochstein <[email protected]> > --- > recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb > b/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb > index f0c9d5a..d886e30 100644 > --- a/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb > +++ b/recipes-bsp/imx-vpu/imx-vpu_5.4.38.bb > @@ -1,8 +1,8 @@ > # Copyright (C) 2013-2018 O.S. Systems Software LTDA. > # Copyright (C) 2013-2016 Freescale Semiconductor > -# Copyright 2017 NXP > +# Copyright 2017-2018 NXP > > -DESCRIPTION = "Freescale VPU library" > +DESCRIPTION = "Freescale Chips&Media VPU library" > LICENSE = "Proprietary" > LIC_FILES_CHKSUM = "file://COPYING;md5=75abe2fa1d16ca79f87cde926f05f72d" > > @@ -32,4 +32,4 @@ do_install () { > } > > PACKAGE_ARCH = "${MACHINE_ARCH}" > -COMPATIBLE_MACHINE = "(mx6)" > +COMPATIBLE_MACHINE = "(mx6q|mx6dl)" > -- > 2.7.4 > > -- > _______________________________________________ > meta-freescale mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-freescale -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
