public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Haojian Zhuang <haojian.zhuang@linaro.org>
To: <edk2-devel@lists.01.org>
Subject: Re: UEFI_DRIVER dependencies
Date: Thu, 18 May 2017 12:51:06 +0800	[thread overview]
Message-ID: <CY1PR15MB0730B5BB94EEC7BFCB5062EBF2E40@CY1PR15MB0730.namprd15.prod.outlook.com> (raw)
In-Reply-To: <CAN9vWDJ0fSyyoP0yr1soq5SCSPZfx4yjHqnwyDTx=3HO7HccSQ@mail.gmail.com>

On 2017/5/18 12:43, Michael Zimmermann wrote:
> I know that UEFI_DRIVERs don't need or support Depex sections, but
> what if an UEFI_DRIVER depends on a protocol provided by another
> UEFI_DRIVER?
> Since they get loaded automatically because I put them in my
> platform's fdf, it raises the question of the loading order.
>
> Will they get loaded in the order they're defined? How often will the
> core retry if one of the drivers returns EFI_NOT_READY?
>

Just adjust the driver sequence in both dsc and fdf file. Then they will 
get loaded in your order.

Regards
Haojian



  reply	other threads:[~2017-05-18  5:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18  4:43 UEFI_DRIVER dependencies Michael Zimmermann
2017-05-18  4:51 ` Haojian Zhuang [this message]
2017-05-18  5:00 ` Kinney, Michael D
2017-05-18  5:21   ` Andrew Fish
2017-05-18  5:42     ` Michael Zimmermann
2017-05-18  6:09       ` Andrew Fish
2017-05-18  6:16         ` Andrew Fish
2017-05-18  6:25           ` Michael Zimmermann
2017-05-18  6:29             ` Zeng, Star
2017-05-18  6:33             ` Andrew Fish
2017-05-18  6:44               ` peter.kirmeier
2017-05-18  6:56                 ` Andrew Fish
2017-05-18 10:07             ` Laszlo Ersek

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=CY1PR15MB0730B5BB94EEC7BFCB5062EBF2E40@CY1PR15MB0730.namprd15.prod.outlook.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