Hi Karunakar,
I guess you configure the VLAN on the NIC that PXE boot option selected. If so,
that's the expect behavior since the VLAN callback function will destroy the
previous NIC info including the MNP service data, then PXE driver binding
stop/start will be called again to update the device path.
Thanks,
Jiaxin
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Karunakar P
> Sent: Thursday, October 26, 2017 10:55 PM
> To: 'edk2-devel@lists.01.org' <edk2-devel@lists.01.org>
> Cc: Ye, Ting <ting...@intel.com>; Fu, Siyuan <siyuan...@intel.com>; Wu,
> Jiaxin <jiaxin...@intel.com>
> Subject: Re: [edk2] Adding VLAN changing Boot order to default
>
> Could you please provide your comments.
>
> Thank You,
> Karunakar
>
> From: Karunakar P
> Sent: Monday, October 23, 2017 8:38 PM
> To: 'edk2-devel@lists.01.org'
> Cc: Wu, Jiaxin; 'Fu, Siyuan'; Ye, Ting
> Subject: RE: Adding VLAN changing Boot order to default
>
> Hello All,
>
> Boot order is changing to default if we add VLAN, below are the steps
> followed.
>
> [Steps]
>
> 1. Change default boot order to some other, Then Commit changes and
> Exit. (In my case first boot option Is UEFI Internal Shell, then I changed
> PXEv4
> as first boot option)
>
> 2. Add a VLAN
>
> Network Device List -> MAC -> VLAN Configuration -> Create new VLAN and
> Add VLAN
>
> 3. Now check the Boot order
>
> Observation:- The boot order was changed to default(In my case, UEFI
> Internal shell becomes first boot option)
>
> Could you please provide your comments on this?
>
> Thanks,
> Karunakar
> ___
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
___
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
