All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Juergen Keil <jk@tools.de>,
	Steve Ofsthun <sofsthun@virtualiron.com>,
	xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>,
	Bruce Rogers <brogers@novell.com>,
	Ke Liping <liping.ke@intel.com>, Yu Ke <ke.yu@intel.com>,
	Travis Betak <travis.betak@amd.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Keir Fraser <keir.fraser@citrix.com>,
	Seiji Munetoh <seiji.munetoh@gmail.com>
Subject: Re: [Patch][RFC] Update rombios.c
Date: Thu, 18 Dec 2008 22:27:39 +0900	[thread overview]
Message-ID: <494A4FCB.6080200@jp.fujitsu.com> (raw)
In-Reply-To: <20081218111810.GM460@york.uk.xensource.com>

Tim Deegan wrote:
> Hi,
> 
> At 23:50 +0900 on 17 Dec (1229557835), Akio Takebe wrote:
>> This patch update rombios to the latest Bochs's.
>> I'd like to corabolate bochs community to enhance the guest bios.
>> I'm not familiar around TCGBIOS.
>> So could you review the patch?
>>
>> I tested boot/shutdown, S3 suspend/resume with linux guest.
>> Any comments are welcome :-)
> 
> Does the boot-options menu work properly after the patch?  This bit of
> code looks suspect to me; surely some more translation is necessary to
> turn a scan code into an offset into the boot device table:
> 
> +      while (!valid_choice) {
> +        scan_code = get_keystroke();
> +        if (scan_code == 0x01 || scan_code == 0x58) /* ESC or F12 */
> +        {
> +          valid_choice = 1;
> +        }
> +        else if (scan_code <= count)
> +        {
> +          valid_choice = 1;
> +          scan_code -= 1;
> +          /* Set user selected device */
> +          write_word(ebda_seg, IPL_BOOTFIRST_OFFSET, scan_code);
> +        }
> +      }
> 
Thank you for your review.
I used the bochs upstream code instead of xen's
because I want to use the upstream code.
It works fine. The scan_codes are below.
http://www.arl.wustl.edu/~lockwood/class/cs306/books/artofasm/APNDXC.PDF

> Otherwise, this patch looks good to me, though it's enormous so I
> haven't looked at every detail.
> 
> Also: does this update mean that the Xen rombios now has two separate
> 32-bit extensions?  Might it be worth using the upstream one instead of
> maintaining our own?
> 
I added "#define LAGACY" in rombios.h
So the patch uses Xen's 32bit extentions.
As you said, using the upstream one may be better.
But merging the upstream's 32bits extentions looks difficult
because xen initialize some parts of BIOS data in hvmloader.

Best Regards,

Akio Takebe

  reply	other threads:[~2008-12-18 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 14:50 [Patch][RFC] Update rombios.c Akio Takebe
     [not found] ` <OFDF7B026B.B70180EB-ON85257522.0054EDB1-85257522.0055840C@us.ibm.com>
2008-12-17 23:42   ` Akio Takebe
2008-12-17 23:43 ` Akio Takebe
2008-12-17 23:52 ` Akio Takebe
2008-12-18 11:18 ` Tim Deegan
2008-12-18 13:27   ` Akio Takebe [this message]
2008-12-18 13:33     ` Tim Deegan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=494A4FCB.6080200@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=berrange@redhat.com \
    --cc=brogers@novell.com \
    --cc=jk@tools.de \
    --cc=ke.yu@intel.com \
    --cc=keir.fraser@citrix.com \
    --cc=liping.ke@intel.com \
    --cc=seiji.munetoh@gmail.com \
    --cc=sofsthun@virtualiron.com \
    --cc=stefanb@us.ibm.com \
    --cc=travis.betak@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.