search for: efi_guid

...ServiceBinding based on Pxebc but fall back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it works. Everything is done within efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) from image_DeviceHandle I get the right DevPath handle, I parse it and I get the MAC address. Next I LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles) what gives me all the handles that include the Service Binding Protocol "bguid". For each o...

...I > timeout (5 minutes). > > Signed-off-by: Julien Viard de Galbert <jviarddegalbert at online.net> > --- > efi/udp.c | 24 ++---------------------- > 1 file changed, 2 insertions(+), 22 deletions(-) That almost certainly explains the decaying download rates. > extern EFI_GUID Udp4ServiceBindingProtocol, Udp4Protocol; > > -/* > - * This UDP binding is configured to operate in promiscuous mode. It is > - * only used for reading packets. It has no associated state unlike > - * socket->net.efi.binding, which has a remote IP address and port > - * number...

...NDLE image_handle, pxe_handle; > > struct screen_info; > extern void setup_screen(struct screen_info *); > diff --git a/efi/main.c b/efi/main.c > index 208fee4..6e43f79 100644 > --- a/efi/main.c > +++ b/efi/main.c > @@ -40,36 +40,27 @@ efi_close_protocol(EFI_HANDLE handle, EFI_GUID *guid, EFI_HANDLE agent, > guid, agent, controller); > } > > +/* As of UEFI-2.4.0, all EFI_SERVICE_BINDINGs are for networking */ > struct efi_binding *efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) > { > EFI_SERVICE_BINDING *sbp; >...

...set of PXE parameters. It seems to work. It would be really interesting if the HP guys having this issue can give it a try... Please see the new code at https://github.com/ppatpat/syslinux/blob/master/efi/main.c Patched: efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) {} efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) {} Best, Patrick

On Wed, May 31, 2017 at 10:06 AM, Matt Fleming <matt at codeblueprint.co.uk> wrote: > On Wed, 31 May, at 07:45:00AM, Gene Cumm wrote: >> > extern EFI_GUID Udp4ServiceBindingProtocol, Udp4Protocol; >> > >> > -/* >> > - * This UDP binding is configured to operate in promiscuous mode. It is >> > - * only used for reading packets. It has no associated state unlike >> > - * socket->net.efi.binding, which has...

...ll back to MAC-based searching, > saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle. > Presumably the UDP and TCP handles _should_ be the same... > -- > -Gene > <<< > > OK now it works. > Everything is done within efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) > from image_DeviceHandle I get the right DevPath handle, I parse it and I get the MAC address. > Next I LibLocateHandle(ByProtocol, bguid, NULL, &nr_handles, &handles) > what gives me all the handles that include the Service Binding Protocol "bguid&qu...

...> It would be really interesting if the HP guys having this issue can give it a try... > > > Please see the new code at > https://github.com/ppatpat/syslinux/blob/master/efi/main.c > > Patched: > efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) {} > efi_create_binding(EFI_GUID *bguid, EFI_GUID *pguid) {} Debating if this hunting should be more persistent so we don't go hunting at every binding. It shouldn't affect large files but could affect lots of tiny files if we're hunting every time. If it's to be more persistent, a table of known GUIDs to match...

...ix to the 'master' branch. Thanks for the report! protocol.h | 13 ------------- 1 files changed, 0 insertions(+), 13 deletions(-) diff --git a/protocol.h b/protocol.h index 88b4a7b..6881d70 100644 --- a/protocol.h +++ b/protocol.h @@ -51,19 +51,6 @@ handle_protocol(EFI_HANDLE handle, EFI_GUID *protocol, void **interface) } /** - * locate_protocol - Returns the first protocol instance for @protocol - * @protocol: the protocol to search for - * @registration: optional registration key - * @interface: used to return a pointer to the first matching interface - */ -static inline EFI_STAT...

From: Sylvain Gault <sylvain.gault at gmail.com> I don't know if I should merge those trivial warning fix into one commit. I can reformat it as requested. Those are a few warning fixes for the efi part. The code involved has mainly been introduced in recent commits. Sylvain Gault (3): efi: fix warnings about argument types efi: fix pointer-type mismatch assigment warning efi: fix

...{ 0xd3b46f3b, 0xd441, 0x1244, {0x9a, 0x12, 0x0, 0x12, 0x27, 0x3f, 0xc1, 0x4d } } @@ -35,6 +37,11 @@ typedef struct { /// Hypervisor minor version. /// UINT16 VersionMinor; + /// + /// E820 map + /// + EFI_PHYSICAL_ADDRESS E820; + UINT32 E820EntriesCount; } EFI_XEN_INFO; extern EFI_GUID gEfiXenInfoGuid; diff --git a/OvmfPkg/PlatformPei/Xen.h b/OvmfPkg/PlatformPei/Xen.h new file mode 100644 index 0000000..1885ede --- /dev/null +++ b/OvmfPkg/PlatformPei/Xen.h @@ -0,0 +1,44 @@ +/** @file + Ovmf info structure passed by Xen + +Copyright (c) 2013, Wei Liu <wei.liu2@citrix.com> +...

OK there are problems. From https://sourceforge.net/p/edk2/mailman/message/31604654/ ""In current EDKII implementation, all the network servicebinding protocols for a NIC device are installed together on the NIC's device handle, so you can get all of them when you have chosen a special NIC handle."" Unfortunately there are PCs with UEFI implementations not following the

...# dh > handles.txt it's all we need to see the relationship between the NBP's device handle and the Service Binding handles. Did you get handles.txt? is it available for download somewhere? >>> Gene, after modifying some of Patrick's code I have been able to get the EFI_GUID - 83F01464-99BD-45E5-B383AF6305D8E9E6 <<< OK that GUID is EFI_UDP4_SERVICE_BINDING_PROTOCOL_GUID then you bound the required Service Binding protocol. Could you please show us here the modified code? >>> Does this give you the info you need? <<< Depending on your code...

On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Gene > > Thanks for the reply. I didn't have a guid command, and couldn't find the > equivalent. dh > fs0:\efi-dh.txt worked, but dh -p Net did not so I ran dh Nothing of the sort listed with the help command to list the full GUIDs and their aliases? > -d -v -p SimpleNetwork >

Signed-off-by: Julien Viard de Galbert <jviarddegalbert at online.net> --- efi/udp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/efi/udp.c b/efi/udp.c index 1088f47..b0f13ad 100644 --- a/efi/udp.c +++ b/efi/udp.c @@ -163,7 +163,7 @@ void core_udp_connect(struct pxe_pvt_inode *socket, uint32_t ip, } else { udata.UseDefaultAddress = FALSE;

Gene, after modifying some of Patrick's code I have been able to get the EFI_GUID - 83F01464-99BD-45E5-B383AF6305D8E9E6 Does this give you the info you need? On Mon, Aug 17, 2015 at 4:33 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> > wrote: > > Gene > > > > Thanks...

> >>> > Gene, after modifying some of Patrick's code I have been able to get the > EFI_GUID - 83F01464-99BD-45E5-B383AF6305D8E9E6 > <<< > > OK that GUID is EFI_UDP4_SERVICE_BINDING_PROTOCOL_GUID > then you bound the required Service Binding protocol. > Could you please show us here the modified code? > FWIW, http://uefi.blogspot.com/2012/08/how-to-efigui...

>>> If searching for: 83F01464-99BD-45E5-B383AF6305D8E9E6 you might possibly need to search instead for: 83F01464-99BD-45E5-B383-AF6305D8E9E6 or even for: 83f01464-99bd-45e5-b383-af6305d8e9e6 <<< Hi Ady, Those GUIDs are just the text representation of a 16 byte hexadecimal number. The format/case in this context does not really matter. Best, Patrick

...at/case > in this context does not really matter. > > Best, > Patrick > Sure. Note that I started that email with "FWIW" (plus a link to a blog post). In any case, I tend to think that using some kind of "common" way / "format" to refer to these (EFI_GUID) hex values might be helpful, if not for searching information, then at least for easier readability. After all, computers understand "ones and zeroes"... Well, actually, electric charges, but we are not going to be writing here in such scheme / format unless really really really need...

...Signed-off-by: Julien Viard de Galbert <jviarddegalbert at online.net> --- efi/udp.c | 24 ++---------------------- 1 file changed, 2 insertions(+), 22 deletions(-) diff --git a/efi/udp.c b/efi/udp.c index 8f4d7dc..4032d0b 100644 --- a/efi/udp.c +++ b/efi/udp.c @@ -10,14 +10,6 @@ extern EFI_GUID Udp4ServiceBindingProtocol, Udp4Protocol; -/* - * This UDP binding is configured to operate in promiscuous mode. It is - * only used for reading packets. It has no associated state unlike - * socket->net.efi.binding, which has a remote IP address and port - * number. - */ -static struct efi_bi...

On Wed, 31 May, at 07:45:00AM, Gene Cumm wrote: > > extern EFI_GUID Udp4ServiceBindingProtocol, Udp4Protocol; > > > > -/* > > - * This UDP binding is configured to operate in promiscuous mode. It is > > - * only used for reading packets. It has no associated state unlike > > - * socket->net.efi.binding, which has a remote IP address...