From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9DAB621A16EFB for ; Wed, 17 May 2017 22:00:33 -0700 (PDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP; 17 May 2017 22:00:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,357,1491289200"; d="scan'208";a="1170848487" Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by fmsmga002.fm.intel.com with ESMTP; 17 May 2017 22:00:33 -0700 Received: from orsmsx161.amr.corp.intel.com (10.22.240.84) by ORSMSX105.amr.corp.intel.com (10.22.225.132) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 17 May 2017 22:00:21 -0700 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.59]) by ORSMSX161.amr.corp.intel.com ([169.254.4.102]) with mapi id 14.03.0319.002; Wed, 17 May 2017 22:00:22 -0700 From: "Kinney, Michael D" To: Michael Zimmermann , edk2-devel-01 , "Zeng, Star" , "Dong, Eric" , "Kinney, Michael D" Thread-Topic: [edk2] UEFI_DRIVER dependencies Thread-Index: AQHSz5FKJLscbVofV0u1EDLZtIwFkqH5huFQ Date: Thu, 18 May 2017 05:00:20 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTkxOWYyMDctMGViNC00ZTdiLThiM2ItMWEzNDY4ZTU2MDNkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlV5R09lbzI5Wng1MnhJczBwTFlYaWU2ZWxaeGRuTU11TktkZ040QmR2OVE9In0= dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.22.254.138] MIME-Version: 1.0 Subject: Re: UEFI_DRIVER dependencies X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2017 05:00:33 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Michael, The UEFI Driver Model and the Driver Binding Protocol provide support for this case. The idea is that a driver is loaded and started, but when a UEFI Driver is started, it only registers a Driver Binding Protocol. Then in the=20 BDS phase, the devices required to boot are started using the UEFI Boot Service ConnectController() and ConnectController() calls the Driver Binding Protocol(s). The dependencies between UEFI Drivers are in their Driver=20 Binding Protocols which are not used until after all of=20 the UEFI Drivers are loaded and started. Mike > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Mi= chael > Zimmermann > Sent: Wednesday, May 17, 2017 9:43 PM > To: edk2-devel-01 ; Zeng, Star ; Dong, > Eric > Subject: [edk2] UEFI_DRIVER dependencies >=20 > 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. >=20 > 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? >=20 > Thanks, > Michael > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel