[U-Boot] Uboot as x86_64 EFI payload

[Juan Alfonso Reyes Ajenjo <jareyes@gmv.com>]

Hi,
I am Juan Alfonso Reyes, a firmware engineer in GMV. Currently we are developing new boards based in Apollo Lake CPU.  We are trying to load uboot from UEFI. Using the default qemu-x86_efi_payload64_defconfig  we are getting "U-Boot EFI Payload 2002 No memory map" error code.
As I can see in the code 2002 means (efi_stub.c):

ret = boot->get_memory_map(&size, NULL, &key, &desc_size, &version);
            if (ret != EFI_BUFFER_TOO_SMALL) {
                        printhex2(BITS_PER_LONG);
                        printhex2(ret);
                        puts(" No memory map\n");
                        while(1);
                        return ret;
            }

0x20   -> BITS_PER_LONG 32bits
0x02 -> EFI_INVALID_PARAMETER

32bits sounds weird for me, so I changed config to use CONFIG_X86_RUN_64BIT instead of CONFIG_X86_RUN_32BIT. I have changed it and I got a compilation error:

In file included from include/common.h:53:0,
                 from cmd/efi.c:8:
cmd/efi.c: In function 'do_efi_mem':
./arch/x86/include/asm/global_data.h:117:12: error: 'global_data_ptr' undeclared (first use in this function)
#define gd global_data_ptr


I have surfed in the code and I have found this in ./arch/x86/include/asm/global_data.h

# if defined(CONFIG_EFI_APP) || CONFIG_IS_ENABLED(X86_64)
/* TODO(sjg at chromium.org<mailto:sjg@chromium.org>): Consider using a fixed register for gd on x86_64 */
#define gd global_data_ptr

What do you mean with "Consider using a fixed register for gd" ?Can you help us to make this work? Are we in the correct direction?

Thank you very much,

Best regards,
________________________________
[cid:image001.gif at 01D39918.97D8D0B0]

Juan Alfonso Reyes Ajenjo
Ingeniero en Informatica / Computer Systems Engineer
Ingeniero en Automática y Electrónica Industrial / Automation and Industrial Electronics Engineer

GMV
Juan de Herrera nº17
Boecillo
E-47151 Valladolid
Tel. +34 983 54 65 54
Fax +34 983 54 65 53
www.gmv.com <http://www.gmv.com/>
[cid:image002.png at 01D39918.97D8D0B0]<http://www.facebook.com/infoGMV>

[cid:image003.png at 01D39918.97D8D0B0]<http://www.twitter.com/infoGMV_es>

[cid:image004.png at 01D39918.97D8D0B0]<https://plus.google.com/+Gmvcompany>

[cid:image005.png at 01D39918.97D8D0B0]<http://www.youtube.com/infoGMV>

[cid:image006.png at 01D39918.97D8D0B0]<https://www.linkedin.com/company/gmv>

[cid:image007.png at 01D39918.97D8D0B0]<http://www.gmv.com/en/RSS>


[cid:image008.png at 01D39918.97D8D0B0]<http://www.gmv.com/blog_gmv/language/en/>






P Please consider the environment before printing this e-mail.

______________________
This message including any attachments may contain confidential 
information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
 en el marco de su Sistema de Gestion de Seguridad de la 
Informacion siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgacion copia o distribucion a terceros sin la 
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
 erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
Gracias por su colaboracion.

______________________

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 5711 bytes
Desc: image001.gif
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2914 bytes
Desc: image002.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2946 bytes
Desc: image003.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 3037 bytes
Desc: image004.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 3026 bytes
Desc: image005.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2913 bytes
Desc: image006.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 3042 bytes
Desc: image007.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 4932 bytes
Desc: image008.png
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180129/69241f8e/attachment-0006.png>