From: Akio Takebe Subject: Re: [Patch][2/2][BIOS] Support BCV table Date: Fri, 27 Mar 2009 23:22:03 +0900 Message-ID: <8EC9AEE766A284takebe_akio@jp.fujitsu.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , xen-devel Cc: Akio Takebe List-Id: xen-devel@lists.xenproject.org >On 27/03/2009 10:31, "Akio Takebe" wrote: > >> I don't try the idea of vendor:dev id, but I made a patch(bcv.v2.patch) >> adding the feature of retrying to boot with the next drives. >> What do you think about this patch? >> This patch doesn't add any new syntax, just add the retry feature. >> >> Also I made another patch(support_interactive_boot_for_bcv.patch). >> It allows user to select a bootable pass-through device with F12. >> support_interactive_boot_for_bcv.patch depends on bcv.v2.patch. > >Both are plausible. Looking at your previous email, I get the impression >that the limitations are in rombios, and/or its integration with hvmloader. >Would the right fix really to make rombios be a bit smarter: being able to >load and discard option ROMs into 0xc0000-0xe0000 range, for example? Also, Thanks. Yes, you are right. >I have the view that parts of rombios's POST routines could get moved into >hvmloader, even if we keep rombios for its real-mode BIOS service routines, >after POST. Actually I'd be happy to see hvmloader get a bit fatter at >rombios's expense! Perhaps this is a possibility for the Xen 3.5 development >cycle. OK, I will also improve my patch with your idea of vendor:dev id for Xen-3.5. Best Regards, Akio Takebe