public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, pedro.falcato@gmail.com
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	 "Lin, Benny" <benny.lin@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	 "Liu, Zhiguang" <zhiguang.liu@intel.com>,
	Sean Brogan <sean.brogan@microsoft.com>,
	 Michael Kubacki <mikuback@linux.microsoft.com>,
	Leif Lindholm <llindhol@qti.qualcomm.com>
Subject: Re: [edk2-devel] [PATCH 0/2] Support FDT library.
Date: Fri, 31 Mar 2023 13:39:33 +0200	[thread overview]
Message-ID: <ffd5ohlve563y6tpjqvmgahguefhaok5t254kwhjeo5g3w6kjv@vuska3losaxy> (raw)
In-Reply-To: <CAKbZUD2u_tG5uV_+T4WwgBwss2cX89fBD+mA34BkJA8TAZqvKg@mail.gmail.com>

  Hi,

> > Getting down to one libc wrapper would be great.  Do you want to provide a proposed
> > implementation?  That could be handled as a separate task.
> 
> I would like it if we could stop contributing to that problem. We very
> much *know* there is a problem with both libc fragments and compiler
> intrinsic fragments all over edk2.

I'd suggest to start with what we already have in the tree.  Which is
(not fully sure the list is actually complete):

 - CryptoPkg/Library/Include/ carrying the bits needed to make openssl
   compile, and
 - CryptoPkg/Library/IntrinsicLib (again, for openssl, mostly IA32, some
   X64) and,
 - ArmPkg/Library/CompilerIntrinsicsLib (mostly ARM, some AARCH64).

Can we move that over to MdePkg so everyone can easily share it instead
of adding more copies of the same to the tree?

I have an old branch gathering dust doing that for the intrinsics, I can
try rebasing it to latest master next week ...

take care,
  Gerd


  parent reply	other threads:[~2023-03-31 11:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 16:52 [PATCH 0/2] Support FDT library benny.lin
2023-03-30 16:52 ` [PATCH 1/2] MdePkg: " Benny Lin
2023-03-30 17:01   ` Michael D Kinney
2023-03-30 23:19   ` [edk2-devel] " Pedro Falcato
2023-04-12 16:59     ` Benny Lin
2023-03-30 16:52 ` [PATCH 2/2] .pytool: " Benny Lin
2023-03-30 21:50 ` [edk2-devel] [PATCH 0/2] " Pedro Falcato
2023-03-30 22:59   ` Michael D Kinney
2023-03-30 23:26     ` Pedro Falcato
2023-03-30 23:32       ` Michael D Kinney
2023-03-31  2:35         ` Pedro Falcato
2023-03-31 11:39       ` Gerd Hoffmann [this message]
2023-03-31 12:18         ` Pedro Falcato
2023-03-31 12:17       ` Leif Lindholm
2023-03-31 12:12   ` Leif Lindholm
2023-04-01  1:29 ` Andrei Warkentin
2023-04-06 16:33   ` Sheng Lean Tan
2023-04-07 13:23     ` Pedro Falcato
2023-04-07 22:35       ` Andrei Warkentin
2023-04-07 23:04         ` Michael D Kinney
2023-04-11 13:19           ` Sheng Lean Tan
2023-04-11 16:07             ` Pedro Falcato
2023-04-11 17:00               ` 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=ffd5ohlve563y6tpjqvmgahguefhaok5t254kwhjeo5g3w6kjv@vuska3losaxy \
    --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