Thanks for information.
The fix has been checked in at edk2 15318.
Regards
Elvin
-Original Message-
From: Mike Maslenkin [mailto:miha...@parallels.com]
Sent: Tuesday, March 04, 2014 7:23 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] [PATCH 1/1] Fix amount of memory value s
Hi All,
I have problems with the my PCI OpRom device driver on some platforms.Driver executing successfully on the old DG41TX motherboard, but on the DH67BL and on the some new HP motherboards driver does not loading from OpRom on the PCIe card (probably, even entrypoint does not executing).Boot p
Hi All,
I have problems with the my PCI OpRom device driver on some platforms.
Driver executing successfully on the old DG41TX motherboard, but on the DH67BL
and on the some new HP motherboards driver does not loading from OpRom on the
PCIe card (probably, even entrypoint does not executing).
B
On 03/05/2014 02:12 AM, ritul guru (riguru) wrote:
> Hi,
>
> Is there any efi utility for CPU stress test, like mprime, prime95
> (which are windows utility)?
I'm not 100% positive, but I believe that Passmark's version of
memtest86 includes such a test:
http://www.memtest86.com/download.htm
--
if you are trying to locate a specific protocol from your driver, it might
not installed during boot process so it doesn't work, but when you execute
it from shell the consumed protocol might already been loaded by some other
driver so it works.
please check the protocol you are trying to locate
Sorry, CPU stress test? What is your purpose, to burn out your CPU?
At boot stage CPU works on one core and on maximum speed not regarding what
process is performed. It will not heated more or less.
CPU will heated at the same rate no matter what application is started.
On 05.03.2014, at 11:12, r
On Mar 5, 2014, at 4:58 AM, Sergey Isakov wrote:
> Sorry, CPU stress test? What is your purpose, to burn out your CPU?
> At boot stage CPU works on one core and on maximum speed not regarding what
> process is performed. It will not heated more or less.
> CPU will heated at the same rate no mat
On Tue, 2014-03-04 at 15:19 +0100, Laszlo Ersek wrote:
>
> > What happens if you use the csm build?
>
> Last time I tested: there was no love lost between CSM and S3,
> independently of video card / driver :) The resume boot path decayed
> to a reboot. I saw the log and ran screaming.
Pfft. That
And where can I see hardware realization? It is just an infinite loop? Or
MWAIT? Or drop to C6 state?
Or this abstract for OEM decided what to do?
On 05 марта 2014 г., at 19:38, Andrew Fish wrote:
>
> On Mar 5, 2014, at 4:58 AM, Sergey Isakov wrote:
>
>> Sorry, CPU stress test? What is your
On Mar 5, 2014, at 8:49 AM, Sergey Isakov wrote:
> And where can I see hardware realization? It is just an infinite loop? Or
> MWAIT? Or drop to C6 state?
> Or this abstract for OEM decided what to do?
>
Usually the CpuDxe PI driver does this. Putting the CPU to sleep (hlt) is a
huge win in
Thanks, I understand
—
VOID
EFIAPI
CpuSleep (
VOID
)
{
_asm {
hlt
}
}
---
On 05 марта 2014 г., at 21:02, Andrew Fish wrote:
>
> On Mar 5, 2014, at 8:49 AM, Sergey Isakov wrote:
>
>> And where can I see hardware realization? It is just an infinite loop? Or
>> MWAIT? Or drop to C6
Hello
I'm building the Ovmf code as part of the edk2. The website mentions
OvmfVideo.rom in the install procedure for working with Qemu. Where do I
get this file? My build made a Ovmf.fv so I think its working for me.
On a related note. How do I search all the edk2 mailing lists? Clicking on
ea
On 03/05/14 18:30, John Davis wrote:
> Hello
>
> I'm building the Ovmf code as part of the edk2. The website mentions
> OvmfVideo.rom in the install procedure for working with Qemu. Where do
> I get this file? My build made a Ovmf.fv so I think its working for me.
Please search the README for t
On 03/05/14 17:22, David Woodhouse wrote:
> On Tue, 2014-03-04 at 15:19 +0100, Laszlo Ersek wrote:
>>
>>> What happens if you use the csm build?
>>
>> Last time I tested: there was no love lost between CSM and S3,
>> independently of video card / driver :) The resume boot path decayed
>> to a reboo
Hello Laszlo,
Many thanks. The readme says the video is no longer being built. I simply
ignored it and did the rest of the procedure on
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=How_to_run_OVMF#Run_QEMU_using_OVMF
and I could get a UEFI shell.
Oddly, the ls/dir command doe
Another problem could be that you not correctly report Device ID in efirom
utility. Some UEFI BIOS implementation don't care about Device ID, reported
in a OptionalRom image, but some does. You should check what you report
when execute efirom.
Igor Sharovar
On Wed, Mar 5, 2014 at 5:54 AM, Neeraj
Hi Everyone
I'm currently doing my MSc in Computer Science and my idea is to do this
task as my final work:
http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=Tasks/UefiCpuPkg/CpuDxe_MP_support
I still have some time (two years) to finish the course, but I'l already
talking with a t
I beg your pardon - I just realized that assert existed:
ConvertPages: failed to find range
AllocatePages fail - Not Found!
I forgot to substract base address from a system memory size:
BuildResourceDescriptorHob (
EFI_RESOURCE_SYSTEM_MEMORY,
EFI_RESOURCE_ATTRIBUTE_PRESENT |
EFI_RES
GraphicsConsoleDxe (a UEFI_DRIVER under MdeModulePkg/Universal/Console)
determines the preferred video resolution from the dynamic PCDs
- gEfiMdeModulePkgTokenSpaceGuid.PcdVideoHorizontalResolution
- gEfiMdeModulePkgTokenSpaceGuid.PcdVideoVerticalResolution
In one of the next patches, we'd like to
If Start() succeeds, the callback is only executed when the setup is
complete (on the stack of RestoreTPL()), rather than on the stack of
InstallMultipleProtocolInterfaces(), when the driver setup may yet be
theoretically incomplete.
If Start() fails, the protocol interface will have been uninstal
I've addressed Jordan's v2 remarks (also noted separately per patch):
- the platform driver is now introduced as an empty driver first,
- replaced the string "PlatformConfig" with "Platform" in many
filenames,
- folded PlatformConfigLib into PlatformDxe,
- bi-directional compatibility in the conf
This DXE driver will load/save persistent values for OVMF's config knobs,
plus expose those knobs via HII.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
---
Notes:
- introduce driver emptily as first step, so that we can later add HII vs.
config (d
The RouteConfig() function is also called now as expected.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
---
OvmfPkg/PlatformDxe/Platform.h| 3 +++
OvmfPkg/PlatformDxe/PlatformForms.vfr | 13 +
OvmfPkg/PlatformDxe/Platform.c|
Establish the full stack of conversions when modifying the platform
configuration:
ConfigResp-- form engine / HII communication
|
[ConfigToBlock]
|
v
MAIN_FORM_STATE -- binary representation of form/widget state
|
This GUID should become a new "namespace" for UEFI variables that are
specific to OVMF configuration (as opposed to standard UEFI global
variables). We'll also use it as the GUID of the related HII form-set (ie.
the interactive user interface).
Contributed-under: TianoCore Contribution Agreement 1
We'll need a C language (ie. structure) representation for the state of
the visual elements on the form. We choose the Buffer Storage kind (see
29.2.5.6 "Storage" in UEFI 2.4A), because it's easy to work with.
Note that the structure added in this patch has nothing to do with UEFI
non-volatile var
The two functions introduced here allow the saving and loading of platform
configuration to/from the non-volatile variable store.
The PLATFORM_CONFIG structure and the two functions that take it / return
it are generally meant for any DXE or UEFI driver that needs to access
platform configuration.
The GraphicsConsoleDxe driver (in MdeModulePkg/Universal/Console)
determines the preferred video resolution from the dynamic PCDs
- gEfiMdeModulePkgTokenSpaceGuid.PcdVideoHorizontalResolution
- gEfiMdeModulePkgTokenSpaceGuid.PcdVideoVerticalResolution
Setting the graphics resolution during boot is
Generate the options for the drop-down list from the GOP resolutions.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
---
Notes:
- replace GOP Depex with GOP installation callback
OvmfPkg/PlatformDxe/Platform.inf | 2 +
OvmfPkg/PlatformDxe/Platform.c
Establish the full stack of conversions in retrieving the platform
configuration:
MultiConfigAltResp -- form engine / HII communication
^
|
[BlockToConfig]
|
MAIN_FORM_STATE -- binary representation of form/widget state
^
In this patch we populate the form with the two widgets related to video
resolution:
- A read-only string field displaying the preference for the next boot.
- A drop-down list offering choices for changing the setting. This list is
implemented with dynamically generated IFR opcodes.
(In general,
... which opens from the Device Manager window.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek
---
Notes:
- make dependency on HiiDatabaseDxe explicit
OvmfPkg/PlatformDxe/Platform.inf | 9 ++
OvmfPkg/PlatformDxe/Platform.h| 24 +
Ovm
You may recall that I mentioned that due to a mishap with some UEFI OS loader
code I was developing, I managed to brick my UEFI-based tablet by setting an
improperly formatted boot path variable as the default boot path.
Unfortunately unplugging the internal SSD drive didn't have any effect, and
A driver is able to do this, but whether your driver gets loaded and run is a
platform policy decision and may be different for your tablet.
If you go ahead with it, you may borrow some code from the shell's BCFG command
for BOOT variable manipulation.
-Jaben
-Original Message-
Fro
Of all the gin joints in all the towns in all the world, Carsey, Jaben had to
walk into mine at 17:26:07 on Wednesday 05 March 2014 and say:
> A driver is able to do this, but whether your driver gets loaded and run is
> a platform policy decision and may be different for your tablet.
Can you el
On Mar 5, 2014, at 5:53 PM, Bill Paul wrote:
> Of all the gin joints in all the towns in all the world, Carsey, Jaben had to
> walk into mine at 17:26:07 on Wednesday 05 March 2014 and say:
>
>> A driver is able to do this, but whether your driver gets loaded and run is
>> a platform policy de
36 matches
Mail list logo
