search for: image_handl

...+---------- > 3 files changed, 23 insertions(+), 35 deletions(-) > > diff --git a/efi/efi.h b/efi/efi.h > index ef5bacb..1416488 100644 > --- a/efi/efi.h > +++ b/efi/efi.h > @@ -42,7 +42,7 @@ struct efi_binding { > EFI_HANDLE this; > }; > > -extern EFI_HANDLE image_handle; > +extern EFI_HANDLE 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_protoc...

...- if (!map) + map_sz = buf_sz; + status = uefi_call_wrapper(BS->GetMemoryMap, + 5, + &map_sz, + map, + &key, + &desc_sz, + &desc_ver); + if (!map) { + FreePool(map); + return -1; + } + + status = uefi_call_wrapper(BS->ExitBootServices, 2, image_handle, key); + + if (status == EFI_INVALID_PARAMETER) { + /* + * Retry GetMemoryMap() and ExitBootServices() if the + * first try fails per UEFI Spec v2.6, Section 6.4: + * EFI_BOOT_SERVICES.ExitBootServices. + */ + map_sz = buf_sz; + status = uefi_call_wrapper(BS->GetMemoryMap, +...

From: Sylvain Gault <sylvain.gault at gmail.com> On some architecture, including my hardware, the function ExitBootServices may need to be called twice in order to successfully exit the boot services. As stated by the UEFI spec, the first call to ExitBootServices may perform a partial shutdown of the services. It seems that during this partial shutdown, the memory map can be modified, thus

...nt to create a route for any image. This is in order to create an email report explaining what the missing image is. I could create a route for each directory that currently has images in it but wanted something more general like: map.connect "/**/*.gif", :controller => ''image_handler'', :action => ''handle_image'' Which doesn''t work. Anyone know more about the inner workings? Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060315/44ba1c66/at...

...esc_sz, &desc_ver); - if (!map) + map_sz = buf_sz; + status = uefi_call_wrapper(BS->GetMemoryMap, + 5, + &map_sz, + map, + &key, + &desc_sz, + &desc_ver); + if (!map) { + FreePool(map); + return -1; + } + + status = uefi_call_wrapper(BS->ExitBootServices, 2, image_handle, key); + + if (status == EFI_INVALID_PARAMETER) { + /* + * Retry GetMemoryMap() and ExitBootServices() if the + * first try fails per UEFI Spec v2.6, Section 6.4: + * EFI_BOOT_SERVICES.ExitBootServices. + */ + map_sz = buf_sz; + status = uefi_call_wrapper(BS->GetMemoryMap, + 5, + &am...

...ntries, &key, > + &desc_sz, &desc_ver); > + if (!map) > + return -1; > + > + status = uefi_call_wrapper(BS->ExitBootServices, 2, > + image_handle, key); > + retry++; > + } while (status != EFI_SUCCESS && retry < 3); > + > + if (status != EFI_SUCCESS) { > + printf("Failed to exit boot services: 0x%016lx\n", status); > + FreePool(map); >...

...n at commit ID 5186539 > 2.2) I think "image_DeviceHandle" instead of "pxe_DeviceHandle" produces a code easier to follow; > specially when we end up using that handle to create a TCP4 or UDP4 child... Not all handles are devices but all usable devices have handles. The image_handle is a type EFI_LOADED_IMAGE_PROTOCOL, not a device. pxe_handle could perhaps be renamed as nic_handle or device_handle. -- -Gene

...;> > 2.2) > I think "image_DeviceHandle" instead of > "pxe_DeviceHandle" produces a code easier to follow; > specially when we end up using > that handle to create a TCP4 or UDP4 child... Not all handles are devices but all usable devices have handles.? The image_handle is a type EFI_LOADED_IMAGE_PROTOCOL, not a device. pxe_handle could perhaps be renamed as nic_handle or device_handle. -- -Gene <<< We already have "image_handle" that (as you say) corresponds to the EFI_LOADED_IMAGE_PROTOCOL I think that "image_DeviceHandle" w...

...L; + allocsize = 0; + retry = 0; + do { + map = get_memory_map_realloc(map, &allocsize, &nr_entries, &key, + &desc_sz, &desc_ver); + if (!map) + return -1; + + status = uefi_call_wrapper(BS->ExitBootServices, 2, + image_handle, key); + retry++; + } while (status != EFI_SUCCESS && retry < 3); + + if (status != EFI_SUCCESS) { + printf("Failed to exit boot services: 0x%016lx\n", status); + FreePool(map); return -1; + } + bp->efi.memmap = (uint32_t)(unsigned long)map; bp->efi.memmap_si...

