From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0b-0031df01.pphosted.com (mx0b-0031df01.pphosted.com [205.220.180.131]) by mx.groups.io with SMTP id smtpd.web10.53122.1680265087407486776 for ; Fri, 31 Mar 2023 05:18:07 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@quicinc.com header.s=qcppdkim1 header.b=BPyU69xa; spf=permerror, err=parse error for token &{10 18 %{ir}.%{v}.%{d}.spf.has.pphosted.com}: invalid domain name (domain: quicinc.com, ip: 205.220.180.131, mailfrom: quic_llindhol@quicinc.com) Received: from pps.filterd (m0279872.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 32VAv1ap015075; Fri, 31 Mar 2023 12:17:59 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=qcppdkim1; bh=28BshI2i7K6ER4GKe1cJqo3k9I0Gv40yTy2gK1MPTIA=; b=BPyU69xa9w08wBWT+hi3hycGcjX/LDwSMoFrZwwuNZTWaSunNJRuvRHdhLYH/n0CJeuM PZy6TPEiTVc2T64cnSf4spIAQqGgVuLgmbqmRFfzB+hAXrndDCDyfrJ+Fb1Ml0YwQ4Oj CR54gLLd1NEt8Z+xu4+eARS2lGPtww+gPfIiQRo8tZamQ6H25PxWEPCNvfYOG//MgDGV c9uGn0HYKLSv7AcyJitphDH6qI2TayPzBxxpRnzzzKzGhUktYbO581dYKGgf4mKjYNkB OGKCpsaLjm79zRu6PQK+KYcioaU+z4Zr6z/OFWDD8OgkXbm8mP+0DaiMQ1XuK5jSgqdf uA== Received: from nasanppmta05.qualcomm.com (i-global254.qualcomm.com [199.106.103.254]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 3pncx0ttsv-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 31 Mar 2023 12:17:59 +0000 Received: from nasanex01c.na.qualcomm.com (nasanex01c.na.qualcomm.com [10.45.79.139]) by NASANPPMTA05.qualcomm.com (8.17.1.5/8.17.1.5) with ESMTPS id 32VCHwJW003005 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 31 Mar 2023 12:17:58 GMT Received: from qc-i7.hemma.eciton.net (10.80.80.8) by nasanex01c.na.qualcomm.com (10.45.79.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.42; Fri, 31 Mar 2023 05:17:55 -0700 Date: Fri, 31 Mar 2023 13:17:52 +0100 From: "Leif Lindholm" To: , CC: "Kinney, Michael D" , "Lin, Benny" , "Gao, Liming" , "Liu, Zhiguang" , Sean Brogan , Michael Kubacki , Leif Lindholm Subject: Re: [edk2-devel] [PATCH 0/2] Support FDT library. Message-ID: References: MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nasanex01c.na.qualcomm.com (10.45.79.139) X-QCInternal: smtphost X-Proofpoint-Virus-Version: vendor=nai engine=6200 definitions=5800 signatures=585085 X-Proofpoint-ORIG-GUID: WfoDn7h_zvtcOCOL0PaEyKl8wKHtw_jJ X-Proofpoint-GUID: WfoDn7h_zvtcOCOL0PaEyKl8wKHtw_jJ X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-03-31_06,2023-03-30_04,2023-02-09_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 mlxscore=0 malwarescore=0 priorityscore=1501 bulkscore=0 adultscore=0 clxscore=1015 suspectscore=0 phishscore=0 mlxlogscore=999 spamscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2303200000 definitions=main-2303310099 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Fri, Mar 31, 2023 at 00:26:37 +0100, Pedro Falcato wrote: > We also have a whole libc implementation in edk2-libc that seems to be > permanently gathering dust until Intel touches it for Python purposes > from time to time. So between crypto, libfdt, etc, could we try to > unify things here a bit? Personally, I'd quite like to nuke edk2-libc. The only effect I'm seeing from it is that it keeps misleading people into believing it's sensible to expect full POSIX compliance under UEFI, then embed those expectations into their organisational workflows. Meanwhile, it receives (next to) no security fixes. / Leif