From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49914) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vq7fb-0002az-GQ for qemu-devel@nongnu.org; Mon, 09 Dec 2013 15:43:19 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vq7fT-0001wS-2W for qemu-devel@nongnu.org; Mon, 09 Dec 2013 15:43:11 -0500 Sender: Paolo Bonzini Message-ID: <52A62B3E.1020002@redhat.com> Date: Mon, 09 Dec 2013 21:42:38 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1385112460-27156-1-git-send-email-pbonzini@redhat.com> <516BBB5E-D285-48BE-921E-5C347A1E17BA@suse.de> In-Reply-To: <516BBB5E-D285-48BE-921E-5C347A1E17BA@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH for-1.7] spapr: tie spapr-nvram to -pflash List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Alexey Kardashevskiy , "qemu-ppc@nongnu.org" , "qemu-devel@nongnu.org" Il 09/12/2013 20:25, Alexander Graf ha scritto: > > >> Am 22.11.2013 um 10:27 schrieb Paolo Bonzini : >> >> spapr-nvram's drive property is currently connected to a non-existent >> "-machine nvram=" option. Instead, tie it to -pflash like >> other non-volatile RAM devices. This provides the following possibilities >> for adding a backend for the sPAPR non-volatile RAM: >> >> * -pflash filename >> >> * -drive if=pflash,file=filename,format=raw,... >> >> * -drive if=none,file=filename,format=raw,id=foo,... -global spapr-nvram.drive=foo >> >> Signed-off-by: Paolo Bonzini > > Makes sense, but why for 1.7? At this point it is not for 1.7 of course. :) Paolo