Re: [edk2] Why two places for network code in EDK2?

Subject: Re: [edk2] Why two places for network code in EDK2?

From: "Ye, Ting" <ting.ye@intel.com>

To: Blibbet <blibbet@gmail.com>, "edk2-devel@lists.sourceforge.net" <edk2-devel@lists.sourceforge.net>

Date: 2014-05-08 15:10:16

As I known, IPv4 network commands are already in UEFI shell tree like ping and ifconfig. IPv6 commands are not integrated to UEFI shell yet. The reason might be UEFI shell spec excludes IPv6 network commands. Shell spec owner can correct me if I am wrong.

Best Regards,
Ye Ting

-----Original Message-----
From: Blibbet [mailto:blibbet@gmail.com] 
Sent: Thursday, May 08, 2014 11:12 AM
To: edk2-devel@lists.sourceforge.net
Cc: Ye, Ting
Subject: Re: [edk2] Why two places for network code in EDK2?

On a related note, shouldn't some of the IPv4 and IPv6 network shell 
commands in the network tree possibly be moved to the UEFI Shell tree, 
and at least integrated with the shell profiles/levels build, so that 
these profiles/levels are up-to-date with the available commands?

Thanks,
Lee

On 5/7/14 6:13 PM, Ye, Ting wrote:
> NetworkPkg is a package added to support EFI IPv6 stack. TCP in NetworkPkg supports dual network stack, while TCP module in MdeModulePkg supports IPv4 stack only.
>
> Best Regards,
> Ye Ting


------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel