From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuPEN-0003e0-Ll for qemu-devel@nongnu.org; Tue, 10 Jun 2014 12:49:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WuPEG-0007tf-6p for qemu-devel@nongnu.org; Tue, 10 Jun 2014 12:49:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38136) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WuPEF-0007qb-KZ for qemu-devel@nongnu.org; Tue, 10 Jun 2014 12:48:55 -0400 Message-ID: <539736F3.6080605@redhat.com> Date: Tue, 10 Jun 2014 18:48:51 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1402411908-25821-1-git-send-email-peter.maydell@linaro.org> <1402411908-25821-2-git-send-email-peter.maydell@linaro.org> <53972F12.4030900@redhat.com> <539730FD.8070204@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/2] hw/arm/virt: Provide flash devices for boot ROMs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Michael Casadevall , QEMU Developers , Christoffer Dall , Patch Tracking Il 10/06/2014 18:38, Peter Maydell ha scritto: > On 10 June 2014 17:23, Paolo Bonzini wrote: >> Il 10/06/2014 18:17, Peter Maydell ha scritto: >> >>>>>>> + create_one_flash("virt.flash0", flashbase, flashsize); >>>>>>> + create_one_flash("virt.flash1", flashbase + flashsize, >>>>>>> flashsize); >>>> >>>>> >>>>> >>>>> What happens if you specify both -bios and -drive if=pflash? Can you >>>>> check >>>>> that the user does not specify both? >>> >>> We'll create the device and then overlay it with the "ROM" >>> image, same as for vexpress. (If the bios image is short >>> then the underlying pflash contents will be visible.) >> >> >> Could you provide slightly saner semantics for -M virt? :) > > Heh. How about: > * if both bios_name and pflash drive 0 specified, this is an error > * otherwise use whichever we have > * (NB that bios_name + pflash drive 1 is a reasonable combination) Yes, it is. > vexpress should do this too, for consistency. If it's okay for you, why not. Paolo > (Actually ideally I'd just make bios_name be a convenient > shortcut for specifying a block backend for pflash that's > readonly and permits undersized backing files, but I don't > think we can easily do that right now.) > > thanks > -- PMM >