From: "Andrei Warkentin" <andrei.warkentin@intel.com>
To: Pedro Falcato <pedro.falcato@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Tan, Lean Sheng" <sheng.tan@9elements.com>
Cc: "Lin, Benny" <benny.lin@intel.com>,
"Kinney, Michael D" <michael.d.kinney@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>
Subject: Re: [edk2-devel] [PATCH 0/2] Support FDT library.
Date: Fri, 7 Apr 2023 22:35:56 +0000 [thread overview]
Message-ID: <PH8PR11MB68566AC98E14E7FF7885268283969@PH8PR11MB6856.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAKbZUD06RDvqM5TNQOou2W8is592-Fs9gL_VUL_8PiDgSuKPog@mail.gmail.com>
I think in general it would be nice to understand the long term picture of a change, esp. since there is already FDT support in EDK2 in various forms (with libraries and drivers depending on the existing FdtLib). So it would really of confusing to see another FDT library in MdePkg, without a clear reasoning for the work (this isn't reflected in the BZ) and a clear action plan to end up with just one FDT library in MdePkg in some identified time frame.
I do think FDT lib *does* belong in MdePkg, but it seems the shortest path to get there is to simply move the existing EmbeddedPkg one (and update all users). Subsequent cleanup can be incremental. And regardless, every existing FdtLib user ought to be updated to use the new one, so there need to be more patches (we're not just throwing the code over the wall, right?)
A
> -----Original Message-----
> From: Pedro Falcato <pedro.falcato@gmail.com>
> Sent: Friday, April 7, 2023 8:24 AM
> To: devel@edk2.groups.io; Tan, Lean Sheng <sheng.tan@9elements.com>
> Cc: Warkentin, Andrei <andrei.warkentin@intel.com>; Lin, Benny
> <benny.lin@intel.com>; Kinney, Michael D <michael.d.kinney@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>
> Subject: Re: [edk2-devel] [PATCH 0/2] Support FDT library.
>
> On Thu, Apr 6, 2023 at 5:34 PM Sheng Lean Tan
> <sheng.tan@9elements.com> wrote:
> >
> > Thanks for the nice feedback Pedro, Gerd and Andrei! Yeah it seems like a
> valid concern here as Mik mentioned on edk2-libc, and it seems to fits edk2
> long term interest on this.
> > Can we file this as an issue in Bugzilla for tracking or something? Since this
> will take some time to work on this as it involves a bigger discussion,
> personally I think we could get this FDT patch in first meanwhile, and also
> remove the FDT from Embedded Pkg as next step, per discussion with Leif?
> > What do you think?
>
> I'm all for not merging this without a proper solution in that regard (I even
> presented a quick RFC solution which wasn't tested by anyone involved in
> this patch, yet).
>
> But if there really is an urgent need for this lib, I'm O-K with merging this
> given that all my concerns are addressed (minus libc duplication).
>
> --
> Pedro
next prev parent reply other threads:[~2023-04-07 22:36 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
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 [this message]
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=PH8PR11MB68566AC98E14E7FF7885268283969@PH8PR11MB6856.namprd11.prod.outlook.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