Jack, iscsi driver lays on top of undi driver so you need a undi nic driver
first.
在 2013年10月27日 下午11:15， 写道：
> Dear Jeff,
>
>
>
> Thanks for your rapid reply.
>
> I used the VMware 10 EFI for testing.
>
> My test steps as below
>
> 1. After building EDK2, copy shell.efi and IscsiDxe.efi to
Hi Sathya,
To your question, no. Most of memory region reserved as
EfiRuntimeServicesData will NOT be reported in RMRR table.
VT-d spec:
" BIOS allocated reserved memory ranges that may be DMA
targets. BIOS may report each such reserved memory region through the RMRR
structures, along
with t
since you are working on application why not copy to usb thumb drive, load
it from uefi shell and manual bind to your pci device? in case errors then
rebuild, copy and load again, no need to reboot system.
在 2013-5-6 下午10:20，"Saheb Biswas" 写道：
> Hi,
>
> I am a beginner in UEFI development and movi
Hi Ramesh,
In which case please if the OpROM is for a storage class device?
Thanks,
Tao
On Thu, Nov 1, 2012 at 8:33 AM, Ramesh Raju wrote:
> There is a case that CsmBlockio is not handling the option rom.
>
>
>
> Thanks,
>
> Ramesh
>
>
> -------
BlockIo is a trunk and once legacy OpROM executed it will marked the device
handler as ALREADY_STARTED and how UEFI driver can get started on the same
device handle? The same thing apply to UEFI first then blockio wil not
able to start on that device handler so I believe it will be a bug if on
som
Hi all,
Though my question is not connected with EDKII, may I have some help on
my question about CoreInitializeGcdServices ?
CoreInitializeGcdServices will init memory map and IO space map, walk the
Hob list to add all resources in resource descriptors to GCD, this is easy
to understand since
Hi Ting,
Thanks a lot!
Best regards,
Tao
On Wed, Sep 26, 2012 at 11:04 PM, Ye, Ting wrote:
> See below.
>
> ** **
>
> *From:* Tao Yuan [mailto:yuanta...@gmail.com]
> *Sent:* Thursday, September 27, 2012 10:07 AM
> *To:* edk2-devel@lists.sourceforge.net
> *Subjec
Tcp.supported called first, then IP6
TCPDriverBindingSupported() fail since it failed to locate
Ip6ServiceBinding Protocol
then
Ip6DriverBingdingSupported get called, return EFI_SUCCESS, then
Ip6DriverBindingStart() get called and install Ip6ServiceBindingProtocol.
Will TCPDriverBindingSupporte
Hi all,
By use EDKII iSCSI and Network stack I met problems to map iSCSI target
to local block devices, when check on serial log I found following:
Intel(R) PRO/1000 5.1.01 PCI-E .Start(7EE7DC20)=EFI_SUCCESS
PciBus: SetAttributes(1) @ B0|D1|F0 Attr=0x8000; Capab=0x80078763;
Status=EFI_SU
