Hi David,
> -Original Message-
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of David
> Woodhouse
> Sent: Friday, June 21, 2019 6:34 AM
> To: devel@edk2.groups.io; ler...@redhat.com; Lu, XiaoyuX
>
> Cc: Wang, Jian J ; Ye, Ting ;
> Richard Levitte
> Subject: Re: [e
On Fri, Jun 21, 2019 at 01:58:17AM +, Fan, ZhijuX wrote:
> BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1855
>
> GenBiosId is a tool to generate the BIOS ID binary file which uses
> the data from the configuration file.
> This tool can be run in both Py2 and Py3.
>
> This patch is going
On Fri, Jun 21, 2019 at 01:58:57AM +, Fan, ZhijuX wrote:
> BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1855
>
> UniTool is one python script to generate UQI (Universal Question
> Identifier) unicode string for HII question PROMPT string. UQI
> string can be used to identify each HII ques
Pushed at 90e8f13d51278791e9534fc736a5319f9b4f9f0a
Regards,
Jian
> -Original Message-
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Wang,
> Jian J
> Sent: Thursday, June 20, 2019 8:35 AM
> To: Lu, XiaoyuX ; devel@edk2.groups.io
> Subject: Re: [edk2-devel] [PATCH
Pushed at b86fbe1f980102eee3e55eed92ac91937aee638e
Regards,
Jian
> -Original Message-
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Xiaoyu Lu
> Sent: Thursday, June 20, 2019 1:55 PM
> To: devel@edk2.groups.io; Laszlo Ersek ; Wang, Jian J
>
> Cc: Lu, XiaoyuX
Hi:
Thank you for your comments. The output 1 was designed as a standard error.
Function EdkLogger () sys.exit(1) "1" missing while writing the script
Any question, please let me know. Thanks.
Best Regards
Fan Zhiju
> -Original Message-
> From: devel@edk2.groups.io [mailto:d
There are several reasons why argparse is not used:
1. The logic and parameters of this script are simple.
2. This script is ported from another directory, Only functional changes have
been made to it,
and its architecture is basically unchanged,
3. Printing a Help Message when an error occ
BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1855
GenBiosId is a tool to generate the BIOS ID binary file which uses
the data from the configuration file.
This tool can be run in both Py2 and Py3.
This patch is going to add GenBiosId to Platform/Intel/Tools
Cc: Liming Gao
Cc: Bob Feng
Cc:
On Fri, Jun 21, 2019 at 09:47:37AM +, Fan, ZhijuX wrote:
> Hi:
>
> Thank you for your comments. The output 1 was designed as a standard error.
> Function EdkLogger () sys.exit(1) "1" missing while writing the script
>
>
>
>
> Any question, please let me know. Thanks.
>
> Best Regar
On Fri, Jun 21, 2019 at 10:02:18AM +, Fan, ZhijuX wrote:
> There are several reasons why argparse is not used:
>
> 1. The logic and parameters of this script are simple.
But for others, having to relearn how each individual script works
rather than having all of them use the same common mecha
On Fri, Jun 21, 2019 at 10:03:42AM +, Fan, ZhijuX wrote:
> BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=1855
>
> GenBiosId is a tool to generate the BIOS ID binary file which uses
> the data from the configuration file.
> This tool can be run in both Py2 and Py3.
>
> This patch is going
On Thu, 2019-06-20 at 22:35 +0200, Laszlo Ersek wrote:
> > > I think your note on patch#2 is valuable too and should be captured in
> > > the commit message body. Please consider formulating it with a bit more
> > > neutral tone :)
> >
> > I would prefer to express that particular concern in 'diff
Removed-by: Star Zeng to the series.
> -Original Message-
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Zhang, Shenglei
> Sent: Friday, June 21, 2019 11:00 AM
> To: devel@edk2.groups.io
> Cc: Wang, Jian J ; Wu, Hao A ;
> Ni, Ray ; Zeng, Star ; Gao, Liming
>
>
https://bugzilla.tianocore.org/show_bug.cgi?id=1882
The new notify phase allows platform to configure additional
bus paramters in addition to parameters that can already be configured
with capability override. Specifically we allow to configure bus width,
clock frequency and driver strength. If pl
To allow platform greater control over the bus settings for SD card and eMMC
card we have added a new notify phase to SdMmcOverrideProtocol called
GetOperatingParam.
This phase is signaled before SD card/eMMC initialization and allows platform
to tweak the values in new structure called EDKII_SD
From: "Albecki, Mateusz"
https://bugzilla.tianocore.org/show_bug.cgi?id=1882
Implement support for GetOperatingParamters notify phase
in SdMmcHcDxe driver. GetOperatingParameters notify phase
is signaled before we start card detection and initialization.
Code has been updated for both eMMC and S
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1341
Since UFS specification requirs the data buffer specified
in PRDT to be DWORD aligned in size we had a code in
UfsInitUtpPrdt that aligned the data buffer by rounding down
the buffer size to DWORD boundary. This meant that for SCSI
commands
In current implementation we are checking for device presence every
time we execute UIC command. To make UfsExecUicCommands more generic
checking device presence has been moved to UfsDeviceDetection.
Cc: Hao A Wu
Signed-off-by: Mateusz Albecki
---
.../Bus/Ufs/UfsPassThruDxe/UfsPassThruHci.c
It would be useful for LegacyBiosDxe to be able to get descriptive names
for block devices, for legacy boot options. It gets a bit confusing when
they're all called "Harddisk".
Since we have a collection of the special cases for various types of
device already in BmGetBootDescription(), let's expo
This is hard-coded in the IntThunk structure, and the additional entries
will be needed for other devices like VirtIO and NVMe disks. So admit
that they exist.
Signed-off-by: David Woodhouse
Acked-by: Laszlo Ersek
---
OvmfPkg/Csm/LegacyBiosDxe/LegacyBios.c | 2 +-
1 file changed, 1 insertion(+)
Iterate over the available block devices in much the same way as
BdsLibEnumerateAllBootOption() does, but limiting to those devices
which are PCI-backed, which can be represented in the BbsTable.
One day we might need to extend the BbsTable to allow us to distinguish
between different NVMe namespa
Mostly, this is only necessary for devices that the CSM might have
native support for, such as VirtIO and NVMe; PciBusDxe will already
degrade devices to 32-bit if they have an OpROM.
However, there doesn't seem to be a generic way of requesting PciBusDxe
to downgrade specific devices.
There's In
I know, I said it was Someone Else's Problem. But it annoyed me.
My initial thought was to look for VIRTIO_DEVICE_PROTOCOL on the same
handle but I don't think I can do that if I can't rely on VirtIO being
present in the build. This will do.
Signed-off-by: David Woodhouse
---
.../UefiBootManage
QemuVideoDxe installs its own legacy INT 10h handler for the benefit of
systems like Windows 2008r2 which attempt to use INT 10h even when booted
via EFI.
This interacts extremely badly with a CSM actually attempting to install
a real video BIOS.
The last thing done before invoking a legacy OpROM
No longer call all NVMe & VirtIO devices just "Harddisk". Admittedly,
VirtIO disks are now just called 'Misc Device' instead, but at least
that is now Someone Else's Problem™.
Signed-off-by: David Woodhouse
---
OvmfPkg/Csm/LegacyBiosDxe/LegacyBbs.c | 46 -
OvmfPkg/Csm/L
25 matches
Mail list logo
