From: "H. Peter Anvin" <hpa@linux.intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "Glove box" BIOS patch causes boot flicker
Date: Thu, 23 Sep 2010 13:51:41 -0700 [thread overview]
Message-ID: <4C9BBDDD.6050803@linux.intel.com> (raw)
In-Reply-To: <4C9BBD0C.6070905@zytor.com>
On 09/23/2010 01:48 PM, H. Peter Anvin wrote:
> On 09/23/2010 01:46 PM, Jan Engelhardt wrote:
>>
>> On Thursday 2010-09-23 22:00, H. Peter Anvin wrote:
>>> On 09/23/2010 11:54 AM, Jan Engelhardt wrote:
>>>> On Wednesday 2010-09-22 02:34, H. Peter Anvin wrote:
>>>>
>>>>> There were some minor bugs (typos) in the conversion to the glove box
>>>>> coding style. The ones we have found have been fixed, so the first
>>>>> thing is to try the current mainline or the current tip tree.
>>>>> Otherwise I would look for issues where either the wrong register is
>>>>> changed, or something like a variable is changed instead of a field.
>>>>
>>>> I tried v2.6.36-rc5 now, and it looks better. The cursor position is
>>>> retained as desired. The mode switch is still there, albeit much
>>>> shorter than it used to be.
>>>
>>> The mode switch was there in the original code.
>>
>> That may very well be so, but there clearly is distinguished behavior
>> w.r.t. that in 2.6.36 compared to .30.
>
> Yes, but that caused regressions from the old assembly code.
>
By the way, if you don't want a mode reset, use "vga=current".
-hpa
prev parent reply other threads:[~2010-09-23 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 23:53 "Glove box" BIOS patch causes boot flicker Jan Engelhardt
2010-09-22 0:34 ` H. Peter Anvin
2010-09-23 18:54 ` Jan Engelhardt
2010-09-23 20:00 ` H. Peter Anvin
2010-09-23 20:46 ` Jan Engelhardt
2010-09-23 20:48 ` H. Peter Anvin
2010-09-23 20:51 ` H. Peter Anvin [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=4C9BBDDD.6050803@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
/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