...DevicePath = DevicePathFromHandle(handles[i]); if (efi_get_MAC(DevicePath, &mac_2, PXE_MAC_LENGTH) && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == 0) { sb_handle = handles[i]; status = uefi_call_wrapper(BS->OpenProtocol, 6, sb_handle, bguid, (void **)&sbp, image_handle, sb_handle, EFI_OPEN_PROTOCOL_GET_PROTOCOL); if (status == EFI_SUCCESS) { mnpsb_handle = sb_handle; break; } } } } if (status != EFI_SUCCESS) goto free_binding; child = NULL; status = uefi_call_wrapper(sbp->CreateChild, 2, sbp, (EFI_HANDLE *)&a...

...> + map = get_memory_map_realloc(map, &allocsize, > &nr_entries, &key, > + &desc_sz, &desc_ver); > + if (!map) > + return -1; > + > + status = uefi_call_wrapper(BS->ExitBootServices, 2, > + image_handle, key); > + retry++; > + } while (status != EFI_SUCCESS && retry < 3); > + > + if (status != EFI_SUCCESS) { > + printf("Failed to exit boot services: 0x%016lx\n", > status); > + FreePool(map); > return -1; > + } > + > > bp->efi.m...

...&desc_sz, &desc_ver); >>> + if (!map) >>> + return -1; >>> + >>> + status = uefi_call_wrapper(BS->ExitBootServices, 2, >>> + image_handle, key); >>> + retry++; >>> + } while (status != EFI_SUCCESS && retry < 3); >>> + >>> + if (status != EFI_SUCCESS) { >>> + printf("Failed to exit boot services: 0x%016lx\n", >>> status)...

...t; + &desc_sz, &desc_ver); >> + if (!map) >> + return -1; >> + >> + status = uefi_call_wrapper(BS->ExitBootServices, 2, >> + image_handle, key); >> + retry++; >> + } while (status != EFI_SUCCESS && retry < 3); >> + >> + if (status != EFI_SUCCESS) { >> + printf("Failed to exit boot services: 0x%016lx\n", >> status); >> +...

...&desc_sz, &desc_ver); >>>> + if (!map) >>>> + return -1; >>>> + >>>> + status = uefi_call_wrapper(BS->ExitBootServices, 2, >>>> + image_handle, key); >>>> + retry++; >>>> + } while (status != EFI_SUCCESS && retry < 3); >>>> + >>>> + if (status != EFI_SUCCESS) { >>>> + printf("Failed to exit boot services: 0x%016lx\n",...

...uf, size_t kernel_size, + char *cmdline, int cmdlineSize) +{ + +char* szLoadImage = "LoadImage()"; +char* szHandleProtocol = "HandleProtocol()"; +char* szStartImage = "StartImage()"; + +char* action = NULL; + +EFI_LOADED_IMAGE * image_info = NULL; +EFI_HANDLE Child_image_handle; +EFI_LOADED_IMAGE * Child_image_info = NULL; +EFI_STATUS status; + +CHAR16 w_emptyCmdLine [4]={0,0,0,0}; + + + +status = uefi_call_wrapper(BS->HandleProtocol, 3, image_handle, + &LoadedImageProtocol,(void**)&image_info); +if(status != EFI_SUCCESS) + { + action=szHandleProtocol;...

...+ > +char* szLoadImage = "LoadImage()"; > +char* szHandleProtocol = "HandleProtocol()"; > +char* szStartImage = "StartImage()"; > + > +char* action = NULL; > + > +EFI_LOADED_IMAGE * image_info = NULL; > +EFI_HANDLE Child_image_handle; > +EFI_LOADED_IMAGE * Child_image_info = NULL; > +EFI_STATUS status; > + > +CHAR16 w_emptyCmdLine [4]={0,0,0,0}; > + > + > + > +status = uefi_call_wrapper(BS->HandleProtocol, 3, image_handle, > + &LoadedImageProtocol,...

...amp;& memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == 0) { > sb_handle = handles[i]; > status = uefi_call_wrapper(BS->OpenProtocol, 6, sb_handle, > bguid, (void **)&sbp, > image_handle, sb_handle, > EFI_OPEN_PROTOCOL_GET_PROTOCOL); > if (status == EFI_SUCCESS) { > mnpsb_handle = sb_handle; > break; > } > } > > } > > }...

Signed-off-by: Beno?t Allard <benoit.allard at greenbone.net> --- efi/fio.h | 9 --------- 1 file changed, 9 deletions(-) diff --git a/efi/fio.h b/efi/fio.h index 65fff8d..a1bfe68 100644 --- a/efi/fio.h +++ b/efi/fio.h @@ -11,15 +11,6 @@ #define MAX_EFI_ARGS 64 #define WS(c16) (c16 == L' ' || c16 == CHAR_TAB) -/* VPrint is not in export declarations in gnu-efi lib yet

On Thu, Jun 25, 2015 at 7:28 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 25, 2015 at 11:54 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >> Yes I know what you mean; >> "I think" the handle of the running image (our code) has a "path" telling us where >> was laded from. That would solve this thing. > > I just

On Fri, Aug 28, 2015 at 03:34:12AM -0700, Patrick Masotta via Syslinux wrote: Derrick wrote: > > More importantly: look at the actual captured text.? It does NOT > > specify a valid MAC in its entirety and leaves off the leading nibble > > (11 characters, not 12).? Handle 267 shows "065F36E00EE" not "0065F36E00EE". > > I saw that, they might even be