From: "H. Peter Anvin" <hpa@zytor.com>
To: Guenter Roeck <guenter.roeck@ericsson.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"penberg@cs.helsinki.fi" <penberg@cs.helsinki.fi>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: [PATCH][RESEND] x86: Do not write to VGA memory space if CONFIG_VGA_CONSOLE is undefined
Date: Mon, 19 Apr 2010 20:55:35 -0700 [thread overview]
Message-ID: <4BCD25B7.2020102@zytor.com> (raw)
In-Reply-To: <20100420022110.GA20116@ericsson.com>
On 04/19/2010 07:21 PM, Guenter Roeck wrote:
> On Mon, Apr 19, 2010 at 05:02:25PM -0400, H. Peter Anvin wrote:
>> Hi Guenter,
>>
>> I wanted to check where we are at... at the very least we should drop
>> messages issued before initialization when isVGA != 1.
>>
>> Since serial ports require initialization, I really don't want to send
>> messages to the serial port before the port has been initialized, but
>> obviously it would be good to initialize earlyprintk as early as at all
>> possible.
>>
> Moving setup_early_printk() around may be possible, but I do not know
> the code good enough to take that risk. Even trying was a bad idea.
>
> I could submit a patch to add some protection into early_printk(),
> to ensure it does not write into VGA memory space if there is no VGA,
> and do that without changing current semantics - specifically, still
> write into VGA memory space even if setup_early_printk() was not called
> yet, but if boot_params.screen_info.orig_video_isVGA is set.
>
> I thought you indicated that you are opposed to changing the code,
> and it looks kind of clumsy, so I concluded that it was not worth
> trying again. Maybe I misunderstood - let me know.
>
> Guenter
I think writing into VGA memory if we know there is a VGA device is
there. I don't want to write to an uninitialized serial port, because
that can cause all kinds of problems.
But yes, dropping output to VGA if there isn't one makes a lot of sense.
-hpa
next prev parent reply other threads:[~2010-04-20 4:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 14:41 [PATCH][RESEND] x86: Do not write to VGA memory space if CONFIG_VGA_CONSOLE is undefined Guenter Roeck
2010-03-31 15:32 ` Pekka Enberg
2010-04-05 18:10 ` Guenter Roeck
2010-04-05 18:46 ` H. Peter Anvin
2010-04-05 20:02 ` Guenter Roeck
2010-04-05 20:25 ` H. Peter Anvin
2010-04-05 21:04 ` Guenter Roeck
2010-04-05 21:11 ` H. Peter Anvin
2010-04-05 21:15 ` H. Peter Anvin
2010-04-05 22:12 ` Guenter Roeck
2010-04-06 20:17 ` H. Peter Anvin
2010-04-06 20:37 ` Guenter Roeck
2010-04-19 21:02 ` H. Peter Anvin
2010-04-20 2:21 ` Guenter Roeck
2010-04-20 3:55 ` H. Peter Anvin [this message]
2010-03-31 18:31 ` H. Peter Anvin
2010-03-31 19:08 ` Guenter Roeck
2010-03-31 20:05 ` Guenter Roeck
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=4BCD25B7.2020102@zytor.com \
--to=hpa@zytor.com \
--cc=guenter.roeck@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@cs.helsinki.fi \
--cc=x86@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