Menu
▾
▴
efidevkit-devel — EFI Dev Kit (EDK) developer discussions
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(8) |
Jun
(11) |
Jul
(5) |
Aug
(1) |
Sep
|
Oct
(12) |
Nov
(5) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
(1) |
Jul
(13) |
Aug
(17) |
Sep
(9) |
Oct
(6) |
Nov
(6) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dhanasekar J <dha...@ve...> - 2017-05-04 12:12:04
|
Hi All, I am trying to build BIOS for Inte Xeon Server v3. But I am not seeing PlatformPkg for v3 in https://github.com/tianocore/edk2. <https://github.com/tianocore/edk2> Where can I get PlatformPkg for v3? Is it possible to boot Intel Server by open UEFI source without BIOS vendor help?. Is Intel providing FSP support Xeon server v3?. Can I able to boot xeon sever v3 with FSP? Thanks, Dhanasekar |
|
From: Amit K. <ami...@ya...> - 2013-12-11 06:49:27
|
Hi All, Please ignore my previous mail. I am very new to developing UEFI applications using UDK. I have just installed UDK, EADK and compiled it with VS2010. When I started looking at different samples provided(Main, Hello, HelloWorld etc) I observed that in HelloWorld you can access boot/runtime services but you don't have C libraries available there. On the other side Main, Hello you can use standard C libraries but at same time I want access to boot/runtime services too. So is there any way to access boot/runtime services in Main/Hello? Thanks & Regards, Amit Kulkarni. |
|
From: Amit K. <ami...@ya...> - 2013-12-11 06:33:25
|
Hi All, I am very new to developing UEFI applications using UDK. I have just installed UDK, EADK and compiled it with VS2010. When I started looking at different samples provided(Main, Hello, HelloWorld etc) I observed that in HelloWorld you can access boot/runtime services but you don't have C libraries available there. On the other side Main, Hello you can use standard C libraries but at same time I want access to boot/runtime services too. So is there any way to access boot/runtime services in Main/Hello? Thanks & Regards, Amit Kulkarni. |
|
From: Jordan J. <jlj...@gm...> - 2013-06-06 22:58:03
|
On Fri, Apr 19, 2013 at 4:06 PM, Jordan Justen <jlj...@gm...> wrote: > I will send out notices when the EDK, EDK II and EDK II Buildtools > projects are migrated. For other projects, please refer to the wiki > page. The EDK II project's svn repository url has now been migrated to a new url. For more information, see: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=2013_Subversion_Change Note: * The old svn url still works, but it is read-only * New changes will only be visible at the new url -Jordan |
|
From: Jordan J. <jlj...@gm...> - 2013-06-06 06:47:22
|
On Fri, Apr 19, 2013 at 4:06 PM, Jordan Justen <jlj...@gm...> wrote: > I will send out notices when the EDK, EDK II and EDK II Buildtools > projects are migrated. For other projects, please refer to the wiki > page. The EDK II Buildtools project's svn repository url has now been migrated to a new url. For more information, see: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=2013_Subversion_Change Note: * The old svn url still works, but I've been told it should now be read-only * New changes should only be visible at the new url * The main EDK II project's svn has not migrated yet -Jordan |
|
From: Jordan J. <jlj...@gm...> - 2013-05-23 22:14:08
|
On Fri, Apr 19, 2013 at 4:06 PM, Jordan Justen <jlj...@gm...> wrote: > I will send out notices when the EDK, EDK II and EDK II Buildtools > projects are migrated. For other projects, please refer to the wiki > page. The original EDK project's svn repository url has now been migrated to a new url. For more information, see: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=2013_Subversion_Change Note: EDK II and EDK II Buildtools still are not migrated. -Jordan |
|
From: Jordan J. <jlj...@gm...> - 2013-04-19 23:06:54
|
SourceForge is making a change to project hosting that will eventually force all of our subversion source control URLs to change. (It appears they will change the old URL into read-only mode. I don't yet know if it will see newer commits following the change.) They are currently migrating all inactive projects to the newer system, but they will be starting to migrate active projects next week. There is no way to tell when they will upgrade our more active projects (like EDK II), but it could happen as early as next Monday. I have made this wiki page that will have information on updating your subversion tree based on this change: http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=2013_Subversion_Change Please let me know if any other information is needed on the wiki page. I will send out notices when the EDK, EDK II and EDK II Buildtools projects are migrated. For other projects, please refer to the wiki page. -Jordan |
|
From: Alan E. <ala...@gm...> - 2013-04-18 01:17:16
|
I am trying to use mkramdisk.efi from EFI Toolkit 2.0.0.1 (I apologize if this is not the right place, I saw some other mkramdisk posts so I thought I'd try.) and I am running into problems. I extracted ramdisk.efi and mkramdisk.efi to what is my fs0: but when I try to run it I get the following. Shell> fs0: fs0:\> mkramdisk.efi -d fs0:\ramdisk.efi -s 4 ram0 LoadImage of fs0:\ramdisk.efi returned EFI error 0x8000000000000002 Please assign the ramdisk driver using -d option with full path fs0:\> The shell is the one embedded with my motherboard so I tried Full_Shell.efi from EDK 1.06, same result. Some perhaps useful info: fs0:\> map fs0 Device mapping table fs0 :HardDisk - Alias hd13b blk0 PciRoot(0x0)/Pci(0x3,0x2)/Pci(0x0,0x0)/VenHw(cf31fac5-c24e-11d2-85f3-00a0c93ec93b,80)/HD(1,MBR,0x0000f3b0,0x1,0x4c4b) fs0:\> ver EFI Specification Revision : 2.31 EFI Vendor : American Megatrends EFI Revision : 4.651 I got mkramdisk.efi/ramdisk.efi from http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=EFI_Toolkit Please help and thank you, -Alan |
|
From: Melwyn D. <mel...@gm...> - 2012-08-15 19:13:29
|
I have been looking at various documents ... Are there replacement apis similar to Windows APIs _beginthreadex _endthreadex SetThreadAffinity I would like to start thread, exit thread and assign the thread to a specific Core or a Core Thread... I would like to use these in a UEFI application.. I am looking for the above apis for UEFI or EDK2 Does anyone have an idea how to achieve same or similar to above functions... basically start a thread exit a thread assign the thread to Core or a Core Thread ? Thanks, Melwyn |
|
From: Glenn B. <gl...@my...> - 2012-06-06 23:43:17
|
If you're porting to C++, "decltype". http://en.wikipedia.org/wiki/Decltype |
|
From: Ian N. <ian...@ho...> - 2012-06-06 21:33:13
|
Hello,
I inherit some gcc driver code and I'm porting a part of it to my EBC driver.
What's the equivalent of gcc typeof or how to implement the equivalent?
In particular, I'm having problem with this line of code:
list_for_each_entry_safe_from(bn, _bn, &dev->bvec_list.lh, lh)
1.Since list_for_each_entry_safe_from(pos, n, head, member) is defined as:
for (n = list_entry(pos->member.next, typeof(*pos), member); &pos->member != (head); pos = n, n = list_entry(n->member.next, typeof(*n), member))
2. And list_entry(ptr, type, member) = container_of(ptr, type, member)
3. #define container_of(ptr, type, member) ({ \
const typeof( ((type *)0)->member ) *__mptr = (ptr);
(type *)( (char *)__mptr - offsetof(type,member) );})
By the time I expand all arguments, I'm hopelessly lost (:
Any suggestions?
Thanks!
|
|
From: Ian N. <ian...@ho...> - 2012-06-01 00:07:56
|
Hello,
Doing a build of OptionRomPkg, I got the AtapiPassThruDxe.efi and AtapiPassThruDxe.rom
Using load AtapiPassThruDxe.efi, I always failed in AtapiScsiPassThruDriverBindingSupported () as soon as I loaded
Status = gBS->OpenProtocol (
Controller,
&gEfiPciIoProtocolGuid,
(VOID **) &PciIo,
This->DriverBindingHandle,
Controller,
EFI_OPEN_PROTOCOL_BY_DRIVER
);
So, what's the reason?
I've
an Asus P8H67V motherboard with EFI BIOS and it has an IDE connector on
it. An IDE drive is hooked up and in EFI shell, I see it as fs0:
Thanks!
|
|
From: Jarlstrom, L. <lau...@in...> - 2012-04-05 16:21:10
|
Hi Amin, First I would suggest you subscribe to the EDK 2 Development mailing list edk...@li...<mailto:edk...@li...> at: https://lists.sourceforge.net/lists/listinfo/edk2-devel This mailing list has a board list of EDK 2 Developers helping with UEFI Development. Are you looking at the OvmfPkg to use with QEMU? What would you like to do? Write a UEFI application? Would you like to use the Shell protocols? thanks, Laurie thanks, Laurie lau...@in...<mailto:lau...@in...> EFI / Framework Technical Marketing Engineering Team (503) 712-9395 From: Amin Sa [mailto:ami...@gm...] Sent: Thursday, April 05, 2012 5:20 AM To: efi...@li... Subject: [edk] efi - where is the main hey, Right now I'm working in UEFI protocol. I have already set up the environment (EDKII) and tested the protocol in Qemu and it works fine. the thing is when I look at the code I don't find any main() !!! I want to understand the code, any tips? what is the sequence of the code? appreciate your helping, aminonsh |
|
From: Amin Sa <ami...@gm...> - 2012-04-05 12:20:12
|
hey, Right now I'm working in UEFI protocol. I have already set up the environment (EDKII) and tested the protocol in Qemu and it works fine. the thing is when I look at the code I don't find any main() !!! I want to understand the code, any tips? what is the sequence of the code? appreciate your helping, aminonsh |
|
From: Suraj J. <sur...@ze...> - 2011-11-07 05:35:08
|
Hello Folks, I am doing R&D on EFI APIs and protocols. Are there any EFI / ATAPI for doing tray open/ close operations of Optical media (CV/DVD)? Waiting for your earliest response. Thanks in advance. Regards, Suraj Joshi |
|
From: Daniel M. <dan...@er...> - 2011-11-02 13:11:15
|
Btw, I know that the BLOCK_SIZE option extension can be used to have up to 4.29GB of maximum file size. Nevertheless a 1024 bytes block size is used (limited by the server) and cannot be changed. Thanks BR Daniel ________________________________ From: Daniel Moral [mailto:dan...@er...] Sent: Wednesday, November 02, 2011 2:10 PM To: edk...@li...; efi...@li... Subject: Re: [edk2] MTFTP4 Protocol - Wrapping I will provide more information. I ran a test in which a TFTP client using the MTFTP4 protocol asks to read a file from a TFTP server. This is what happens: -> DATA(#65533) <- ACK(#65533) -> DATA(#65534) <- ACK(#65534) -> DATA(#65535) <- ACK(#0) -> DATA(#65535) -> DATA(#65535) -> DATA(#65535) The ->DATA(#BLOCK_NUMBER) is sent by the TFTP server. The <-ACK(#BLOCK_NUMBER) is sent by a TFTP application using the MTFTP4 driver. The behavior is clearly incorrect because ACK=0 should be only used by the TFTP server (according to TFTP's RFC number 1350). And it should be used only when the client asks for a write request, which is not the case. Any ideas? Thanks ________________________________ From: Daniel Moral [mailto:dan...@er...] Sent: Wednesday, November 02, 2011 1:48 PM To: edk...@li...; efi...@li... Subject: [edk2] MTFTP4 Protocol - Wrapping Hi all, This is a simple question in case you have worked with MTFTP4. This protocol has 2 bytes for the block sequence numbers. Therefore the maximum sequence number is 65535. Some servers, after the block 65535 has been sent, are able to wrap the numbers and start with the block number 0 again. Therefore, there would not be a file limit. My question is, the MTFTP4 protocol has this behavior? Or it does not wrap numbers? (i.e it finishes in seq number 65535 and does not continue) Thanks BR Daniel |
|
From: Daniel M. <dan...@er...> - 2011-11-02 13:09:54
|
I will provide more information. I ran a test in which a TFTP client using the MTFTP4 protocol asks to read a file from a TFTP server. This is what happens: -> DATA(#65533) <- ACK(#65533) -> DATA(#65534) <- ACK(#65534) -> DATA(#65535) <- ACK(#0) -> DATA(#65535) -> DATA(#65535) -> DATA(#65535) The ->DATA(#BLOCK_NUMBER) is sent by the TFTP server. The <-ACK(#BLOCK_NUMBER) is sent by a TFTP application using the MTFTP4 driver. The behavior is clearly incorrect because ACK=0 should be only used by the TFTP server (according to TFTP's RFC number 1350). And it should be used only when the client asks for a write request, which is not the case. Any ideas? Thanks ________________________________ From: Daniel Moral [mailto:dan...@er...] Sent: Wednesday, November 02, 2011 1:48 PM To: edk...@li...; efi...@li... Subject: [edk2] MTFTP4 Protocol - Wrapping Hi all, This is a simple question in case you have worked with MTFTP4. This protocol has 2 bytes for the block sequence numbers. Therefore the maximum sequence number is 65535. Some servers, after the block 65535 has been sent, are able to wrap the numbers and start with the block number 0 again. Therefore, there would not be a file limit. My question is, the MTFTP4 protocol has this behavior? Or it does not wrap numbers? (i.e it finishes in seq number 65535 and does not continue) Thanks BR Daniel |
|
From: Daniel M. <dan...@er...> - 2011-11-02 12:47:52
|
Hi all, This is a simple question in case you have worked with MTFTP4. This protocol has 2 bytes for the block sequence numbers. Therefore the maximum sequence number is 65535. Some servers, after the block 65535 has been sent, are able to wrap the numbers and start with the block number 0 again. Therefore, there would not be a file limit. My question is, the MTFTP4 protocol has this behavior? Or it does not wrap numbers? (i.e it finishes in seq number 65535 and does not continue) Thanks BR Daniel |
|
From: Tian, H. <hot...@in...> - 2011-10-21 02:01:23
|
Could you provide more details on which EFI reference implementation has such issue? Thanks, Hot -----Original Message----- From: Terry Lambert [mailto:tla...@ch...] Sent: Friday, October 21, 2011 7:45 AM To: efi...@li... Subject: [edk] EFI_MEMORY_DESCRIPTOR with improper EFI_MEMORY_RUNTIME attribute Not sure if this is the place to report it, but I see no "report an issue" link, and this seems to be the right people... We've worked around this in Linux using local patches; however, it would be nice if the EFI reference implementation could be fixed as a strategy for getting the fix out to everyone who has used it for their own implementations, which is practically everyone. -- This appears to be an issue in the reference implementation which has been copied by most EFI implementations... One or more EFI_MEMORY_DESCRIPTOR entries improperly fail to set the EFI_MEMORY_RUNTIME attribute, but are referenced in the runtime services call SetVirtualAddressMap(). When an program calls ExitBootServices() and immediately does a recovery of the pages referenced by descriptors lacking the EFI_MEMORY_RUNTIME attribute, a subsequent call to SetVirtualAddressMap() can fail as a result of the recovered pages either not being mapped or having their contents modified through reuse. Steps to Reproduce: For EFI vendors, an easy debug strategy for this would be to: [case #1: data reference] pattern-wipe all the pages marked as only being used by boot services in the ExitBootServices() implementation itself, and detect the pattern in the failure case. [case #2: instruction reference] would be to wipe the pages with NOPs and put a code trampoline at the end of the page to indicate which page block was being jumped into by the offending call - jump anywhere in the page and you NOP until the trampoline and jump to the debug frame with page block specific register indicators. A small test implementation in an area known to not be used by EFI that then calls ExitBootServices() and SetVirtualAddressMap() would be sufficient to trigger the problem for both these test cases. -- Terry ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ efidevkit-devel mailing list efi...@li... https://lists.sourceforge.net/lists/listinfo/efidevkit-devel |
|
From: Terry L. <tla...@ch...> - 2011-10-20 23:44:51
|
Not sure if this is the place to report it, but I see no "report an issue" link, and this seems to be the right people... We've worked around this in Linux using local patches; however, it would be nice if the EFI reference implementation could be fixed as a strategy for getting the fix out to everyone who has used it for their own implementations, which is practically everyone. -- This appears to be an issue in the reference implementation which has been copied by most EFI implementations... One or more EFI_MEMORY_DESCRIPTOR entries improperly fail to set the EFI_MEMORY_RUNTIME attribute, but are referenced in the runtime services call SetVirtualAddressMap(). When an program calls ExitBootServices() and immediately does a recovery of the pages referenced by descriptors lacking the EFI_MEMORY_RUNTIME attribute, a subsequent call to SetVirtualAddressMap() can fail as a result of the recovered pages either not being mapped or having their contents modified through reuse. Steps to Reproduce: For EFI vendors, an easy debug strategy for this would be to: [case #1: data reference] pattern-wipe all the pages marked as only being used by boot services in the ExitBootServices() implementation itself, and detect the pattern in the failure case. [case #2: instruction reference] would be to wipe the pages with NOPs and put a code trampoline at the end of the page to indicate which page block was being jumped into by the offending call - jump anywhere in the page and you NOP until the trampoline and jump to the debug frame with page block specific register indicators. A small test implementation in an area known to not be used by EFI that then calls ExitBootServices() and SetVirtualAddressMap() would be sufficient to trigger the problem for both these test cases. -- Terry |
|
From: Kashif M. <ka...@nv...> - 2011-10-17 23:59:22
|
Jaben, Thank you. I originally downloaded the UDK 2010 UP4 package but couldn't find it there. But I do see at the link that you mentioned and also I found it when I downloaded the individual Shell package. Thanks. Kashif... On Mon, Oct 17, 2011 at 4:33 PM, Carsey, Jaben <jab...@in...>wrote: > Oops. I had a caps lock malfunction there.**** > > ** ** > > EDK II UEFI Shell ( > https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/ShellPkg) has > that command in it.**** > > ** ** > > -Jaben**** > > ** ** > > *From:* Carsey, Jaben > *Sent:* Monday, October 17, 2011 4:32 PM > *To:* efi...@li... > *Cc:* Carsey, Jaben > *Subject:* RE: [edk] Loading a driver from EFS**** > > ** ** > > That command is not part of the EDK shell. I would suggest THAT YOU MOVE > TO THE EDK II version of the shell.**** > > ** ** > > -Jaben**** > > ** ** > > *From:* Kashif Memon [mailto:ka...@nv...] > *Sent:* Monday, October 17, 2011 4:10 PM > *To:* efi...@li... > *Subject:* [edk] Loading a driver from EFS**** > > ** ** > > Hello,**** > > > I need to modify the NVRAM variables to load a driver from the EFI system > partititon. > As far as I understand, this can be done using the bcfg command in Shell. > > Only problem is I can't find bcfg in the Shell binary/source that I > downloaded. > If someone can point out where I can find it that will be great, maybe I am > missing something obvious. > > Thanks. > Kashif...**** > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2d-oct > _______________________________________________ > efidevkit-devel mailing list > efi...@li... > https://lists.sourceforge.net/lists/listinfo/efidevkit-devel > > |
|
From: Carsey, J. <jab...@in...> - 2011-10-17 23:33:55
|
Oops. I had a caps lock malfunction there. EDK II UEFI Shell (https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/ShellPkg) has that command in it. -Jaben From: Carsey, Jaben Sent: Monday, October 17, 2011 4:32 PM To: efi...@li... Cc: Carsey, Jaben Subject: RE: [edk] Loading a driver from EFS That command is not part of the EDK shell. I would suggest THAT YOU MOVE TO THE EDK II version of the shell. -Jaben From: Kashif Memon [mailto:ka...@nv...] Sent: Monday, October 17, 2011 4:10 PM To: efi...@li... Subject: [edk] Loading a driver from EFS Hello, I need to modify the NVRAM variables to load a driver from the EFI system partititon. As far as I understand, this can be done using the bcfg command in Shell. Only problem is I can't find bcfg in the Shell binary/source that I downloaded. If someone can point out where I can find it that will be great, maybe I am missing something obvious. Thanks. Kashif... |
|
From: Carsey, J. <jab...@in...> - 2011-10-17 23:32:27
|
That command is not part of the EDK shell. I would suggest THAT YOU MOVE TO THE EDK II version of the shell. -Jaben From: Kashif Memon [mailto:ka...@nv...] Sent: Monday, October 17, 2011 4:10 PM To: efi...@li... Subject: [edk] Loading a driver from EFS Hello, I need to modify the NVRAM variables to load a driver from the EFI system partititon. As far as I understand, this can be done using the bcfg command in Shell. Only problem is I can't find bcfg in the Shell binary/source that I downloaded. If someone can point out where I can find it that will be great, maybe I am missing something obvious. Thanks. Kashif... |
|
From: Kashif M. <ka...@nv...> - 2011-10-17 23:10:16
|
Hello, I need to modify the NVRAM variables to load a driver from the EFI system partititon. As far as I understand, this can be done using the bcfg command in Shell. Only problem is I can't find bcfg in the Shell binary/source that I downloaded. If someone can point out where I can find it that will be great, maybe I am missing something obvious. Thanks. Kashif... |
|
From: Daniel M. <dan...@er...> - 2011-09-06 14:13:24
|
Ok, I found a way to access that memory, which is accesing it directly. The memmory is in this range: 0000000100000000-000000027FFFFFFF
EFI_PHYSICAL_ADDRESS add = 0x0000000100000000;
Status = BS->AllocatePages(AllocateAddress,EfiLoaderData,1500000, &add);
Then my question is, how could I do to get that memmory automatically detected when for example I use AllocatePages with the AllocateAnyPages modifier:
Status = BS->AllocatePages(AllocateAnyPages,EfiLoaderData,3,NULL);
Or when I call the AllocateZeroPool():
Filename = AllocateZeroPool(FilenameSize);
Or even when trying to load a .efi image, although there is memory available in that range, my system does not recognize it and the .efi image is not loaded. How could I mark that memmory as available (possible to allocate in) or how do I tell the system to search for it there?
Thank you very much.
BR
Daniel
________________________________
From: Daniel Moral [mailto:dan...@er...]
Sent: den 6 september 2011 12:41
To: edk...@li...; efi...@li...
Subject: [edk2] Problem when allocating memory
Hi all,
I am having a problem in my board when trying to allocate memmory. After loading the Shell and executing memmap this is the summary:
reserved : 65 Pages (266,240)
LoaderCode: 349 Pages (1,429,504)
LoaderData: 384 Pages (1,572,864)
BS_code : 1,492 Pages (6,111,232)
BS_data : 262,865 Pages (1,076,695,040)
RT_code : 97 Pages (397,312)
RT_data : 43 Pages (176,128)
available : 1,822,931 Pages (7,466,725,376)
ACPI_recl : 8 Pages (32,768)
ACPI_NVS : 630 Pages (2,580,480)
MemMapIO : 69,711 Pages (285,536,256)
Total Memory: 8,159 MB (8,555,720,704) Bytes
I wrote an application which allocates memmory until it is not possible to allocate more, it executes this loop:
while(!(EFI_ERROR(Status))){
cont++;
Status = BS->AllocatePages(AllocateAnyPages,EfiLoaderData,3,NULL);
}
Then, if for example I try to load an application (EFIFMT.EFI) I get the following error messages:
Promote the memory resource
AllocatePoolPages: failed to allocate 44 pages
AllocatePool: failed to allocate 179296 bytes
Promote the memory resource
AllocatePoolPages: failed to allocate 44 pages
AllocatePool: failed to allocate 179296 bytes
CoreOpenImageFile: Device did not support a known load protocol
Promote the memory resource
AllocatePoolPages: failed to allocate 44 pages
AllocatePool: failed to allocate 179296 bytes
'EFIFMT.EFI' is not recognized as an internal or external command, operable program, or batch file
Exit status code: Invalid Parameter
But if I execute memmap again I get this:
reserved : 65 Pages (266,240)
LoaderCode: 349 Pages (1,429,504)
LoaderData: 250,440 Pages (1,025,802,240)
BS_code : 1,492 Pages (6,111,232)
BS_data : 262,865 Pages (1,076,695,040)
RT_code : 97 Pages (397,312)
RT_data : 43 Pages (176,128)
available : 1,572,875 Pages (6,442,496,000)
ACPI_recl : 8 Pages (32,768)
ACPI_NVS : 630 Pages (2,580,480)
MemMapIO : 69,711 Pages (285,536,256)
Total Memory: 8,159 MB (8,555,720,704) Bytes
So if there is that much available memmory why can I only use like 2GB in total? Is there any limitation or any parameter anywhere to limit this? Or do you think it is because of my board?
Thank you very much
BR
Daniel
|
3 messages has been excluded from this view by a project administrator.