public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Akinobu Mita <akinobu.mita@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com
Subject: Re: [PATCH] x86: fix usage of bios intcall()
Date: Sat, 4 Jul 2009 11:14:13 +0900	[thread overview]
Message-ID: <20090704021410.GA3050@localhost.localdomain> (raw)
In-Reply-To: <20090701021307.GA3127@localhost.localdomain>

Could someone review this patch?

On Wed, Jul 01, 2009 at 11:13:07AM +0900, Akinobu Mita wrote:
> Some intcall() misuses the input biosregs as output in
> cf06de7b9cdd3efee7a59dced1977b3c21d43732
> 
> This fixes the problem vga=ask boot option doesn't show enough modes.
> 
> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
> ---
>  arch/x86/boot/video-bios.c |    3 +--
>  arch/x86/boot/video-vesa.c |    4 ++--
>  2 files changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/x86/boot/video-bios.c b/arch/x86/boot/video-bios.c
> index d660be4..49e0c18 100644
> --- a/arch/x86/boot/video-bios.c
> +++ b/arch/x86/boot/video-bios.c
> @@ -37,14 +37,13 @@ static int set_bios_mode(u8 mode)
>  	ireg.al = mode;		/* AH=0x00 Set Video Mode */
>  	intcall(0x10, &ireg, NULL);
>  
> -
>  	ireg.ah = 0x0f;		/* Get Current Video Mode */
>  	intcall(0x10, &ireg, &oreg);
>  
>  	do_restore = 1;		/* Assume video contents were lost */
>  
>  	/* Not all BIOSes are clean with the top bit */
> -	new_mode = ireg.al & 0x7f;
> +	new_mode = oreg.al & 0x7f;
>  
>  	if (new_mode == mode)
>  		return 0;	/* Mode change OK */
> diff --git a/arch/x86/boot/video-vesa.c b/arch/x86/boot/video-vesa.c
> index c700147..275dd17 100644
> --- a/arch/x86/boot/video-vesa.c
> +++ b/arch/x86/boot/video-vesa.c
> @@ -45,7 +45,7 @@ static int vesa_probe(void)
>  	ireg.di = (size_t)&vginfo;
>  	intcall(0x10, &ireg, &oreg);
>  
> -	if (ireg.ax != 0x004f ||
> +	if (oreg.ax != 0x004f ||
>  	    vginfo.signature != VESA_MAGIC ||
>  	    vginfo.version < 0x0102)
>  		return 0;	/* Not present */
> @@ -70,7 +70,7 @@ static int vesa_probe(void)
>  		ireg.di = (size_t)&vminfo;
>  		intcall(0x10, &ireg, &oreg);
>  
> -		if (ireg.ax != 0x004f)
> +		if (oreg.ax != 0x004f)
>  			continue;
>  
>  		if ((vminfo.mode_attr & 0x15) == 0x05) {

  reply	other threads:[~2009-07-04  2:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  2:13 [PATCH] x86: fix usage of bios intcall() Akinobu Mita
2009-07-04  2:14 ` Akinobu Mita [this message]
2009-07-04 20:07 ` [tip:x86/urgent] " tip-bot for Akinobu Mita

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=20090704021410.GA3050@localhost.localdomain \
    --to=akinobu.mita@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox