From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=2a00:1450:4864:20::444; helo=mail-wr1-x444.google.com; envelope-from=leif.lindholm@linaro.org; receiver=edk2-devel@lists.01.org Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) (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 3FDD72119A454 for ; Fri, 14 Dec 2018 08:36:50 -0800 (PST) Received: by mail-wr1-x444.google.com with SMTP id t6so5861886wrr.12 for ; Fri, 14 Dec 2018 08:36:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=86elNldrsos4rhl6DRHC4evpOljTV2CWZc4SayP/2e4=; b=GoeJM7mZD151Q/SFDucAxjRNSEKaOaiBybnPY3Gc3qwFhyqoJiRgJBRxMx7KlVY7LS Y9geZZlk5NQu6HsqPGQqHs2nVyLtZ8d+PVH+o+YNLzlPCCmcXeSsjcXehfRCWGW3fmNU 3XdHcxn+PBWC59eDJG9VsmKRvbOdQ+m5YBxZw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=86elNldrsos4rhl6DRHC4evpOljTV2CWZc4SayP/2e4=; b=MIu+bBqvg4uD4Sm+4kY2xoIUipPGPWmBzrTqhr7VviD087smv+KB6LHuiBLlLcPtKa anmFRbdbQzAfMptPS6U+FeI7StdMOWrIzLe/TnZaznx69rp9IbPt62hPCuLFgPuZN4BC fjEDTb09jjT4GVjrAiYrYC13tNetTdTk6Ae0pKRJq3oXDoCbD6EVzOOjFfUM5jY7Tia4 YvlEBE8bmK8iJjZmlgcHb7GzVLN41w4K10lc7omOYRuitma736P8NokXhduGzMpIf2XS wNU+cJvaWM6QnGxVmC/K/cbimD94e+ymqFACFdag38E6PtGveF4RAc9mIbpj82VA5CRo dzjg== X-Gm-Message-State: AA+aEWb8/KHsymVH7B4NC9vMULFWFls4SVzqLectYeLGUF82/Mct+dI3 WvG2lBFvUgtT1f/oxwVPZlNBQg== X-Google-Smtp-Source: AFSGD/VT1Wpn9GKLJRrOenq7LH+qBXUXQWgbCaMZ1pOOb0A+1d5V+KJp0xR5J5YAgiFA+fMQHAbCog== X-Received: by 2002:a5d:5409:: with SMTP id g9mr3292474wrv.88.1544805409156; Fri, 14 Dec 2018 08:36:49 -0800 (PST) Received: from bivouac.eciton.net (bivouac.eciton.net. [2a00:1098:0:86:1000:23:0:2]) by smtp.gmail.com with ESMTPSA id r12sm6597165wrq.3.2018.12.14.08.36.47 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 14 Dec 2018 08:36:47 -0800 (PST) Date: Fri, 14 Dec 2018 16:36:46 +0000 From: Leif Lindholm To: Philippe =?iso-8859-1?Q?Mathieu-Daud=E9?= Cc: Pete Batard , edk2-devel@lists.01.org, Laszlo Ersek , Ard Biesheuvel Message-ID: <20181214163646.oji43hgeqxlp3vzq@bivouac.eciton.net> References: <20181210123853.4864-1-pete@akeo.ie> <20181211181040.7i6dfxrl4kfcxspz@bivouac.eciton.net> <20181212183244.sn3h6sgsmz6s4hti@bivouac.eciton.net> <20181212200154.xprpwxlhsmaur744@bivouac.eciton.net> <979c097f-62a6-1b37-049f-bbb751bf986e@redhat.com> MIME-Version: 1.0 In-Reply-To: <979c097f-62a6-1b37-049f-bbb751bf986e@redhat.com> User-Agent: NeoMutt/20170113 (1.7.2) Subject: Re: [PATCH v2 edk2-platforms 00/20] Platform/Broadcom: Add Raspberry Pi 3 support 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, 14 Dec 2018 16:36:51 -0000 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Fri, Dec 14, 2018 at 05:14:05PM +0100, Philippe Mathieu-Daudé wrote: > >> I can certainly upload binary releases for the required ATF files in my > >> github clone of ATF, and then add links to that in the readme with the > >> instructions on how to rebuild ATF. > >> > >> However, I'd rather wait to do that until there has been an official tagged > >> new release for ATF (which would be 2.1 at this stage, since our changes > >> have been applied after 2.0), as it'll look better for Pi users to see an > >> initial ATF serial output that says "BL<#>: v2.1(release)" instead of the > >> current "BL<#>: v2.0(release):v2.0-278-gc3859557" > >> > >> How about this then: If ATF produces a formal release before this proposal > >> is integrated, I'll amend it to remove the ATF binary blobs and apply the > >> suggestion above, with the Atf/ build/link data moved out of non-osi. But if > >> they don't, I'll keep the proposal for ATF as is, and then submit a patch to > >> remove the non-osi data and apply the above at a later date, once there has > >> been a new ATF release. > > > > Yeah, this certainly works for me. > > I setup this Dockerfile [1] to have reproducible builds and avoid to > store those binaries in the non-osi repository, what do you think about > this approach? Get off my lawn? :) > [1] available here: > https://gitlab.com/philmd/edk2-platforms/blob/raspi3-atf/Platform/RaspberryPi/RPi3/Arm-Tf/Dockerfile I think it's a good thing to have, especially for something like the Pi. I guess if that exists, we can trust people who prefer not to use containers to be happy to follow the Readme, or grab binaries from Pete's github? / Leif