Hi Ting,
Then Undi Command entry point is common for all the handles identified by
the VLAN device path nodes. The UNDI command entry point has only one
parameter (PXE_CDB).
from this CDB, i think we cannot disntinguish the handles represented by
VLAN device path nodes from this parameter alone ??. Please correct me if i
am wrong.
Can the MNP_SYS_POLL_INTERVAL be modified from UNDI code ??. I dont know
whether this can be modifed from UNDI code. The "EnableSystemPoll" varaible
is driver by layers above MNP. Can this be disabled from UNDI code
conditionally ??.
Thanks,
Sajeesh.
Hi Sajeesh,
I think you will install device path protocol together with NII. The device
path nodes of the device path protocol include the VLAN + MAC device path;
you should able to distinguish the handle by the VLAN device path node.
For the MNP system poll performance improvement, you might consider update
the MNP_SYS_POLL_INTERVAL to longer time slot; or consider some techniques
like more dynamic timer to help improve system polling in your case.
Best Regards,
Ye Ting
On Mon, Mar 30, 2015 at 8:27 AM, <edk2-devel-requ...@lists.sourceforge.net>
wrote:
> Send edk2-devel mailing list submissions to
> edk2-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> or, via email, send a message with subject or body 'help' to
> edk2-devel-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> edk2-devel-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of edk2-devel digest..."
>
>
> Today's Topics:
>
> 1. Large Vacant.bin in Vlv2TbltDevicePkg (Jordan Justen)
> 2. Re: edk2-devel Digest, Vol 63, Issue 95 (Ye, Ting)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 28 Mar 2015 17:25:28 -0700
> From: Jordan Justen <jordan.l.jus...@intel.com>
> Subject: [edk2] Large Vacant.bin in Vlv2TbltDevicePkg
> To: David Wei <david....@intel.com>
> Cc: edk2-devel@lists.sourceforge.net
> Message-ID: <20150329002528.9478.68326@jljusten-ivb>
> Content-Type: text/plain; charset="utf-8"
>
> David,
>
> Bruce pointed out on irc that
> Vlv2TbltDevicePkg/Stitch/IFWIHeader/Vacant.bin is a large (~3.8MB),
> and essentially empty (filled with 0xff) binary file in the tree. This
> appears to be the largest file in the EDK2 tree.
>
> Isn't there a more efficient way to just create this file via a script
> as needed?
>
> For example:
> dd if=/dev/zero ibs=1k count=3836 | tr "\000" "\377" > Vacant.bin
>
> Or, a python script could easily create the file too.
>
> -Jordan
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 30 Mar 2015 02:56:48 +0000
> From: "Ye, Ting" <ting...@intel.com>
> Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 95
> To: "edk2-devel@lists.sourceforge.net"
> <edk2-devel@lists.sourceforge.net>
> Message-ID:
> <
> bc0c045b0e2a584ca4575e779fa2c12a0a885...@shsmsx104.ccr.corp.intel.com>
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Sajeesh,
>
> I think you will install device path protocol together with NII. The
> device path nodes of the device path protocol include the VLAN + MAC device
> path; you should able to distinguish the handle by the VLAN device path
> node.
> For the MNP system poll performance improvement, you might consider update
> the MNP_SYS_POLL_INTERVAL to longer time slot; or consider some techniques
> like more dynamic timer to help improve system polling in your case.
>
> Best Regards,
> Ye Ting
>
> From: Sajeesh Kk [mailto:sajee...@gmail.com]
> Sent: Friday, March 27, 2015 10:33 PM
> To: edk2-devel@lists.sourceforge.net
> Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 95
>
> Hello Ting,
> In some of the servers, we can configure more than one VLAN for an
> interface. The entry point of (Id field of NII Protocol) is common
> for all the VLAN handles. when an UNDI command is issued by SNP, i am
> unable to figure out on which VLAN instance the command
> is issued. This information is required since so as to correctly get the
> UNDI state for that VLAN instance. I am stuck at this point.
> Please let me know your inputs.
> Thanks,
> Sajeesh.
>
>
> Hi Ting,
> I could make some progress by maintaining states per handle. But the
> download process is quite slow.
> As an experiment, i disabled the MNP System Poll timer and could observe a
> major inprovement in
> perfomance. If an interface supports more than one VLAN interface, then
> this timer would be an overhead
> and will reduce the perfomance. Am i missing something in the driver ??
> Please share your thoughts.
>
> Thanks,
> Sajeesh.
>
> Hi Sajeesh,
>
> I think the UNDI differences should be hidden from SNP. I.e. The SNP driver
> need not know whether the NII is installed by a NIC, or by a VLAN device.
> You need maintain the UNDI state per handles to guarantee SNP work
> properly.
> In your example, if there are a NIC and a VLAN NIC, and the NIC is already
> initialized by SNP; later when SNP tries to initialize the VLAN NIC, SNP
> should return EFI_SUCCESS instead of EFI_DEVICE_ERROR to MNP. This way, the
> upper layer drivers can function.
>
> Best Regards,
> Ye Ting
>
> On Mon, Mar 23, 2015 at 11:42 PM, <
> edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>> wrote:
> Send edk2-devel mailing list submissions to
> edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
> or, via email, send a message with subject or body 'help' to
> edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>
>
> You can reach the person managing the list at
> edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of edk2-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: edk2-devel Digest, Vol 63, Issue 87 (Sajeesh Kk)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 23 Mar 2015 23:41:54 +0530
> From: Sajeesh Kk <sajee...@gmail.com<mailto:sajee...@gmail.com>>
> Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 87
> To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
> Message-ID:
> <CA+1y_6UE+Op0_FT=
> znzkt_dnwcu69bqr2x4aeycvjsn9pbh...@mail.gmail.com<mailto:
> znzkt_dnwcu69bqr2x4aeycvjsn9pbh...@mail.gmail.com>>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Ting,
> I could make some progress by maintaining states per handle. But the
> download process is quite slow.
> As an experiment, i disabled the MNP System Poll timer and could observe a
> major inprovement in
> perfomance. If an interface supports more than one VLAN interface, then
> this timer would be an overhead
> and will reduce the perfomance. Am i missing something in the driver ??
> Please share your thoughts.
>
> Thanks,
> Sajeesh.
>
> Hi Sajeesh,
>
> I think the UNDI differences should be hidden from SNP. I.e. The SNP driver
> need not know whether the NII is installed by a NIC, or by a VLAN device.
> You need maintain the UNDI state per handles to guarantee SNP work
> properly.
> In your example, if there are a NIC and a VLAN NIC, and the NIC is already
> initialized by SNP; later when SNP tries to initialize the VLAN NIC, SNP
> should return EFI_SUCCESS instead of EFI_DEVICE_ERROR to MNP. This way, the
> upper layer drivers can function.
>
> Best Regards,
> Ye Ting
>
> On Wed, Mar 18, 2015 at 10:46 AM, <
> edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>>
> wrote:
>
> > Send edk2-devel mailing list submissions to
> > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > or, via email, send a message with subject or body 'help' to
> > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>
> >
> > You can reach the person managing the list at
> > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net>
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of edk2-devel digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: edk2-devel Digest, Vol 63, Issue 85 (Sajeesh Kk)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 18 Mar 2015 10:46:06 +0530
> > From: Sajeesh Kk <sajee...@gmail.com<mailto:sajee...@gmail.com>>
> > Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 85
> > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
> > Message-ID:
> > <
> > ca+1y_6xy+irfqz-wm28gigw19nhkcxd50h6w3wtbpp+bnq2...@mail.gmail.com
> <mailto:
> ca%2b1y_6xy%2birfqz-wm28gigw19nhkcxd50h6w3wtbpp%2bbnq2...@mail.gmail.com>>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi Ting,
> >
> > Thanks for your response. Its of great help to me. I tried to simulate by
> > having states per new handles created. But this require more changes in
> > the driver.
> > Will implement and get back to you. Thanks a lot for clarifying this.
> >
> > Thanks,
> > Sajeesh.
> >
> > Hi Sajeesh,
> >
> > I think the UNDI differences should be hidden from SNP. I.e. The SNP
> driver
> > need not know whether the NII is installed by a NIC, or by a VLAN device.
> > You need maintain the UNDI state per handles to guarantee SNP work
> > properly.
> > In your example, if there are a NIC and a VLAN NIC, and the NIC is
> already
> > initialized by SNP; later when SNP tries to initialize the VLAN NIC, SNP
> > should return EFI_SUCCESS instead of EFI_DEVICE_ERROR to MNP. This way,
> the
> > upper layer drivers can function.
> >
> > Best Regards,
> > Ye Ting
> >
> > On Wed, Mar 18, 2015 at 8:11 AM, <
> edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>
> > >
> > wrote:
> >
> > > Send edk2-devel mailing list submissions to
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > > or, via email, send a message with subject or body 'help' to
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>
> > >
> > > You can reach the person managing the list at
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net>
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of edk2-devel digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > > 1. Re: edk2-devel Digest, Vol 63, Issue 74 (Ye, Ting)
> > >
> > >
> > > ----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Wed, 18 Mar 2015 02:38:17 +0000
> > > From: "Ye, Ting" <ting...@intel.com<mailto:ting...@intel.com>>
> > > Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 74
> > > To: "edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>"
> > > <edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>
> > > Message-ID:
> > > <
> > > bc0c045b0e2a584ca4575e779fa2c12a0a875...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a875...@shsmsx104.ccr.corp.intel.com>>
> > >
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > >
> > > Hi Sajeesh,
> > >
> > > I think the UNDI differences should be hidden from SNP. I.e. The SNP
> > > driver need not know whether the NII is installed by a NIC, or by a
> VLAN
> > > device. You need maintain the UNDI state per handles to guarantee SNP
> > work
> > > properly.
> > > In your example, if there are a NIC and a VLAN NIC, and the NIC is
> > > already initialized by SNP; later when SNP tries to initialize the VLAN
> > > NIC, SNP should return EFI_SUCCESS instead of EFI_DEVICE_ERROR to MNP.
> > This
> > > way, the upper layer drivers can function.
> > >
> > > Best Regards,
> > > Ye Ting
> > >
> > > From: Sajeesh Kk [mailto:sajee...@gmail.com<mailto:sajee...@gmail.com
> >]
> > > Sent: Tuesday, March 17, 2015 5:03 PM
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
> > > Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 74
> > >
> > > Hi Ting,
> > > Thanks for your response. I am exactly doing the same way you have
> > > mentioned here. Create a new handle and install VLAN + MAC device path,
> > NII
> > > protocols on this handle.
> > > Then make this handle the child of the controller handle (parameter to
> > the
> > > driver start). But the Question is the regarding the Undi State
> > > (started/stopped/initialized). Do we need to maintain this State per
> Vlan
> > > handle since are installing NII Protocol ??.
> > >
> > > The problem i am curently facing is described below:
> > >
> > > Once the driver start routine is completed, the Undi state eventually
> > > changes to Initialized state in response to a series of UNDI calls done
> > > from SNP + MNP. Now when Vlan handle gets created with has its own
> > instance
> > > of VLAN+MAC dev path and NII Protocols, I could see UNDI APIs being
> > called
> > > from SNP driver. This is expected since a new instance of NII Protocol
> > is
> > > being installed. the UNDI code returns the status as "Already Started"
> to
> > > SNP in response to these UNDI calls This is because there is a single
> > state
> > > variable maintained in the UNDI driver. SNP returns EFI_DEVICE_ERROR
> to
> > > MNPdriver and eventually i am receiving Undi Shutdown and Undi Stop
> > calls.
> > > As an experiment, i after creating new Vlan Handle, i changed the Undi
> > > State to Stopped state. Then things started to work. I could see that
> NBP
> > > gets loaded. Is it the right method to change the Undi State like
> this.
> > > Please share your thoughts.
> > >
> > > Thanks,
> > > Sajeesh.
> > >
> > >
> > > Hi Sajeesh,
> > >
> > > You can refer to the software VLAN implementation in MNP to produce the
> > > EFI_VLAN_CONFIG_PROTOCOL. In MNP VLAN, create a VLAN device means to
> > create
> > > a virtual NIC device handle and install MNP service binding and device
> > path
> > > protocol to the handle. The device path node for this handle is MAC +
> > VLAN
> > > node. Thus, a NIC with two VLAN configured supplies three NIC handles
> to
> > > the system. In your UNDI, I think you also can create a virtual handle
> > for
> > > a VLAN device and install a new device path protocol to it. You also
> need
> > > install NII protocol to each handle.
> > >
> > > Best Regards,
> > > Ye Ting
> > >
> > > On Tue, Mar 17, 2015 at 7:37 AM, <
> > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>
> > > <mailto:edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>>> wrote:
> > > Send edk2-devel mailing list submissions to
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > > or, via email, send a message with subject or body 'help' to
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net><mailto:
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>>
> > >
> > > You can reach the person managing the list at
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net><mailto:
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net>>
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of edk2-devel digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > > 1. Re: edk2-devel Digest, Vol 63, Issue 70 (Ye, Ting)
> > >
> > >
> > > ----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Tue, 17 Mar 2015 02:06:29 +0000
> > > From: "Ye, Ting" <ting...@intel.com<mailto:ting...@intel.com><mailto:
> ting...@intel.com<mailto:ting...@intel.com>>>
> > > Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 70
> > > To: "edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>"
> > > <edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > Message-ID:
> > > <
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > <mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>>>
> > >
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Hi Sajeesh,
> > >
> > > You can refer to the software VLAN implementation in MNP to produce the
> > > EFI_VLAN_CONFIG_PROTOCOL. In MNP VLAN, create a VLAN device means to
> > create
> > > a virtual NIC device handle and install MNP service binding and device
> > path
> > > protocol to the handle. The device path node for this handle is MAC +
> > VLAN
> > > node. Thus, a NIC with two VLAN configured supplies three NIC handles
> to
> > > the system. In your UNDI, I think you also can create a virtual handle
> > for
> > > a VLAN device and install a new device path protocol to it. You also
> need
> > > install NII protocol to each handle.
> > >
> > > Best Regards,
> > > Ye Ting
> > >
> > > From: Sajeesh Kk [mailto:sajee...@gmail.com<mailto:sajee...@gmail.com
> ><mailto:sajee...@gmail.com<mailto:sajee...@gmail.com>>]
> > > Sent: Monday, March 16, 2015 9:32 PM
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>
> > > Subject: Re: [edk2] edk2-devel Digest, Vol 63, Issue 70
> > >
> > > Hi Ting,
> > > We dont have our own network modules for PXE boot. we are using UEFI
> > > notwork stack. Our hadrware has the capability to add/remove vlan tags
> > from
> > > the packets
> > > and we dont want the software implementation part done by MNP. During
> the
> > > driver start we publish EFI_VLAN_CONFIG_PROTOCOL on the child handle. I
> > > could see
> > > in the system bios menus an option to configure vlans for our network
> > > interface. I do get a call ("Set" call of EFI_VLAN_CONFIG_PROTOCOL).
> But
> > > when tried to boot,
> > > the driver gets Undi_Shutdown and Undi_Stop calls and there after no
> > more
> > > UNDI API calls.
> > > The uefi Spec mentions that as part of "Set" call, a new Vlan device
> > needs
> > > to be created. Does this mean to create a new handle and publish
> > > EFI_VLAN_CONFIG_PROTOCOL
> > > on this new handle ??.
> > >
> > >
> > > Thanks,
> > > Sajeesh.
> > >
> > > Message: 1
> > > Date: Mon, 16 Mar 2015 03:05:25 +0000
> > > From: "Ye, Ting" <ting...@intel.com<mailto:ting...@intel.com><mailto:
> ting...@intel.com<mailto:ting...@intel.com>><mailto:
> > > ting...@intel.com<mailto:ting...@intel.com><mailto:ting...@intel.com
> <mailto:ting...@intel.com>>>>
> > > Subject: Re: [edk2] Vlan config protocol Query
> > > To: "edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>"
> > > <edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>>
> > > Message-ID:
> > > <
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > <mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > ><mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > <mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>>>>
> > >
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Hi Sajeesh,
> > >
> > > I need more information to understand your question. As you said you
> are
> > > implementing EFI_VLAN_CONIFG_PROTOCOL in your UNDI driver, do you use
> > your
> > > own network modules for PXE boot, or you use UEFI network stack? If you
> > use
> > > UEFI network stack, MnpDxe driver already supplies
> > EFI_VLAN_CONIFG_PROTOCOL
> > > and VlanConfigDxe provides UI configuration.
> > >
> > > Best Regards,
> > > Ye Ting
> > >
> > > On Mon, Mar 16, 2015 at 3:53 PM, <
> > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>
> > > <mailto:edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>><mailto:
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net><mailto:
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>>>> wrote:
> > > Send edk2-devel mailing list submissions to
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > >
> > > To subscribe or unsubscribe via the World Wide Web, visit
> > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > > or, via email, send a message with subject or body 'help' to
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net><mailto:
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>><mailto:
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net><mailto:
> > > edk2-devel-requ...@lists.sourceforge.net<mailto:
> edk2-devel-requ...@lists.sourceforge.net>>>
> > >
> > > You can reach the person managing the list at
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net><mailto:
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net>><mailto:
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net><mailto:
> > > edk2-devel-ow...@lists.sourceforge.net<mailto:
> edk2-devel-ow...@lists.sourceforge.net>>>
> > >
> > > When replying, please edit your Subject line so it is more specific
> > > than "Re: Contents of edk2-devel digest..."
> > >
> > >
> > > Today's Topics:
> > >
> > > 1. Re: Vlan config protocol Query (Ye, Ting)
> > > 2. Re: [PATCH] PeCoffExtraActionLibDebug: Restore debug
> > > registers in PeCoffExtraActionLibDebug (Fan, Jeff)
> > > 3. Socket Programming (partha sarathi swain)
> > > 4. Re: [Patch] ShellPkg: Fix typo in ShellPkg. (Bruce Cran)
> > > 5. Re: [Patch] ShellPkg: Fix typo in ShellPkg. (Bruce Cran)
> > >
> > >
> > > ----------------------------------------------------------------------
> > >
> > > Message: 1
> > > Date: Mon, 16 Mar 2015 03:05:25 +0000
> > > From: "Ye, Ting" <ting...@intel.com<mailto:ting...@intel.com><mailto:
> ting...@intel.com<mailto:ting...@intel.com>><mailto:
> > > ting...@intel.com<mailto:ting...@intel.com><mailto:ting...@intel.com
> <mailto:ting...@intel.com>>>>
> > > Subject: Re: [edk2] Vlan config protocol Query
> > > To: "edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>"
> > > <edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>>
> > > Message-ID:
> > > <
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > <mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > ><mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>
> > > <mailto:
> > > bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com
> <mailto:
> bc0c045b0e2a584ca4575e779fa2c12a0a874...@shsmsx104.ccr.corp.intel.com>>>>
> > >
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Hi Sajeesh,
> > >
> > > I need more information to understand your question. As you said you
> are
> > > implementing EFI_VLAN_CONIFG_PROTOCOL in your UNDI driver, do you use
> > your
> > > own network modules for PXE boot, or you use UEFI network stack? If you
> > use
> > > UEFI network stack, MnpDxe driver already supplies
> > EFI_VLAN_CONIFG_PROTOCOL
> > > and VlanConfigDxe provides UI configuration.
> > >
> > > Best Regards,
> > > Ye Ting
> > >
> > >
> > >
> > > From: Sajeesh Kk [mailto:sajee...@gmail.com<mailto:sajee...@gmail.com
> ><mailto:sajee...@gmail.com<mailto:sajee...@gmail.com>
> > > ><mailto:sajee...@gmail.com<mailto:sajee...@gmail.com><mailto:
> sajee...@gmail.com<mailto:sajee...@gmail.com>>>]
> > > Sent: Saturday, March 14, 2015 2:00 AM
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > Subject: [edk2] Vlan config protocol Query
> > >
> > > Hello,
> > > I am supporting vlan config protocol in undi driver four our network
> > > adapter. I am creating vlan device path on to the same handle on which
> > NII
> > > protocol is installed. I could see that i get a set call when
> > > VLAN is configured and the device path created looks ok. when tried to
> > > perform PXE boot, i could see Undi_Shutdown and Undi_stop calls comming
> > in.
> > > Can someone explain whether i am proceeding in the right direction and
> > > there after no Undi calls are comming. Not able to figiure out
> > > why this is happening. Any help in this regard greatly appreciated.
> > >
> > > Thanks,
> > > Sajeesh.
> > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > >
> > > ------------------------------
> > >
> > > Message: 2
> > > Date: Mon, 16 Mar 2015 03:05:58 +0000
> > > From: "Fan, Jeff" <jeff....@intel.com<mailto:jeff....@intel.com
> ><mailto:jeff....@intel.com<mailto:jeff....@intel.com>><mailto:
> > > jeff....@intel.com<mailto:jeff....@intel.com><mailto:
> jeff....@intel.com<mailto:jeff....@intel.com>>>>
> > > Subject: Re: [edk2] [PATCH] PeCoffExtraActionLibDebug: Restore debug
> > > registers in PeCoffExtraActionLibDebug
> > > To: "Brian J. Johnson" <bjohn...@sgi.com<mailto:bjohn...@sgi.com
> ><mailto:bjohn...@sgi.com<mailto:bjohn...@sgi.com>
> > ><mailto:
> > > bjohn...@sgi.com<mailto:bjohn...@sgi.com><mailto:bjohn...@sgi.com
> <mailto:bjohn...@sgi.com>>>>,
> > > "edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>" <
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:edk2-devel@lists.sourceforge.net
> <mailto:edk2-devel@lists.sourceforge.net>
> > > ><mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>>
> > > Message-ID:
> > > <
> > > 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com
> <mailto:
> 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com>
> > > <mailto:
> > > 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com
> <mailto:
> 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com>
> > > ><mailto:
> > > 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com
> <mailto:
> 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com>
> > > <mailto:
> > > 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com
> <mailto:
> 542cf652f8836a4ab8dbfaad40ed192a1194e...@shsmsx102.ccr.corp.intel.com>>>>
> > >
> > > Content-Type: text/plain; charset="us-ascii"
> > >
> > > Brian,
> > >
> > > Sorry, I missed this patch.
> > >
> > > Thank you finding and fixing this bug. Your patch looks good to me.
> One
> > > minimal comment is to remove the word "qemu" from the code comment,
> > because
> > > we will avoid to use any specific platform information in core code.
> > > > + if ((NewDr7 & ~BIT10) == 0) { // H/w sets bit 10, qemu doesn't
> > >
> > > I suggest you may say "some simulator platform doesn't".
> > >
> > > PS: CR4 seems has the similar issue reported by you on
> > > DEBUG_LOAD_IMAGE_METHOD_SOFT_INT3 path. Are you interesting in fixing
> it
> > > together in your patch?
> > >
> > > Thanks!
> > > Jeff
> > > -----Original Message-----
> > > From: Brian J. Johnson [mailto:bjohn...@sgi.com<mailto:
> bjohn...@sgi.com><mailto:bjohn...@sgi.com<mailto:bjohn...@sgi.com>
> > > ><mailto:bjohn...@sgi.com<mailto:bjohn...@sgi.com><mailto:
> bjohn...@sgi.com<mailto:bjohn...@sgi.com>>>]
> > > Sent: Saturday, March 14, 2015 12:41 AM
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > Cc: Fan, Jeff
> > > Subject: Re: [edk2] [PATCH] PeCoffExtraActionLibDebug: Restore debug
> > > registers in PeCoffExtraActionLibDebug
> > >
> > > Ping?
> > >
> > > CCing the SourceLevelDebugPkg maintainer.
> > >
> > > Brian
> > >
> > > On 03/05/2015 09:26 AM, Brian J. Johnson wrote:
> > > > PeCoffExtraActionLibDebug uses the debug registers to pass module
> load
> > > > information to the DebugAgent, then restores the old register values.
> > > > However, it was missing code to restore Dr7 in the
> > > > DEBUG_LOAD_IMAGE_METHOD_SOFT_INT3 case. This broke hardware
> > > > breakpoints and watchpoints.
> > > >
> > > > Restore the values correctly in the DEBUG_LOAD_IMAGE_METHOD_SOFT_INT3
> > > > case, as well as the DEBUG_LOAD_IMAGE_METHOD_IO_HW_BREAKPOINT case.
> > > >
> > > > Contributed-under: TianoCore Contribution Agreement 1.0
> > > > Signed-off-by: Brian J. Johnson <bjohn...@sgi.com<mailto:
> bjohn...@sgi.com><mailto:
> > > bjohn...@sgi.com<mailto:bjohn...@sgi.com>><mailto:bjohn...@sgi.com
> <mailto:bjohn...@sgi.com><mailto:bjohn...@sgi.com<mailto:bjohn...@sgi.com
> >>>>
> > > > ---
> > > >
> > > > This fix has been built with OvmfPkg/OvmfPkgIa32X64.dsc, using the
> > > > GCC48 toolchain under Ubuntu. It has been tested (32- and 64-bit
> > > > mode) using qemu with tcg and a proprietary DebugAgentLib. We've
> also
> > > > used it on hardware in a proprietary BIOS with various Intel CPUs,
> > > > using the SourceLevelDebugPkg DebugAgentLib (an older version). It's
> > > > been built successfully with the WINDDK compilers, but I'm not really
> > > > in a position to build with MSVC.
> > > >
> > > > A note on Dr7 bit 10: the Intel SDM says that this bit always reads
> > > > as 1, and that's the behavior I see on hardware. However, on
> > > > simulators (including qemu in tcg mode) it often reads as 0. So I
> > > > just ignore it in the patch below when determining if Dr7 needs to be
> > > restored.
> > > >
> > > > Thanks,
> > > > Brian
> > > >
> > > > .../PeCoffExtraActionLib.c | 10
> ++++++++--
> > > > 1 file changed, 8 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git
> > > >
> a/SourceLevelDebugPkg/Library/PeCoffExtraActionLibDebug/PeCoffExtraAct
> > > > ionLib.c
> > > >
> b/SourceLevelDebugPkg/Library/PeCoffExtraActionLibDebug/PeCoffExtraAct
> > > > ionLib.c
> > > > index 9bf76bf..be26293 100644
> > > > ---
> > > >
> a/SourceLevelDebugPkg/Library/PeCoffExtraActionLibDebug/PeCoffExtraAct
> > > > ionLib.c
> > > > +++
> > > >
> b/SourceLevelDebugPkg/Library/PeCoffExtraActionLibDebug/PeCoffExtraAct
> > > > ionLib.c @@ -164,8 +164,14 @@ PeCoffLoaderExtraActionCommon (
> > > > if (AsmReadCr4 () == (Cr4 | BIT3)) {
> > > > AsmWriteCr4 (Cr4);
> > > > }
> > > > - if (NewDr7 == 0x20000480) {
> > > > - AsmWriteDr7 (Dr7);
> > > > + if (LoadImageMethod == DEBUG_LOAD_IMAGE_METHOD_IO_HW_BREAKPOINT) {
> > > > + if (NewDr7 == 0x20000480) {
> > > > + AsmWriteDr7 (Dr7);
> > > > + }
> > > > + } else if (LoadImageMethod == DEBUG_LOAD_IMAGE_METHOD_SOFT_INT3) {
> > > > + if ((NewDr7 & ~BIT10) == 0) { // H/w sets bit 10, qemu doesn't
> > > > + AsmWriteDr7 (Dr7);
> > > > + }
> > > > }
> > > > //
> > > > // Restore original IDT entry for INT1 if it was hooked.
> > > >
> > > >
> ----------------------------------------------------------------------
> > > > -------- Dive into the World of Parallel Programming The Go Parallel
> > > > Website, sponsored by Intel and developed in partnership with
> Slashdot
> > > > Media, is your hub for all things parallel software development, from
> > > > weekly thought leadership blogs to news, videos, case studies,
> > > > tutorials and more. Take a look and join the conversation now.
> > > > http://goparallel.sourceforge.net/
> > > > _______________________________________________
> > > > edk2-devel mailing list
> > > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > ><mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > > >
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 3
> > > Date: Mon, 16 Mar 2015 12:30:34 +0530
> > > From: partha sarathi swain <partha161.sili...@gmail.com<mailto:
> partha161.sili...@gmail.com><mailto:
> > > partha161.sili...@gmail.com<mailto:partha161.sili...@gmail.com
> >><mailto:partha161.sili...@gmail.com<mailto:partha161.sili...@gmail.com
> ><mailto:
> > > partha161.sili...@gmail.com<mailto:partha161.sili...@gmail.com>>>>
> > > Subject: [edk2] Socket Programming
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > Message-ID:
> > > <
> > > cak7jbgdzmu3udbyqmbdf+yj7xojkwb9bn+rd6cfite6vtas...@mail.gmail.com
> <mailto:
> cak7jbgdzmu3udbyqmbdf%2byj7xojkwb9bn%2brd6cfite6vtas...@mail.gmail.com>
> > <mailto:
> > > cak7jbgdzmu3udbyqmbdf%2byj7xojkwb9bn%2brd6cfite6vtas...@mail.gmail.com
> <mailto:
> cak7jbgdzmu3udbyqmbdf%252byj7xojkwb9bn%252brd6cfite6vtas...@mail.gmail.com
> >
> > > ><mailto:
> > > cak7jbgdzmu3udbyqmbdf%2byj7xojkwb9bn%2brd6cfite6vtas...@mail.gmail.com
> <mailto:
> cak7jbgdzmu3udbyqmbdf%252byj7xojkwb9bn%252brd6cfite6vtas...@mail.gmail.com
> >
> > > <mailto:
> > >
> >
> cak7jbgdzmu3udbyqmbdf%252byj7xojkwb9bn%252brd6cfite6vtas...@mail.gmail.com
> <mailto:
> cak7jbgdzmu3udbyqmbdf%25252byj7xojkwb9bn%25252brd6cfite6vtas...@mail.gmail.com
> >
> > > >>>
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Hi All,
> > > Could any one help me in writing a socket programming in UEFI (using
> > > UDK2014). My requirement is like "a server and client setup, where
> > client
> > > will open a socket ( with a port and Ip of server) and return some data
> > to
> > > the server". In Windows we have implemented the same using "winsock.h"
> > but
> > > difficulty here is i don't have any idea which header will have the
> > > information about socket in UEFI ( how to open a socket and send some
> > > buffer). Any link that explain socket programming in UEFI will really
> > help
> > > me, if any one has the same please reply to this mail chain.
> > >
> > >
> > > *Thanks,*
> > >
> > > *~ParthaS*
> > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > >
> > > ------------------------------
> > >
> > > Message: 4
> > > Date: Mon, 16 Mar 2015 04:23:08 -0600
> > > From: Bruce Cran <bruce.c...@gmail.com<mailto:bruce.c...@gmail.com
> ><mailto:bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>
> > > ><mailto:bruce.c...@gmail.com<mailto:bruce.c...@gmail.com><mailto:
> bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>>>>
> > > Subject: Re: [edk2] [Patch] ShellPkg: Fix typo in ShellPkg.
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>, "Carsey, Jaben"
> > > <jaben.car...@intel.com<mailto:jaben.car...@intel.com><mailto:
> jaben.car...@intel.com<mailto:jaben.car...@intel.com>><mailto:
> > > jaben.car...@intel.com<mailto:jaben.car...@intel.com><mailto:
> jaben.car...@intel.com<mailto:jaben.car...@intel.com>>>>
> > > Message-ID: <5506af0c.3020...@gmail.com<mailto:
> 5506af0c.3020...@gmail.com><mailto:
> > 5506af0c.3020...@gmail.com<mailto:5506af0c.3020...@gmail.com>
> > > ><mailto:5506af0c.3020...@gmail.com<mailto:5506af0c.3020...@gmail.com
> ><mailto:5506af0c.3020...@gmail.com<mailto:5506af0c.3020...@gmail.com>>>>
> > > Content-Type: text/plain; charset=windows-1252; format=flowed
> > >
> > > On 3/15/2015 8:14 PM, Qiu, Shumin wrote:
> > > > Thanks for your comments. Update the patch.
> > >
> > > Reviewed-by: Bruce Cran <bruce.c...@gmail.com<mailto:
> bruce.c...@gmail.com><mailto:
> > bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>
> > > ><mailto:bruce.c...@gmail.com<mailto:bruce.c...@gmail.com><mailto:
> bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>>>>
> > >
> > > --
> > > Bruce
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 5
> > > Date: Mon, 16 Mar 2015 04:23:08 -0600
> > > From: Bruce Cran <bruce.c...@gmail.com<mailto:bruce.c...@gmail.com
> ><mailto:bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>
> > > ><mailto:bruce.c...@gmail.com<mailto:bruce.c...@gmail.com><mailto:
> bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>>>>
> > > Subject: Re: [edk2] [Patch] ShellPkg: Fix typo in ShellPkg.
> > > To: edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>><mailto:
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > > <mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > Message-ID: <5506af0c.3020...@gmail.com<mailto:
> 5506af0c.3020...@gmail.com><mailto:
> > 5506af0c.3020...@gmail.com<mailto:5506af0c.3020...@gmail.com>
> > > ><mailto:5506af0c.3020...@gmail.com<mailto:5506af0c.3020...@gmail.com
> ><mailto:5506af0c.3020...@gmail.com<mailto:5506af0c.3020...@gmail.com>>>>
> > > Content-Type: text/plain; charset=windows-1252; format=flowed
> > >
> > > On 3/15/2015 8:14 PM, Qiu, Shumin wrote:
> > > > Thanks for your comments. Update the patch.
> > >
> > > Reviewed-by: Bruce Cran <bruce.c...@gmail.com<mailto:
> bruce.c...@gmail.com><mailto:
> > bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>
> > > ><mailto:bruce.c...@gmail.com<mailto:bruce.c...@gmail.com><mailto:
> bruce.c...@gmail.com<mailto:bruce.c...@gmail.com>>>>
> > >
> > > --
> > > Bruce
> > >
> > >
> > >
> > >
> > > ------------------------------
> > >
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Dive into the World of Parallel Programming The Go Parallel Website,
> > > sponsored
> > > by Intel and developed in partnership with Slashdot Media, is your hub
> > for
> > > all
> > > things parallel software development, from weekly thought leadership
> > blogs
> > > to
> > > news, videos, case studies, tutorials and more. Take a look and join
> the
> > > conversation now. http://goparallel.sourceforge.net/
> > >
> > > ------------------------------
> > >
> > > _______________________________________________
> > > edk2-devel mailing list
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:edk2-devel@lists.sourceforge.net
> <mailto:edk2-devel@lists.sourceforge.net>
> > > ><mailto:edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>>>
> > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > >
> > >
> > > End of edk2-devel Digest, Vol 63, Issue 70
> > > ******************************************
> > >
> > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > >
> > > ------------------------------
> > >
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Dive into the World of Parallel Programming The Go Parallel Website,
> > > sponsored
> > > by Intel and developed in partnership with Slashdot Media, is your hub
> > for
> > > all
> > > things parallel software development, from weekly thought leadership
> > blogs
> > > to
> > > news, videos, case studies, tutorials and more. Take a look and join
> the
> > > conversation now. http://goparallel.sourceforge.net/
> > >
> > > ------------------------------
> > >
> > > _______________________________________________
> > > edk2-devel mailing list
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net><mailto:edk2-devel@lists.sourceforge.net
> <mailto:edk2-devel@lists.sourceforge.net>
> > >
> > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > >
> > >
> > > End of edk2-devel Digest, Vol 63, Issue 74
> > > ******************************************
> > >
> > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > >
> > > ------------------------------
> > >
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Dive into the World of Parallel Programming The Go Parallel Website,
> > > sponsored
> > > by Intel and developed in partnership with Slashdot Media, is your hub
> > for
> > > all
> > > things parallel software development, from weekly thought leadership
> > blogs
> > > to
> > > news, videos, case studies, tutorials and more. Take a look and join
> the
> > > conversation now. http://goparallel.sourceforge.net/
> > >
> > > ------------------------------
> > >
> > > _______________________________________________
> > > edk2-devel mailing list
> > > edk2-devel@lists.sourceforge.net<mailto:
> edk2-devel@lists.sourceforge.net>
> > > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> > >
> > >
> > > End of edk2-devel Digest, Vol 63, Issue 85
> > > ******************************************
> > >
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> >
> > ------------------------------
> >
> >
> >
> ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming The Go Parallel Website,
> > sponsored
> > by Intel and developed in partnership with Slashdot Media, is your hub
> for
> > all
> > things parallel software development, from weekly thought leadership
> blogs
> > to
> > news, videos, case studies, tutorials and more. Take a look and join the
> > conversation now. http://goparallel.sourceforge.net/
> >
> > ------------------------------
> >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net
> >
> > https://lists.sourceforge.net/lists/listinfo/edk2-devel
> >
> >
> > End of edk2-devel Digest, Vol 63, Issue 87
> > ******************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
>
> ------------------------------
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>
> End of edk2-devel Digest, Vol 63, Issue 95
> ******************************************
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
>
> ------------------------------
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/edk2-devel
>
>
> End of edk2-devel Digest, Vol 63, Issue 115
> *******************************************
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
