From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: xen-devel <xen-devel@lists.xensource.com>,
"Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: [Patch] Enable Option ROM write access
Date: Fri, 26 Dec 2008 14:17:56 +0900 [thread overview]
Message-ID: <49546904.60604@jp.fujitsu.com> (raw)
In-Reply-To: <4952EAC2.1070700@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
Akio Takebe wrote:
> Hi,
>
> This patch is enabling write access during rom_scan.
>
> Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com>
I think this patch is better than the previous one.
Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com>
Best Regards,
Akio Takebe
[-- Attachment #2: enable_write_access.patch --]
[-- Type: text/x-diff, Size: 634 bytes --]
diff -r e2f36d066b7b tools/firmware/rombios/rombios.c
--- a/tools/firmware/rombios/rombios.c Mon Dec 22 13:48:40 2008 +0000
+++ b/tools/firmware/rombios/rombios.c Fri Dec 26 14:13:34 2008 +0900
@@ -11008,11 +11008,9 @@
#endif // BX_ELTORITO_BOOT
#ifdef HVMASSIST
- call _enable_rom_write_access
call _clobber_entry_point
call _copy_e820_table
call smbios_init
- call _disable_rom_write_access
#endif
call _init_boot_vectors
@@ -11020,6 +11018,7 @@
mov cx, #0xc800 ;; init option roms
mov ax, #0xe000
call rom_scan
+ call _disable_rom_write_access
#if BX_ELTORITO_BOOT
call _interactive_bootkey
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2008-12-26 5:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 2:06 [Patch] Enable Option ROM write access Akio Takebe
2008-12-26 5:17 ` Akio Takebe [this message]
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=49546904.60604@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=kevin.tian@intel.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.