ight be able to just link the library and make the
calls).
https://svn.code.sf.net/p/edk2/code/trunk/edk2/EmbeddedPkg/Library/EfiFileLib/EfiFileLib.c
Thanks,
Andrew Fish
> Google shows that many Intel platforms already have a TFTP command in their
> shell, so someone has certainly writte
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
le
reak normal
operation.
There is a spec for this driver:
http://www.intel.com/content/dam/doc/reference-guide/efi-pci-host-bridge-allocation-protocol-specification.pdf
<http://www.intel.com/content/dam/doc/reference-guide/efi-pci-host-bridge-allocation-protocol-specification.pdf>
Thanks,
Andre
om WinPE I have no clue, but that seems
like something to ask on a WinPE forum. You need access to the EFI Variable
Runtime Services.
Thanks,
Andrew Fish
> Thanks in advance,
> Koen Mulderij
> --
> New Year. N
BasePcdLibNull.inf so far.
>
It is likely that adding a real PCD lib, has added a dependency on the PCD
protocol that is produced by this driver:
https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Universal/PCD/Dxe/Pcd.inf
So likely you are missing that driver.
Thanks,
Andrew Fi
/code/trunk/edk2/MdeModulePkg/Bus/Pci/PciBusDxe/
Thanks,
Andrew Fish
> Thank you in advance for any replies and I apologize if this is not
> correct forum for the question or if I have not explained it properly.
> Sincerely,
> Dan Rosendorf
>
>
try point defines “Structure Table Length” for entire SMBIOS
> table with WORD.
This option would work for us, maybe with a PCD option to disable the 32-bit
table if we ever want to deprecate it in the future.
Thanks,
Andrew Fish
> Option 2:
> We introduce a new PCD P
t linking against stdlib because it won't be
> available to EFI applications when they're running? If so, is it not possible
> to statically link them?
>
The EFI version of stdlib is
https://github.com/tianocore/edk2/tree/master/AppPkg
The MdePkg (https://github.com/tianoc
> On Feb 10, 2015, at 5:18 AM, Li, Elvin wrote:
>
> Hi Andrew/Samer,
> So does option 2 could meet your requirement? Option2 is a full set
> which cover option 1. This would provide flexibility to disable 32-bit and
> 64-bit.
>
Yes, it would work.
Thanks,
An
devices that are not PCI (mostly ISA like devices). On a system
like that most of the MMIO space is behind the PCI Root Bridge.
Thus MMIO devices that are not PCI need to be described via ACPI, or via some
other standard (GUID’ed configuration table discovered via the EFI System
Table).
Thanks
in the Conf/tools_def.txt.
Thanks,
Andrew Fish
> - John 'Warthog9' Hawley
>
> On 02/11/2015 02:34 PM, Jack Black wrote:
>> OK, it turned out that the error was because I had just slapped VS
>> 2008 express on the box (since there were no instructions on how to
>> ch
ut what goes into the table, and
when the table gets created. I assume that we want to report OS visible
ranges, so for example memory stolen for SMM would not be in the table.
Thanks,
Andrew Fish
>
> - DW
> -
---
at leaf maps to the
handle. So the EFI_DEVICE_PATH_PROTOCOL is the name (or representation) of the
handle it is associated with.
If you want walk the tree of a handles you need to walk the Handle/Protocol
database. So you use things like gBS->ProtocolsPerHandle() and
gBS->OpenProtocolInformation().
emented.
20. If a driver is written for an ATA controller, then the
EFI_ATA_PASS_THRU_PROTOCOL must be implemented.
Thanks,
Andrew Fish
> Example Real: I've a hdd sata and i want identify with Device_Path.
> but think which i need walk ALLL path from the Root port to the Sata port.
RIVER DXE_RUNTIME_DRIVER DXE_SAL_DRIVER
DXE_SMM_DRIVER UEFI_APPLICATION UEFI_DRIVER
OvmfPkg/Library/PlatformDebugLibIoPort/PlatformDebugLibIoPort.inf:24:
LIBRARY_CLASS = DebugLib
This will show you the set of Library Instances that produce the DebugLib
LibraryClass, and what mo
y this, it will
set the toolchain to XCODE5 and everything should compile.
Update OS Major number checking to future proof it, and default to XCODE5
(clang + lldb).
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Andrew Fish mailto:af...@apple.com>>
git diff OvmfPkg/b
the dependent ACPI table installation as well,
> before we go to the kernel.
>
> One idea could be to signal EFI_EVENT_GROUP_READY_TO_BOOT ourselves,
That sounds like the right thing to do.
> before booting the kernel; however this event group seems quite tied to
> the Boot Manage
(OS X 10.8) or newer". Again maybe use 'newer' in the line about
> Mavericks too?
>
I should also add a comment to make it clear that uname -r numbers are Darwin
(not OS X) versions.
Thanks,
Andrew Fish
> --
> Bruce
>
> On Sun, Feb 15, 2015 at 6:36 PM, Jor
OvmfPkg/build.sh: Use XCODE5 for newer OS X releases
Update OS Major number checking to future proof it, and default to
XCODE5 (clang + lldb).
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Andrew Fish mailto:af...@apple.com>>
Reviewed-by: Bruce Cran mailto:b
n implementation choice, that is influenced by the technology
being enumerated.
> * Should depex's be able to use 'guid' based events?
>
No the depex are based on Protocols. If you want a depe
> On Feb 17, 2015, at 1:27 AM, Laszlo Ersek wrote:
>
> On 02/17/15 00:26, Jordan Justen wrote:
>> On 2015-02-16 13:10:26, Andrew Fish wrote:
>>>
>>>On Feb 16, 2015, at 12:46 PM, Jordan Justen
>>>wrote:
>>>* Does PI need
Pkg/Library/UefiDpLib/UefiDpLib.inf
!endif #$(INCLUDE_DP)
!endif #$(NO_SHELL_PROFILES)
Thanks,
Andrew Fish
> Any recommendation or suggestion about the idea?
>
> Thanks,
> Olivier
> --
> Download BIRT iHub F
o poll that memory location. Please tell me if there is any
> nearby solution.
>
Are you debugging? You may be able to use the X86 debug registers (often called
watchpoints in a debugger).
Thanks,
Andrew Fish
> -Param
---
>
> In this case is there any feature which can notify me about memory change ?
>
No. Best you can do is have a timer event that watches the event and have that
event signal your driver.
Thanks,
Andrew Fish
> -Param
>
>
>
> From: Andrew Fish [mailto:af...@apple
tent is changed I wanted to take UEFI help.
>>
>> In this case is there any feature which can notify me about memory change ?
>>
>> -Param
>>
>>
>>
>> From: Andrew Fish [mailto:af...@apple.com]
>> Sent: Thursday, Februa
mp;BlockIo);
You can also get BlockIo protocols for things like partitions. So you can skip
a partition by testing BlockIo->Media-> LogicalPartition is TRUE.
You can also retrieve the device path (or look for other associated protocols)
on H
> On Feb 24, 2015, at 2:59 PM, Brian J. Johnson wrote:
>
> On 02/23/2015 04:55 PM, James Bottomley wrote:
>> On Wed, 2015-02-18 at 23:32 -0800, Andrew Fish wrote:
>>>> On Feb 18, 2015, at 11:19 PM, Sergey Isakov wrote:
>>>>
>>>> No, memory ch
ou get the raw data from the mouse and the GUI is up to you.
You are probably accustomed to calling a GUI based API that has built a lot of
infrastructure for you to use (windows, cursor, etc.).
Thanks,
Andrew Fish
e that issue.
Thanks,
Andrew Fish
> Best wishes,
>
> 本邮件仅针对指定的收件人发送并可能含有保密或专有内容。任何非指定收件人所为之查阅、转发或使用本信息是不被允许的。
> 如果您误收到本邮件，请立即告知发件人并删除本邮件及所有附件。谢谢！
> The information transmitted in this e-mail is intended only for the addressee
> and may contain confidential and/or privileged
ing OS.
> So OS won’t occupy these pre-allocated IO ranges when a PnP device is plugged
> during OS runtime.
>
> Is ACPI Table the only method to declare these reserved IO ranges?
>
Yes, the PCI root bridge should know what IO and MMIO ranges it decodes and
return them in it’s CRS m
d HOB thing.
>
> Thoughts?
>
The edk2 PEI Core does not conform to the specification?
I’m guessing some private GUID’ed HOBs existed prior to this PI defined one.
The CPU PEIM pass up data to the CPU DXE driver.
Thanks,
Andrew Fish
> Tim
> //
> // If SEC provi
every CPU PEIM to do it.
Thanks,
Andrew Fish
> Thanks
> Liming
> From: Yao, Jiewen [mailto:jiewen@intel.com]
> Sent: Saturday, February 28, 2015 2:34 PM
> To: edk2-devel@lists.sourceforge.net
> Subject: Re: [edk2] SEC PPI HOBs
>
> I think CPU PEIM need consu
ts that you always
want to come out on the serial output.
Thanks,
Andrew Fish
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Laszlo Ersek
>> Reviewed-by: Ard Biesheuvel
>
> Reviewed-by: Leif Lindholm
>
>> ---
>> ArmPkg/Li
ed on libraries that got picked in the DSC
so the calls to the library constructors is auto generated.
Thanks,
Andrew Fish
>
> I was going to bisect, but bbc3758ab5bc0e526994a63d739d445416ff0c07
> also crashes during build, and I don't know if it's supposed to be
> "go
clear on
who should do it.
Thanks,
Andrew Fish
PS It looks like the PI spec wording needs to get cleaned up. I’l take this up
with PIWG.
> Thanks
> Liming
> From: Andrew Fish [mailto:af...@apple.com]
> Sent: Sunday, March 01, 2015 2:47 AM
> To: edk2-devel@lists.sourcefo
re and more of
the error message over time so it is hard to know what is going on for sure.
Thanks,
Andrew Fish
>
> No idea - this looks like something the edk2 devs might be able to help with,
> though.
>
> --
> Bruce
> ---
> On Mar 3, 2015, at 9:54 PM, Gerard Bucas wrote:
>
> Hi David
>
> I am pretty sure I followed those instructions exactly. The only difference
> is that I have a slightly newer version of VS (which I resolved) and a Python
> (still V2.X so should be OK).
>
> I downloaded the svn from that
l from source control for all the open source bits (a branch). Exact
command line (or GUI for Windows) instructions on how to pull the open source
bit. It seems svn is getting to be uses less and less these days….
Thanks,
Andrew Fish
> Thank you,
>
>
> Michael Krau
--
etq
So the point of making it volatile is to force the compiler to read the value
every time the C code asks for the value.
Thanks,
Andrew Fish
> Thanks,
> Chen
>
>
>
> On 03/04/2015 03:56 PM, Fan, Jeff wrote:
>> Chen,
>>
>> Volatile is to tell compiler
> On Mar 5, 2015, at 4:34 PM, James Bottomley
> wrote:
>
> On Wed, 2015-03-04 at 18:30 -0800, Andrew Fish wrote:
>>> On Mar 4, 2015, at 5:34 PM, Chen Fan wrote:
>>>
>>> Hi Jeff,
>>>
>>> Thanks for your explanation, I didn't encou
to a node in a linked list.
@return Entry.
**/
LIST_ENTRY *
EFIAPI
RemoveEntryList (
IN CONST LIST_ENTRY *Entry
);
Thanks,
Andrew Fish
>
> Thanks & regards
> Meenakshi Aggarwal
>
>
ug Message Print Level.
# @Expression 0x8002 | (gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel
& 0x7F84AA00) == 0
gEfiMdePkgTokenSpaceGuid.PcdDebugPrintErrorLevel|0x8000|UINT32|0x0006
Thanks,
Andrew Fish
00 60 | ..`|
01b0 2e 64 61 74 61 00 00 00 c0 01 00 00 80 3f 00 00 |.data?..|
01c0 c0 01 00 00 80 3f 00 00 00 00 00 00 00 00 00 00 |.?..|
01d0 00 00 00 00 60 00 00 e0 2e 72 65 6c 6f 63 00 00
sure what that would prove? The path, other than reading in the binary
would be identical is LoadImage()/StartImage()?
> I have tried the efi binary shell package and I can successfully run the
> problem binary application from there fine.
>
> Any suggestions would be very h
rting ELF files to
PE/COFF?
Thanks,
Andrew Fish
https://svn.code.sf.net/p/edk2/code/trunk/edk2/BaseTools/Conf/build_rule.template
[Hii-Binary-Package.UEFI_HII]
*.hpk
$(OUTPUT_DIR)(+)$(MODULE_NAME)hii.lib
$(OUTPUT_DIR)(+)$(MODULE_NAME)hii.rc
> On Mar 31, 2015, at 8:08 AM, Andrew Fish wrote:
>
>
>> On Mar 31, 2015, at 3:49 AM, Gao, Liming > <mailto:liming@intel.com>> wrote:
>>
>> Bruce:
>> VS tool chain will generate HII package list as the resource section into
>> the fin
moving it to live SCM on tianocore so
> that it can be evolved with the community.
Vincent,
Was it developed on a private SCM? Anyway to capture that history?
Thanks,
Andrew Fish
> Wiki at
> https://github.com/tianocore/tianocore.github.io/wiki/Coreboot_UEFI_payload,
>
ne used the same system. So the ZIP file was Least Common Denominator.
Thanks,
Andrew Fish--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot M
lue?
Thanks,
Andrew Fish
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, f
has a larger value and it runs last? So
maybe it is a race, or we are just getting lucky? Or maybe there is some
syncing back from EFI_BOOT_SCRIPT_TABLE_HEADER that I missed in the code.
Thanks,
Andrew Fish
PS I’ve not seen any bad S3 data. I’m writing a debugger script to dump out the
tabl
> On Mar 31, 2015, at 6:54 PM, Andrew Fish wrote:
>
>>
>> On Mar 31, 2015, at 6:25 PM, Yao, Jiewen > <mailto:jiewen@intel.com>> wrote:
>>
>> Yes. It seems a bug.
>> We should initialize it.
>
> Thanks!
>
> The other th
y call
the Library in SMM from locking events?
Thanks,
Andrew Fish
> Thanks,
> Star
--
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashd
rior to the event every one is using the same
pointer. After lockdown the SMM get a new one. I confirmed that pattern with
the debugger.
Thanks,
Andrew Fish
> And you may see the below code logic in S3BootScriptGetEntryAddAddress(),
> that is to say only SMM driver is allowed to write boo
he strings are just convention to make things human readable. So
hexdump the device paths to see the difference.
Thanks,
Andrew Fish
> Any suggestions on how I can debug this ?
> Thanx,
>
>
> --
> Di
040: 00 00 00 00 70 79 69 FF-03 00 00 00 98 2C 97 FF
> *pyi..,..*
> 0050: 03 01 00 00 34 46 67 FF
MAC_ADDR_DEVICE_PATH.EFI_MAC_ADDRESS
> -01
MAC_ADDR_DEVICE_PATH.IfType
MAC_ADDR_DEVICE_PATH
> 7F FF 04 00
END Device Path
> 00 00 *4Fg.
reaks ties when it comes to dispatch order), but it sounds like this is a tool
for debugging so no big deal.
Thanks,
Andrew Fish
> From: Olivier Martin [mailto:olivier.mar...@arm.com
> <mailto:olivier.mar...@arm.com>]
> Sent: Tuesday, April 07, 2015 11:18 AM
> To: edk2-deve
ing is not active for
IA-32 (MTRR) and IPF (bit 63 Physical address set means non cacheable). X64
requires paging to operate, and ARM requires page tables for cacheability
controls.
So reverse engineering the state of OS loaders on a CPU that requires paging be
enabled is not going to l
timeImage->ImageSize,
RuntimeImage->RelocationData
);
InvalidateInstructionCacheRange (RuntimeImage->ImageBase, (UINTN)
RuntimeImage->ImageSize);
}
}
Thanks,
Andrew Fish
> Thanks
> Elvin Li
>
> -Original Message-
> From: Andrew Fish [mailto:af...@apple.com]
> On Apr 9, 2015, at 1:21 AM, Vladimir Onipchuk wrote:
>
> Hi All,
>
> I have problems with my PCI device driver.
>
> Driver works great,
What does that mean?
> but after loading and installing it from Option Rom, I can't get access to
> (can't read) my Memory chips, mapped to the Memory s
would also point out on a 32-bit system
this is a much bigger deal (lack of virtual address space).
So I think the only thing to do is call the REPORT_STATUS_CODE() on entry,
before any changes are made to the system.
Thanks,
Andrew Fish
> Thanks
> Elvin
>
> -Original
hat library. and
> build the application which consumes the library.
ParthaS,
I can’t think of a good way to do this. But it is possible to use a
[BuildOptions] section in your driver INF file to pass compiler or linker
flags.
[BuildOptions]
GCC:*_*_*_DLINK_FLAGS = -L -l
Thanks,
And
hould match to environments the code can execute in, not the
data it collects. Otherwise every driver that consumed a HOB would need PEI in
its name.
Thanks,
Andrew Fish
> Thanks,
> Star
> From: Anbazhagan, Baraneedharan [mailto:anbazha...@hp.com]
> Sent: Thursday, April 16, 2015
allocated for the PE/COFF
image.
A Shell app is just an EFI Application that depends on protocols produced by
the Shell.
Thanks,
Andrew Fish
> Thanks!
> __e
>
> --
> BPM Camp - Free Virtual Workshop May
by
the shell looking at the device path on the handle that has the File System
protocol.
Thanks,
Andrew Fish
> Peace!
> __e
>
> From: Andrew Fish [mailto:af...@apple.com]
> Sent: Wednesday, April 15, 2015 8:05 PM
> To: edk2-devel@lists.sourceforge.net
> Subject: Re: [ed
/edk2/MdeModulePkg/Universal/Console/GraphicsConsoleDxe/GraphicsConsole.c
The EDK had a concept of graphics vs. text mode (both on the graphics screen)
but that does not exist in the edk2.
Thanks,
Andrew Fish
> __e
> <>
> From: Andrew Fish [mailto:af...@apple.com]
> Se
; X64
You only need the TimerLib for early boot code (PI Code, that is usually
configuring the chipset/SoC). If you are writing UEFI code (option ROM,
application) you call gBS->Stall() to get a delay that is abstracted from the
platform implementation.
Thanks,
Andrew Fish
MdePkg/Library/SecPeiDxeTimerLibCpu/SecPeiDxeTimerLibCpu.inf
>
If you are writing an UEFI driver you should NOT use the TimerLib and use
gBS->Stall().
>
> I removed the gBs->Stall() of the code and the message yet is showed .
>
I don’t know what you are talking about? Did you remove the Time
o copy all
the error messages into the emails if you want help.
Thanks,
Andrew Fish--
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Proces
t;> without SHELL Spec ?
>>
>>
>> I thought in to use any function of the DEVICE_PATH_PROTOCOL, but doesn't
>> worked!
>>
>>
>> Can you help me?
>>
The question is why you your non Shell application needs to use the Shell
specific names? Th
protocol you transfer control to another driver
that you are not linked against and you only return to your code when that
driver returns.
Thanks,
Andrew Fish
> I going to try do a better explanation:
>
> #the file: myApp.efi
>
> #1 When run myApp.efi in shell, is showed the m
hruDxe.efi in a location
relative to that information.
Thanks,
Andrew Fish
>
> Att.
> Vieira.
>
>
> The question is why you your non Shell application needs to use the Shell
> pecific names? The Volume names,
> which Simple Filesystem Protocol instance to use, are shell spe
VOID *Node
)
{
ASSERT (Node != NULL);
if (DevicePathNodeLength (Node) < sizeof (EFI_DEVICE_PATH_PROTOCOL)) {
return TRUE;
}
return (BOOLEAN) (IsDevicePathEndType (Node) && DevicePathSubType(Node) ==
END_ENTIRE_DEVICE_PATH_SUBTYPE);
}
Thanks,
OS loader, or EFI tool could pass a malformed device path.
Also defening against malformed data is good security practice.
Thanks,
Andrew Fish
PS My crash was a hang in the DXE Core as I was trying to install a device path
protocol that had not been initialized.
>
> -Jaben
>
turn TRUE;
}
return (BOOLEAN) (IsDevicePathEndType (Node) && DevicePathSubType(Node) ==
END_ENTIRE_DEVICE_PATH_SUBTYPE);
}
Thanks,
Andrew Fish
>
> -Original Message-
> From: Andrew Fish [mailto:af...@apple.com]
> Sent: Wednesday, April 22, 2015 5:49 PM
> To: ed
gt; &MyContext,
> &gEfiEventReadyToBootGuid,
> &MyBootEvent
> );
>
> Please help me if there is an alternative method to get the PCI slot
> number or if there is something wrong in the above method.
> Thanks in advance.
ls to do work. You can
use gBS->LocateHandleBuffer() to get an array of Handles that support a given
protocol.
Thanks,
Andrew Fish
> Thanks.
>
>
> --
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM
; uses TSC (Time Stamp Counter) through the instruction "RDTSC". On the
> other side, the "SecPeiDxeTimerLibCpu" uses the "Local APIC timer"
> reading a bit field of an MSR through the instruction "RDMSR".
>
> What's the real impact when using MSR inst
ATUS
EFIAPI
EfiTestChildHandle (
IN CONST EFI_HANDLE ControllerHandle,
IN CONST EFI_HANDLE ChildHandle,
IN CONST EFI_GUID *ProtocolGuid
);
Thanks,
Andrew Fish
>
> --
> BPM Camp - Free
standard drivers work, and you have not intent of getting
the open source driver changed you should just copy the driver into your own
package and modify it.
Thanks,
Andrew Fish
> Thanx,
>
> Narinder Dhillon
>
>
y mapped. The initial FVB implementations are read only and are
used to construct all the Firmware Volumes (another PI concept), and a driver
that understands the FLASH device is added later in the boot.
Thanks,
Andrew Fish
> UEFI spec update will only impact #1.
> And when we have new
the right way to fix the
variable driver…. Thanks!
The PCD could be a device path, or a feature flag to look for an FVB protocol
with a well know protocol on the handle (MdeModulePkg protocol with NUL data).
It should be possible to discover based on address or PCD device path (or
protocol)
ableModuleGlobal);
EfiConvertPointer (0x0, (VOID **) &mNvVariableCache);
EfiConvertPointer (0x0, (VOID **) &mHandlerTable);
for (Index = 0; Index < mNumberOfHandler; Index++) {
EfiConvertPointer (0x0, (VOID **) &mHandlerTable[Index]);
}
Status = EfiConvertList (0x0, &mLo
ache the store), and matching of FVB is
done via an address.
Thus if an FVB only supports a block device that can NOT be memory mapped, it
will not be discovered by the variable driver, and there is no way to cache the
variable store as that 1st read is memory based.
Thanks,
Andrew Fish
> On Apr 23, 2015, at 7:50 PM, Andrew Fish wrote:
>
>
>> On Apr 23, 2015, at 7:44 PM, Yao, Jiewen > <mailto:jiewen@intel.com>> wrote:
>>
>> Hi Andrew or Haojiang
>> Would you please share more your insight below:
>> “It should be possi
waist memory for the OS?
Thanks,
Andrew Fish
--
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports
, 0x100 },
{ EfiLoaderCode, 0x100 },
{ EfiLoaderData, 0x100 },
{ EfiBootServicesCode,0x800 },
{ EfiBootServicesData,0x2500},
{ EfiConventionalMemory, 0 },
{ EfiUnusableMemory, 0 },
{ EfiMaxMemoryType, 0 }
};
Than
cribed as a binary buffer that must be parsed from
> beginning to end.
>
> I recommend we do not add this C data structure to UefiSpec.h.
>
I agree as most of the this C struct is just a comment, that follows the spec.
Given it only has two elements it is not going to be that usef
es and libraries instances."
#string STR_PACKAGE_DESCRIPTION #language en-US "It also provides the
definitions(including PPIs/PROTOCOLs/GUIDs) of EFI1.10/UEFI2.4/PI1.3 and some
Industry Standards."
From searching the web it would seem if the above does not work it is a
a diff to be produced, but I
> don't believe it would actually work to apply a patch to a UTF-16
> file.
>
This
http://stackoverflow.com/questions/777949/can-i-make-git-recognize-a-utf-16-file-as-text
<http://stackoverflow.com/questions/777949/can-i-make-git-recognize-a-utf-16-file-as-text&
d it
> did not require a huge amount of effort.
>
Only issue is a rev change to all the *.uni files. I’m just a little allergic
to touching a lot of files, so that is why I pointed out another way to solve
the problem.
If the .gitattributes does not solve the problems people are having I gues
all the values come from this PEIM
https://svn.code.sf.net/p/edk2/code/trunk/edk2/MdeModulePkg/Universal/PCD/Pei/
and all the other modules will use the PCD PPI to get/set PCD values. The PCD
macro in the PEIM ends up calling a library call that abstracts the PCD PPI
call.
Thanks,
Andrew Fish
> Than
got set to, and a
per driver view. It will also show the set of specific libraries linked into a
module.
Thanks,
Andrew Fish
> Anyway, it seems like I've done the proper declaration (.DSC file wise)
> Thanks again for the feedback.
--
amp;MemoryData
);
if (!EFI_ERROR (Status) && ValidateMemoryTypeInfoVariable(MemoryData,
DataSize)) {
//
// Build the GUID'd HOB for DXE
//
BuildGuidDataHob (
&gEfiMemoryTypeInformationGuid,
MemoryData,
DataSize
Ard,
Would removing the Reserved field and making Size a UINT64 also fix the issue?
Contributed-under: TianoCore Contribution Agreement 1.0
Reviewed-by: Andrew Fish
Thanks,
Andrew Fish
> On May 9, 2015, at 1:15 PM, Ard Biesheuvel wrote:
>
> According to the UEFIv2.5 spec section
> On May 9, 2015, at 1:43 PM, Ard Biesheuvel wrote:
>
> On 9 May 2015 at 22:39, Andrew Fish <mailto:af...@apple.com>> wrote:
>> Ard,
>>
>> Would removing the Reserved field and making Size a UINT64 also fix the
>> issue?
>>
>
> Yes, b
; - UINT32 Reserved;
>> EFI_MEMORY_TYPE Type;
>> UINTN Size;
>> + UINTN Reserved;
>> CHAR8 Data[1];
>> } POOL_HEAD;
>
> So the issue is if sizeof(EFI_MEMORY_TYPE) == 4 on a 64-bit machine and the
> compiler doesn't 64-bit
t looks to match PCI device type, in driver binding
supported. And if supported passes, then the Start() will get called.
Thanks,
Andrew Fish
>
>> Let me know if you're interested in taking this on.
>
> Puh, I'm pretty now to UEFI and have to understand the internals a
> On May 11, 2015, at 2:19 AM, Laszlo Ersek wrote:
>
> Andreas,
>
> On 05/11/15 02:09, Andrew Fish wrote:
>>
>>> On May 10, 2015, at 4:20 PM, Andreas Galauner wrote:
>>>
>>> On 10.05.2015 15:32, Cohen, Eugene wrote:
>>>> I apolo
. I add -fcolor-diagnostics to the compiler lines as this enabled
color diagnostic (error messages) from clang when building under the edk2.
Thanks,
Andrew Fish
> Thanks
> Liming
> From: Chan, Amy
> Sent: Friday, May 8, 2015 4:48 PM
> To: edk2-devel@lists.sourceforge.net <mailto:
ult location is /Applications/Xcode.app/Contents/Developer/, but you
can install multiple copies of the tools and switch via the command line.
Thanks,
Andrew Fish
> -Jordan
>
> On 2015-05-11 18:33:59, Gao, Liming wrote:
>> Andrew:
>>
>> I convert this patch to g
301 - 400 of 1217 matches
Mail list logo
