[meta-xilinx] [PATCH 4/4] arm-trusted-firmware_git.bb: Add provides

[Manjukumar Harthikote Matha]

> -----Original Message-----
> From: Nathan Rossi [mailto:nathan at nathanrossi.com]
> Sent: Saturday, November 19, 2016 3:35 AM
> To: Manjukumar Harthikote Matha
> Cc: meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] [PATCH 4/4] arm-trusted-firmware_git.bb: Add provides
>
> On 18 November 2016 at 11:04, Manjukumar Matha <manjukumar.harthikote-
> matha at xilinx.com> wrote:
> > There are cases where we want different providers for ATF depending on
> > development methodology. Having provides will enable easier switch for
> > ATF development.
> >
> > Signed-off-by: Manjukumar Matha
> > <manjukumar.harthikote-matha at xilinx.com>
> > ---
> >  recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git
> > a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
> > b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
> > index 9f29fc4..4f1c017 100644
> > --- a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
> > +++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_git.bb
> > @@ -3,6 +3,8 @@ DESCRIPTION = "ARM Trusted Firmware"
> >  LICENSE = "BSD"
> >  LIC_FILES_CHKSUM =
> "file://license.md;md5=829bdeb34c1d9044f393d5a16c068371"
> >
> > +PROVIDES = "virtual/atf"
>
> Anything against having this as "virtual/arm-trusted-firmware"
> instead? Which would go in-line with the changes made to the output file names in
> patch 3/4 of this series.
>
Nothing really, we can use as suggested.
We just got used to the terminology "ATF" I guess :)

Thanks
Manju

> Regards,
> Nathan
>
> > +
> >  inherit deploy
> >
> >  DEPENDS += "u-boot-mkimage-native"
> > --
> > 2.7.4
> >
> > --
> > _______________________________________________
> > meta-xilinx mailing list
> > meta-xilinx at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-xilinx


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.