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

2014-05-07 Thread Blibbet
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

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

2014-05-07 Thread Ye, Ting
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 From: Thomas Rognon [mailto:tcrog...@gmail.com] Sent: Thursday, May 08, 2014 7:56 AM To: edk2-devel Subject: [

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

2014-05-07 Thread Thomas Rognon
I've been curious about this for a while. Why is network code both here https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Universal/Network/ and here https://svn.code.sf.net/p/edk2/code/trunk/edk2/NetworkPkg/ ? Some of it is unique (IPv4 in MdeModulePkg vs IPv6 in NetworkPkg) and som

Re: [edk2] ShellPkg: Add a support to query AdapterInfo protocol for Shell ‘dh’ command

2014-05-07 Thread Carsey, Jaben
Reviewed-by: Jaben carsey I will do the commit in just a minute or two. From: Shah, Tapan [mailto:tapands...@hp.com] Sent: Wednesday, May 07, 2014 9:34 AM To: Carsey, Jaben; edk2-devel@lists.sourceforge.net Subject: [edk2] ShellPkg: Add a support to query AdapterInfo protocol for Shell ‘dh’ com

[edk2] ShellPkg: Add a support to query AdapterInfo protocol for Shell ‘dh’ command

2014-05-07 Thread Shah, Tapan
Please review the attached patch file. This patch adds a support to query AdapterInfo protocol for Shell ‘dh’ command. Shell> dh -p AdapterInfo The STR_ADAPTER_INFO string is the only change in UNI file. ShellPkg: Add a support to query AdapterInfo protocol for S

Re: [edk2] Accessing I2C devices under OVMF

2014-05-07 Thread Paolo Bonzini
Il 07/05/2014 04:37, Laszlo Ersek ha scritto: > > I'm not familiar with i2c-bus, but from the qemu code, it looks like you > should check the output of "info mtree". The pc_init1() function calls > piix4_pm_init() with smb_io_base=0xb100. Again from a superficial > reading of the code, this should