On Mon, Aug 31, 2015 at 03:33:41AM +0000, Fu, Siyuan wrote: > Yes wireless connection will be stay in associated state. > Fair enough. Then I only have to take care of the IP address, gateway, etc. from the device path.
Thanks! Gary Lin > -----Original Message----- > From: Gary Ching-Pang Lin [mailto:[email protected]] > Sent: Monday, August 31, 2015 11:15 AM > To: Fu, Siyuan <[email protected]> > Cc: [email protected] > Subject: Re: [edk2] Network disconnected after NBP was loaded > > On Mon, Aug 31, 2015 at 02:29:02AM +0000, Fu, Siyuan wrote: > > Hi, Gary > > > > After NBP (boot loader) file download, the device path of the NIC will be > > update to include the IP address configuration and boot file URL info, and > > this device path could also be found in the loaded image protocol on the > > image handle of the NBP file. The boot loader could continue use this IP > > address and doesn't need to make DHCP again. Please refer section 23.7.3.1 > > Device Path in UEFI 2.5 for details. > > OK. So in this case, the bootloader just retreives the IP address from the > device path and sets up the connection again. This should be easy. > > Another question came to me is: how about the wireless connection? Will the > AP still be associated and authenticated? > > Thanks, > > Gary Lin > > > > > Best Regards > > Siyuan > > > > -----Original Message----- > > From: edk2-devel [mailto:[email protected]] On Behalf Of > > Gary Ching-Pang Lin > > Sent: Friday, August 28, 2015 4:02 PM > > To: [email protected] > > Subject: [edk2] Network disconnected after NBP was loaded > > > > Hi, > > > > I was under the impression that the UEFI firmware would maintain the > > network connection unless a EFI program or OS determine to create a new > > connection. > > Take PXE for example. After the bootloader is loaded, it can utilize the > > PxeBaseCode protocol to download the OS image with the existed connection > > without starting the DHCP process again. However, the current > > implementation of HttpBoot seems to be another case. > > > > In HttpBootDxeLoadFile() in NetworkPkg/HttpBootDxe/HttpBootImpl.c, the > > driver closes the DHCP4 connection right after the file is loaded. This > > means the bootloader has to set up the network connection on its own if it > > needs to load a remote file. > > > > My question is: what's the expection for a bootloader/Network Boot Program? > > Should the bootloader always create its own connection for HTTP Boot? > > > > Thanks, > > > > Gary Lin > > _______________________________________________ > > edk2-devel mailing list > > [email protected] > > https://lists.01.org/mailman/listinfo/edk2-devel > > > _______________________________________________ > edk2-devel mailing list > [email protected] > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
