From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=2a00:1450:400c:c09::229; helo=mail-wm0-x229.google.com; envelope-from=pete@akeo.ie; receiver=edk2-devel@lists.01.org Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0550021B00DC1 for ; Tue, 14 Nov 2017 09:26:52 -0800 (PST) Received: by mail-wm0-x229.google.com with SMTP id r68so18876906wmr.0 for ; Tue, 14 Nov 2017 09:31:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akeo-ie.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=oe45wg+SinCS3DGHUQcZmb/wjwFAn87vRGAWXWqT7DA=; b=mUAIbz97t0P6FNmOGPlxmoIuyW7dFWuwRveW4PfEtrzcxbix0kIIopbcGidaw8YlkA VZkOu3ShQN7Lw5Y7j1RmYBKZ1MSwBba8E8Q9DHSdGHAZQYrIH7QCz9sFYHCT6+LVblfH pXY5q9TDtl0Bn+PTUMssRif2twnmdMChr0awy9HHWknTVL98UHJsxpZ2/IVw8hia4/9a mjj9FUTEhIuR3PO2xN5UNVeLsLw3knFwSqAAlO5z/JepctEo0rTr5Rbz8z3e0vdvTUoI x0nBORjj7oZIZnH5C4t6H7FSHpYOwklhg1Me6hqUwxEZ3va05O/jAWvslmttZ4Cz3kgq nrdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=oe45wg+SinCS3DGHUQcZmb/wjwFAn87vRGAWXWqT7DA=; b=sSy8/jVbQHxQn64EzR8VnPYqjkZqOf7+EQg/QfBMqcApJkxcyVk7He2RaU64LVkcKy ZQKXZuCv41vNFyj6QUWb1TAGx1YUL0RqvkcO+0oGLJZ+A1f1ts9OymWpW1fkWldGZtVQ 6qM4bNVG7HsfAhF4zRlb3FOyv8xsd3mDdfAgKTE/dpq66wqk1S1d7e0CF42SMuqag6xP QxQKdCY9HBF57UPJIbbSQDykOBKgmNmTpm7ryZOHmHxuAJ+3i9MliIyIRQRGxZ4nlruC k/UEte4Gir58vP7fK4OxO38kLKDUBOKPpq5uowEVx+VC1Dv9FXsZhsPLmrXRnLINRWuH 8yug== X-Gm-Message-State: AJaThX6rb2dQW/FyPSfLMd2tarr60FwKSxlHWvWL6xUB6M9sPxFET73V Oxhl8Pr8BEVDKJ9BiExzP331qJWkFpc= X-Google-Smtp-Source: AGs4zMbVSYc2TO4hQBp1ZNW2A4Y8C5T0yQNWYUsLD/maCtQ5x7GZKvGixgMp+XPtKM7FMKwtWkHFhA== X-Received: by 10.80.142.17 with SMTP id 17mr18630567edw.115.1510680658652; Tue, 14 Nov 2017 09:30:58 -0800 (PST) Received: from [10.0.0.101] ([84.203.45.202]) by smtp.googlemail.com with ESMTPSA id y1sm16003477edl.1.2017.11.14.09.30.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Nov 2017 09:30:57 -0800 (PST) To: Kurt Kennett , "edk2-devel@lists.01.org" References: <20171114123229.3516-1-pete@akeo.ie> From: Pete Batard Message-ID: Date: Tue, 14 Nov 2017 17:30:56 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: Subject: Re: [PATCH 0/4] BaseTools: Add VS2017 support, including ARM and AARCH64 X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 17:26:53 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Hi Kurt, On 2017.11.14 16:16, Kurt Kennett wrote: > Does this build and boot a platform? Not yet, but I believe I got pretty close to a full build for ARM. However, the resources I can devote to finalizing ARM image generation, and even more so, to add the missing resources for AARCH64 image generation are limited, even more so as I am no ARM specialist. I was actually hoping that, with the application of these patches, EDK2 contributors would step in to help with the effort of filling the assembly gaps, as well as finalize image generation for ARM and AARCH64. > This should not be committed until a platform is building and booting to UEFI shell, IMO. Well, I see it a bit as a catch 22. If we don't get the VS2017 ARM toolchains in, I don't think many people will be willing to help with the image generation, because there will be very little incentive for them to do so. And if we wait for image generation to be sorted out before adding the toolchains, it may very well be a couple more years before everything is finalized... which would penalize the people who simply want the convenience of VS2017 support to build regular ARM and AARCH64 applications. IMO, a gradual approach to introducing VS2017 ARM/AARCH64 support might be preferable to an "all or nothing" one. Regards, /Pete