From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 8FB8621163247 for ; Fri, 12 Oct 2018 09:07:04 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id DC162C04BD3B; Fri, 12 Oct 2018 16:07:03 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-87.rdu2.redhat.com [10.10.120.87]) by smtp.corp.redhat.com (Postfix) with ESMTP id EEFFC7ADDF; Fri, 12 Oct 2018 16:07:02 +0000 (UTC) To: Leif Lindholm , stephano Cc: edk2-devel@lists.01.org References: <20181012132718.mgpg3f42hjulcwfk@bivouac.eciton.net> From: Laszlo Ersek Message-ID: <180aa195-2e56-06a6-ef66-747e6c3210f7@redhat.com> Date: Fri, 12 Oct 2018 18:07:01 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181012132718.mgpg3f42hjulcwfk@bivouac.eciton.net> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Fri, 12 Oct 2018 16:07:03 +0000 (UTC) Subject: Re: TianoCore Community Meeting Minutes X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2018 16:07:04 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit On 10/12/18 15:27, Leif Lindholm wrote: > On Thu, Oct 11, 2018 at 10:43:57AM -0700, stephano wrote: >> Switching to Standard C Types >> ----------------------------- >> Both Shawn and Nate mentioned that the current system has been in place for >> a long time and some people prefer the current setup. I can start an email >> discussion around this issue specifically if anyone feels strongly that we >> should be using standard types. > > So, I don't think we made it this far down the agenda on the US-EU > call. > > One way would be to simply explicitly permit it, possibly with the > constraint that every module needs to pick one and stick with it, > unless people object. > > I think we'll want to discuss this in a US-EU call as well. I'm playing devil's advocate here -- because, in general, I'm a fan of sticking with standard C as much as possible --, but I see a big obstacle in the way. That obstacle is "Table 5. Common UEFI Data Types", in the UEFI spec. Until a good portion of that table is expressed in terms of standard C types as well (expanding upon the current definitions), possibly in an edk2-level spec (i.e. not necessarily in the UEFI spec itself), I think there's no chance to enable standard C types in edk2 *meaningfully*. Because, as soon as you have to call a PI or UEFI interface, you'll have to stick with the PI/UEFI spec types anyway. >> Using Git Submodules (like we do with OpenSSL) >> -------------------- > > We didn't make it here either. What would we use it _for_? > I think the openssl case makes a lot of sense, but what else? We embed a bunch of other projects (libraries, mainly): - Oniguruma - Brotli - fdt - LZMA SDK - ... Thanks Laszlo