From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49855) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoDdL-0001ym-Ej for qemu-devel@nongnu.org; Mon, 19 Oct 2015 12:50:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZoDdI-0006Or-72 for qemu-devel@nongnu.org; Mon, 19 Oct 2015 12:50:03 -0400 Received: from mail-vk0-f46.google.com ([209.85.213.46]:35052) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoDdI-0006Ok-3D for qemu-devel@nongnu.org; Mon, 19 Oct 2015 12:50:00 -0400 Received: by vkfw189 with SMTP id w189so23798753vkf.2 for ; Mon, 19 Oct 2015 09:49:59 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Mon, 19 Oct 2015 17:49:40 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [RFC 0/3] ARM: Machine specific boot blobs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: Rob Herring , Peter Crosthwaite , "qemu-devel@nongnu.org Developers" , Guenter Roeck , Alistair Francis On 18 October 2015 at 17:25, Peter Crosthwaite wrote: > Ping! > > Although a little featurish and RFCish, this does repair the boot of > two ARM machines so it is very much a bugfix and we should consider > for 2.5. Otherwise we go to release (again) with two broken machines. The general idea looks ok to me, but sending a patchset out labelled RFC when we hit softfreeze is a pretty good way to cause people to ignore it :-) Patch 1 looks OK I think; haven't looked too closely at the others. How are you picking the firmware blob addresses ? thanks -- PMM