I fixed the problem ! It was very easy. You can't use yasm with VS2010. Use
vsyasm instead. You can download the zip file here :download the
http://www.tortall.net/projects/yasm/releases/vsyasm-1.0.0-win64.zip
After that it's very straightforward !
Add this to build_rules.txt :
[Yasm-Assembly-Cod
Hi,
I'm trying to get up and running with EDK II on Haiku (an unsupported
platform), but the GenFw tool is failing at the final steps of the
build with the error:
GenFw: ERROR 3000: Invalid
/Data/edk2//DEBUG_GCC48/X64/MdeModulePkg/Application/HelloWorld/HelloWorld/DEBUG/HelloWorld.dll
unsu
Error I am getting:
"C:\Program Files (x86)\Microsoft Visual Studio
10.0\Vc\bin\x86_amd64\cl.exe" /nologo /E /TC /FIAutoGen.h
/Ic:\edk2\myworkspace\MdeModulePkg\Application\Dumdum
/Ic:\edk2\myworkspace\Build\DuetPkgX64\RELEASE_VS2010x86\X64\MdeModulePkg\Application\Dumdum\Dumdum\DEBUG
This is what's in my build_rule.txt:
[Nasm-Assembly-Code-File.COMMON.COMMON] ?.nasm, ?.Nasm,
?.NASM
$(MAKE_FILE)
$(OUTPUT_DIR)(+)${s_dir}(+)${s_base}.obj
"$(PP)" $(PP_FLAGS) $(INC) ${src} >
${d_path}(+)${s_base}.i Trim --trim-long --source-cod
Andrew Fish pointed out
:http://news.gmane.org/gmane.comp.bios.tianocore.buildtools.devel/cutoff=15
Unfortunately it doesn't work. The guy who asked the original question
actuallyworked in my group. I'm supporting his code (which doesn't work). Any
helpwould be appreciated.
Thanks,
Shubha
Shub
I followed the examples for NASM and things just don't work. Can someone fix
this and post an update ?I realize that by default EDK2 only supports NASM and
MASM. But though I've followed previous posts onthis topic I'm getting massive
errors.
Please help !
Shubha
Shubha D. ramanishubharam...@g
Answered my own quesiton. Yes, you just put the *.c and *.h under [Sources] in
the inf file. Shubha D. ramanishubharam...@gmail.com
shubharam...@yahoo.com
On Friday, September 4, 2015 12:45 PM, Shubha Ramani
wrote:
For instance, I want to just make *.o (object) files from a *.c not
> On Sep 4, 2015, at 2:11 PM, Tim Lewis wrote:
>
> Other than setting BootNext?
>
Or the other bits of UEFI Chapter 3 Boot Manager.
Thanks,
Andrew Fish
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Hamel,
> Lee M
> Sent: Friday, Septe
Other than setting BootNext?
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of Hamel,
Lee M
Sent: Friday, September 04, 2015 2:08 PM
To: edk2-devel@lists.01.org
Subject: [edk2] BDS automatically boot \
Is it possible to tell BDS, without writing a
Is it possible to tell BDS, without writing a custom BDS driver, to
automatically boot a file on a device? I am aware of \efi\boot\bootx64.efi.
I am wondering if I can make BDS boot an arbitrary file on an arbitrary device
without creating a custom BDS driver.
___
For instance, I want to just make *.o (object) files from a *.c not necessarily
make a UEFI *.lib. I wishto link to those object files from my UEFI_APPLICATION.
Shubha Shubha D. ramanishubharam...@gmail.com
shubharam...@yahoo.com
___
edk2-devel mailing l
On 09/04/15 05:56, Shubha Ramani wrote:
> Using this link I was able to get qemu installed on my Ubuntu virtual
> machine. UEFI/OVMF - Ubuntu Wiki
>
> | |
> | | | | | |
> | UEFI/OVMF - Ubuntu WikiOVMF is a port of Intel's tianocore firmware to the
> qemu virtual machine. This allows
The specification of the EFI_EXT_SCSI_PASS_THRU_PROTOCOL.PassThru()
function documents the EFI_BAD_BUFFER_SIZE return status, and the
EFI_EXT_SCSI_STATUS_HOST_ADAPTER_DATA_OVERRUN_UNDERRUN host adapter
status.
These allow an EFI_EXT_SCSI_PASS_THRU_PROTOCOL implementation to request
higher layers i
On 09/04/15 02:24, Larry Cleeton wrote:
> Your efforts have confirmed that it is the initial boot loader that
> is failing (bootia32.efi, aka Windows Boot Manager, aka bootmgr).
>
> The stack implies that bootmgr is failing to create the ramdisk that
> is specified in the BCD as the default boot e
On Fri, Sep 04, 2015 at 01:21:57AM +0200, Laszlo Ersek wrote:
> On 09/03/15 23:25, j...@joshtriplett.org wrote:
> > On Thu, Sep 03, 2015 at 07:19:40PM +0200, Laszlo Ersek wrote:
>
> >> In any case, if what you need resembles a "general virtio filesystem",
> >> then please just use that -- a virtio
> On Sep 4, 2015, at 7:01 AM, Shubha Ramani wrote:
>
> So you're saying that an efi app being compiled as a lib is a normal stage of
> the efi compilation process. Right ? All efi apps are libs at some point.
>
The library is just a collection of object files that map to each of the .c
file
So you're saying that an efi app being compiled as a lib is a normal stage of
the efi compilation process. Right ? All efi apps are libs at some point.
Sent from Shubha Ramani's iPhone 6 Plus
> On Sep 4, 2015, at 6:55 AM, Andrew Fish wrote:
>
>
>> On Sep 4, 2015, at 6:49 AM, Shubha Ramani w
> On Sep 4, 2015, at 6:49 AM, Shubha Ramani wrote:
>
> I have no idea why this is happening. I'm using Visual Studio 2010. Is there
> an obvious reason for why this may be happening ?
The App is linked together like a lib (set of objects) when it is compiled. The
find link is done on a list o
I have no idea why this is happening. I'm using Visual Studio 2010. Is there an
obvious reason for why this may be happening ?
Thanks,
Shubha Shubha D. ramanishubharam...@gmail.com
shubharam...@yahoo.com
___
edk2-devel mailing list
edk2-devel@lists.01.or
On 4 September 2015 at 11:48, Leif Lindholm wrote:
> On Fri, Sep 04, 2015 at 10:19:20AM +0200, Ard Biesheuvel wrote:
>> Commit r18308 ("ArmPlatformPkg/LcdGraphicsOutputDxe: check PrimeCell ID
>> before initializing") introduced a LcdIdentify() function to the PL111
>> LCD driver that makes it fail
These are no longer used by any platform in the tree, nor are they
of any significance to any out of tree platforms.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmVExpressPkg/Library/ArmVExpressLibRTSM/ArmVExpressFoundationLib.inf
On Fri, Sep 04, 2015 at 10:19:20AM +0200, Ard Biesheuvel wrote:
> Commit r18308 ("ArmPlatformPkg/LcdGraphicsOutputDxe: check PrimeCell ID
> before initializing") introduced a LcdIdentify() function to the PL111
> LCD driver that makes it fail gracefully when executed on hardware that
> does not hav
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmVExpressPkg/Library/ArmVExpr
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmVExpressPkg/Library/ArmVExp
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmJunoPkg/Library/ArmJunoLib/A
Replace open coded references to ARM_MP_CORE_INFO_PPI_GUID with
declarations under [Ppis] in the respective .INFs
v2:
- include 3 more instances
Ard Biesheuvel (5):
ArmPlatformPkg/ArmPlatformLibNull: use declared PPI rather than module
local var
ArmPlatformPkg/ArmJunoLib: use declared PPI
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmVExpressPkg/Library/ArmVExp
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/Library/ArmPlatformLibNull/ArmP
On Fri, Sep 04, 2015 at 03:56:11AM +, Shubha Ramani wrote:
> Using this link I was able to get qemu installed on my Ubuntu virtual
> machine. UEFI/OVMF - Ubuntu Wiki
>
> | |
> | | | | | |
> | UEFI/OVMF - Ubuntu WikiOVMF is a port of Intel's tianocore firmware to the
> qemu virtua
Commit r18308 ("ArmPlatformPkg/LcdGraphicsOutputDxe: check PrimeCell ID
before initializing") introduced a LcdIdentify() function to the PL111
LCD driver that makes it fail gracefully when executed on hardware that
does not have the IP. However, the LcdGraphicsOutputDxe driver is shared
with the Hd
On 4 September 2015 at 10:02, Ard Biesheuvel wrote:
> Replace open coded references to ARM_MP_CORE_INFO_PPI_GUID with
> declarations under [Ppis] in the respective .INFs
>
Hmm, right after sending these out, I noticed that there are 3 more
copies of this, so I will follow up with a v2 covering al
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/Library/ArmPlatformLibNull/ArmP
Replace open coded references to ARM_MP_CORE_INFO_PPI_GUID with
declarations under [Ppis] in the respective .INFs
Ard Biesheuvel (2):
ArmPlatformPkg/ArmPlatformLibNull: use declared PPI rather than module
local var
ArmPlatformPkg/ArmJunoLib: use declared PPI rather than module local
va
We can refer to gArmMpCoreInfoPpiGuid directly if we declare it under
[Ppis] in the library's .inf so there is no need to copy it into a
module local variable.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ard Biesheuvel
---
ArmPlatformPkg/ArmJunoPkg/Library/ArmJunoLib/A
34 matches
Mail list logo
