After you load the driver do you run the connect command to connect it? That’s
the next step to getting the driver functioning…
From: Ritesh Tiwari [mailto:[email protected]]
Sent: Tuesday, March 10, 2015 10:16 AM
To: [email protected]
Subject: [edk2] Not able to locate EFI_TCP4_PROTOCOL protocol
Hi,
I am trying to write a TCP application. I am seeing
bootservices->LocateProtocol() for EFI_TCP4_PROTOCOL failing. Although TCP4DXE
driver is loaded as per drivers command. But when I load this TCP4DXE driver
manually I don't see EFI_TCP4_PROTOCOL handle is getting installed. I am
testing all this on NT32.
Just wanted to know which driver to load so that I can locate
EFI_TCP4_PROTOCOL? I want to open a TCP socket so that I can communicate with a
remote host.
Thanks.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
