From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Udit Kumar <udit.kumar@nxp.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: Why we need CapsuleLib even platform does not support this feature
Date: Wed, 15 Nov 2017 13:36:23 +0000 [thread overview]
Message-ID: <CAKv+Gu8fUQVAgXfe-k3hfh6aO6TEt3rSAWLyVr_3EfRAeFJJcQ@mail.gmail.com> (raw)
In-Reply-To: <AM6PR0402MB33343D126F1D634316F339CF91290@AM6PR0402MB3334.eurprd04.prod.outlook.com>
On 15 November 2017 at 13:34, Udit Kumar <udit.kumar@nxp.com> wrote:
> Hi,
> I recently noticed in my build as well, we need to include CapsuleLib even platform does not support Capsule update feature.
> Thanks to help me, why this dependency is added in edk2.
>
It was added as a dependency to
ArmPkg/Library/PlatformBootManagerLib/PlatformBootManagerLib.inf, for
capsule update support.
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ard
>> Biesheuvel
>> Sent: Tuesday, November 14, 2017 4:48 PM
>> To: Kalyan Nagabhirava <kalyankumar.nagabhirava@linaro.org>
>> Cc: edk2-devel@lists.01.org; Leif Lindholm <leif.lindholm@linaro.org>; Mark
>> Gregotski <mark.gregotski@linaro.org>
>> Subject: Re: [edk2] [PATCH edk2-platforms]: resolving Hikey platform build error
>>
>> On 14 November 2017 at 11:16, Kalyan Nagabhirava
>> <kalyankumar.nagabhirava@linaro.org> wrote:
>> >
>> > "Instance of library class [CapsuleLib] is not found" build error is
>> > coming for Hikey platform, to resolve this issueadded CapsuleLib to
>> > "LibraryClasses.common" section
>> >
>> > diff --git a/Platform/Hisilicon/HiKey/HiKey.dsc
>> > b/Platform/Hisilicon/HiKey/HiKey.dsc
>> > index 968e8ac..2e3b1c8 100644
>> > --- a/Platform/Hisilicon/HiKey/HiKey.dsc
>> > +++ b/Platform/Hisilicon/HiKey/HiKey.dsc
>> > @@ -61,6 +61,7 @@
>> >
>> > SynchronizationLib|MdePkg/Library/BaseSynchronizationLib/BaseSynchroni
>> > SynchronizationLib|zationLib.inf
>> >
>> > FdtLib|EmbeddedPkg/Library/FdtLib/FdtLib.inf
>> > +
>> > + CapsuleLib|MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.
>> > + inf
>> >
>> >
>> UefiBootManagerLib|MdeModulePkg/Library/UefiBootManagerLib/UefiBootM
>> an
>> > UefiBootManagerLib|agerLib.inf
>> >
>> >
>> PlatformBootManagerLib|ArmPkg/Library/PlatformBootManagerLib/PlatformB
>> > PlatformBootManagerLib|ootManagerLib.inf
>> > BootLogoLib|MdeModulePkg/Library/BootLogoLib/BootLogoLib.inf
>> >
>> >
>>
>> Thanks Kalyan
>>
>> Could you resend it as a proper patch, please? I.e., with the appropriate
>>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>>
>> and Signed-off-by line,
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.01
>> .org%2Fmailman%2Flistinfo%2Fedk2-
>> devel&data=02%7C01%7Cudit.kumar%40nxp.com%7Cc1807332add6499fcd730
>> 8d52b516fad%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6364625
>> 51151191358&sdata=joABHCm%2F3Iu0jfplBE3Ora9ffp3IfuNuu2GfOgOTsV8%3D
>> &reserved=0
prev parent reply other threads:[~2017-11-15 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 13:34 Why we need CapsuleLib even platform does not support this feature Udit Kumar
2017-11-15 13:36 ` Ard Biesheuvel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKv+Gu8fUQVAgXfe-k3hfh6aO6TEt3rSAWLyVr_3EfRAeFJJcQ@mail.gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox