if we already established a iSCSI connection from initiator to target
based on IPv4 stack, after using reconnect -r command, we can not rebuild
the session with the windows target, since the server thought the session
is still exist. This issue is caused by wrong place of acquire ownership of
sock
if the server name expressed as a site local address begain with FEC0
when retrieving from dhcpv6 option 59 boot file url, it incorrectly process it
as a dns name.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Zhang Lubo
Cc: Wu Jiaxin
Cc: Ye Ting
Cc: Fu Siyuan
---
Net
if we already established a iSCSI connection from initiator to target
based on IPv4 stack, after using reconnect -r command, we can not rebuild
the session with the windows target, since the server thought the session
is still exist. This issue is caused by wrong place of acquire ownership of
sock
Hi Star,
The 2nd RFC for SKUs add some autogen to support setting the SKU from a
platform PEIM.
We should consider additional autogen that allows a module to determine the
relationships between SKUs. This additional autogen is not required for the
PCD part of the proposal, but could be used b
Andrew,
It is definitely supported with or without this RFC. No impact to this by this
RFC.
The code path could use GetSku() to be different after an early platform PEIM
called SetSku().
Thanks,
Star
-Original Message-
From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf
Start,
The RFC adds a new mechanism for expressing a relationship between SKUs. The
[SkuIds] section is not tied to PCDs.
The RFC wants to use this relationship to simplify PCD definitions in the DSC
file. Fine. But SkuId relationships are not exclusive to PCDs. There are other
places wher
> On Apr 27, 2017, at 6:53 PM, Zeng, Star wrote:
>
> Tim,
>
> So, you mean SKU in other scope?
>
> The title of this RFC is about PCD. Should they be discussed together? :)
>
> That relationship between PCD SKUs proposed by this RFC is just used to
> *simplify the PCDs configuring for multi
Tim,
So, you mean SKU in other scope?
The title of this RFC is about PCD. Should they be discussed together? :)
That relationship between PCD SKUs proposed by this RFC is just used to
*simplify the PCDs configuring for multiple SKUs in DSC*.
How the relationship between PCD SKUs impact other t
Star --
Simply to say: We use SKUs for many more things than PCDs. While EDK2's build
system may only use SKU IDs in relation with PCDs, our BIOS uses it for many
other things.
So understanding the relationship between SKUs has an impact (for us) beyond
what can be decided by the PCD database.
Tim,
Could you share more information about the case Hii string packages?
Like Mike replied with below explanation, the purpose of this RFC is simple to
extend SKU inheritance in DSC.
"With this proposal, a relationship between SKUs can be declared in the DSC
file, so SKUs can inherit PCD valu
As I understand things, Intel is maintaining CPython 2.7x for UEFI, and they
also helped with Lua port.
I'm wondering if Lua EFI port is actively maintained?
Asking for someone else, see below.
In addition to developer audience, it would seem that there some need for
pre-compiled binaries of
Mike --
For the one-logo case, yes, that would work. But this is the simplest case.
Consider HII string packages.
Tim
-Original Message-
From: Kinney, Michael D [mailto:michael.d.kin...@intel.com]
Sent: Wednesday, April 26, 2017 5:28 PM
To: Tim Lewis ; Zeng, Star ;
edk2-devel@lists.0
Reviewed-by: Jaben Carsey
> -Original Message-
> From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
> Leif Lindholm
> Sent: Wednesday, April 26, 2017 2:49 PM
> To: edk2-devel@lists.01.org
> Cc: Carsey, Jaben ; Daryl McDaniel li...@mc2research.org>
> Subject: [edk2] [P
Hi Alexei,
I am not getting any messages like
Data Abort Exception PC at 0xAFAFAFB2 CPSR 0xA033 NzCveaifT_svc
Are these messages coming in debug mode?.
when i run reconnect -r all i see is a hang and the platform stops to respond.
Is there any follow up on this issue (Is it resolved ?).
Can it be related to
https://bugzilla.tianocore.org/show_bug.cgi?id=211
?
Alexei.
From: edk2-devel on behalf of Amit kumar
Sent: 27 April 2017 12:45:09
To: edk2-devel@lists.01.org
Subject: [edk2] [APPLE MACBOOK BUG] Reconnect -r command hangs in MacBook Air
Hi,
I have been doing some experiments with MacBook Air in EFI SHELL and found out
that Reconnect -r command hangs(ALWAYS REPRODUCIBLE), and sometime devices -b
command(Not reproducible all the time) hangs too.
Please help me get around this issue .
System Details ::
MacBook Air (13-inch, Mid
Reviewed-by: Liming Gao
>-Original Message-
>From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>Yonghong Zhu
>Sent: Wednesday, April 26, 2017 6:36 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming
>Subject: [edk2] [Patch] BaseTools: Fix a bug for BOOLEAN type value in
Reviewed-by: Liming Gao
>-Original Message-
>From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of
>Yonghong Zhu
>Sent: Thursday, April 13, 2017 3:38 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming
>Subject: [edk2] [Patch] BaseTools: Copy "MODULE_UNI_FILE" file into
>OU
Reviewed-by: Liming Gao
>-Original Message-
>From: Zhu, Yonghong
>Sent: Wednesday, April 19, 2017 6:18 PM
>To: edk2-devel@lists.01.org
>Cc: Gao, Liming
>Subject: [Patch 0/4] BaseTools: support OPENSSL_PATH has space character
>
>Update related Tools to support OPENSSL_PATH has space char
On 04/27/17 07:40, Ni, Ruiyu wrote:
> Laszlo,
> I believe the "Unable to boot" message was added by intention.
>
> I just checked the UEFI Spec Boot Manager chapter again, still I didn't
> find any wording to say what to do, when boot and recovery failure
> happens.
>
> Putting "Unable to boot" m
20 matches
Mail list logo
