Hi Michael, Thank you for your prompt reply.
Yes, in one of our implementation we are doing the same in our network driver (without DriverBinding protocol support). We were thinking to update our network driver to support DriverBinding Protocol and explore if we can get a boot call for boot options one by one starting from 1st boot option. If making the auto-neg asynchronous is the only option, then we don’t see any profit by updating our network driver to support DriverBinding protocol. Regards, Wasim > -----Original Message----- > From: Michael Brown [mailto:[email protected]] > Sent: Friday, March 23, 2018 5:52 PM > To: Wasim Khan <[email protected]>; Laszlo Ersek <[email protected]>; > Pankaj Bansal <[email protected]> > Cc: [email protected] > Subject: Re: [edk2] Boot delay due to network devices > > On 23/03/18 11:58, Wasim Khan wrote: > > Ex: if auto-neg timeout is 5 seconds and if we have 10 network interfaces > > (all > are legal candidate for booting), and cable is connected to 3rd interface only > then 45 seconds will be wasted (5 seconds each for 9 interfaces) in auto-neg > of > interfaces which are not connected via cable. > > There is no need for drivers to block in the Start() method waiting for > link-up > detection. Link detection can happen entirely asynchronously, thereby > reducing > your wasted time from 45 seconds to zero. > > Michael _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
