From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: <devel@edk2.groups.io>, <ardb@kernel.org>, <rebecca@bsdio.com>
Cc: <michael.d.kinney@intel.com>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH 2/2] MdePkg: Update code to be more C11 compliant by using __func__
Date: Fri, 10 Feb 2023 15:19:38 +0000 [thread overview]
Message-ID: <540fd56f-269b-5767-613e-67a0321bb1fe@quicinc.com> (raw)
In-Reply-To: <CAMj1kXEYhvUAP+R1zi7H4XCDoax4itASGTon8FaciKdaNuPHdA@mail.gmail.com>
On 2023-02-10 11:45, Ard Biesheuvel wrote:
>> I wasn't sure if we cared about EBC builds these days. Given the link on
>> https://www.intel.com/content/www/us/en/architecture-and-technology/unified-extensible-firmware-interface/efi-homepage-general-technology.html
>> to the compiler goes to a generic page that doesn't mention it, is it
>> possible to get a copy if I want to verify if changes I'm making are
>> compatible?
>
> We tried to get access to this at Linaro, but I don't think it is
> still available. Leif may remember better.
After asking around, some shady character in a café passed me a very
long and customized URL on a note in a brown paper bag, and I was able
to procure a single license for ARM. I don't think we succeeded for Linaro.
> I wonder whether we should simply drop EBC support? It is unlikely
> that all the changes that went into EDK2 over the years have not
> caused a single EBC regression in the library components that are
> needed to build UEFI drivers that target EBC.
The appearance of RISC-V and Loongarch since those days highlight why
architecture independent drivers would be a good thing, but EBC is
pining for the fjords.
If we don't drop EBC now, we should start drafting a timeline for when
we will.
/
Leif
next prev parent reply other threads:[~2023-02-10 15:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 15:45 [PATCH 1/2] MdePkg: Update Base.h to be compliant with C11 Rebecca Cran
2023-02-09 15:45 ` [PATCH 2/2] MdePkg: Update code to be more C11 compliant by using __func__ Rebecca Cran
2023-02-10 1:01 ` [edk2-devel] " Michael D Kinney
2023-02-10 1:21 ` Rebecca Cran
2023-02-10 11:45 ` Ard Biesheuvel
2023-02-10 15:19 ` Leif Lindholm [this message]
2023-02-10 18:16 ` Michael D Kinney
2023-02-12 19:59 ` Rebecca Cran
2023-03-14 2:19 ` Rebecca Cran
2023-03-14 20:40 ` Michael D Kinney
2023-03-17 13:31 ` Rebecca Cran
2023-03-17 15:16 ` Michael D Kinney
2023-03-22 16:58 ` Michael D Kinney
2023-03-22 17:45 ` Rebecca Cran
2023-03-23 0:58 ` Michael D Kinney
2023-03-23 1:43 ` Huang, Yanbo
2023-03-23 1:46 ` Rebecca Cran
2023-03-17 4:23 ` Sunil V L
2023-02-10 1:03 ` [edk2-devel] [PATCH 1/2] MdePkg: Update Base.h to be compliant with C11 Michael D Kinney
2023-02-10 1:14 ` Rebecca Cran
2023-02-10 4:15 ` Rebecca Cran
2023-03-06 16:39 ` Rebecca Cran
2023-03-10 2:45 ` 回复: " gaoliming
2023-03-10 17:58 ` Rebecca Cran
2023-03-13 17:54 ` Rebecca Cran
2023-03-13 20:46 ` Michael D Kinney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=540fd56f-269b-5767-613e-67a0321bb1fe@quicinc.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox