From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: <devel@edk2.groups.io>, <ardb@kernel.org>,
Rebecca Cran <rebecca@bsdio.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [PATCH 0/3] ArmPlatformPkg: Fix Scripts/Ds5 debugging and Makefile
Date: Wed, 13 Apr 2022 10:56:08 -0600 [thread overview]
Message-ID: <db242fdf-2a9d-84ab-8518-d16e9c471134@quicinc.com> (raw)
In-Reply-To: <CAMj1kXFJuCKYhvp3oniaAqSmZGYoK7o-tLF+csPR7KHxk68k1Q@mail.gmail.com>
On 4/13/22 10:51, Ard Biesheuvel wrote:
> On Mon, 11 Apr 2022 at 03:18, Rebecca Cran <rebecca@bsdio.com> wrote:
>> Also, I noticed Scripts/Makefile defaults to RVCT. Are people still using that, or has everyone moved to gcc or the newer Arm compilers?
>>
> RVCT is 32-bit only, as far as I know, so I don't think anyone still
> cares about it.
Thanks. If there's agreement I can put together a set of patches to
remove support from the various places we have it in the tree (e.g.
here, Conf/tools_def.txt etc.)
--
Rebecca Cran
next prev parent reply other threads:[~2022-04-13 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 1:16 [PATCH 0/3] ArmPlatformPkg: Fix Scripts/Ds5 debugging and Makefile Rebecca Cran
2022-04-11 1:16 ` [PATCH 1/3] ArmPlatformPkg: Fix error message in Scripts/Ds5/edk2_debugger.py Rebecca Cran
2022-04-11 1:16 ` [PATCH 2/3] ArmPlatformPkg: Fix target initialisation in cmd_load_symbols.py Rebecca Cran
2022-04-11 17:39 ` Rebecca Cran
2022-04-11 1:16 ` [PATCH 3/3] ArmPlatformPkg: Fix EDK2_DSC check in Scripts/Makefile Rebecca Cran
2022-04-11 1:18 ` [PATCH 0/3] ArmPlatformPkg: Fix Scripts/Ds5 debugging and Makefile Rebecca Cran
2022-04-13 16:51 ` [edk2-devel] " Ard Biesheuvel
2022-04-13 16:56 ` Rebecca Cran [this message]
2022-04-20 0:43 ` Rebecca Cran
2022-05-03 9:14 ` Ard Biesheuvel
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=db242fdf-2a9d-84ab-8518-d16e9c471134@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