All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomas Carnecky <tom@dbservice.com>
To: root@chaos.analogic.com
Cc: Oliver Neukum <oliver@neukum.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: my opinion about VGA devices
Date: Wed, 20 Oct 2004 16:14:23 +0200	[thread overview]
Message-ID: <417672BF.5040708@dbservice.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410200851080.10711@chaos.analogic.com>

Richard B. Johnson wrote:

> On ix86 machines, regardless of whatever code initialized the
> hardware, if the screen-card is not put into graphics mode,
> anybody can write characters and attributes at 0xb8000 directly
> to the screen. Even user-mode code can mmap() that area and write
> to it. So, the key seems to be to get out of graphics mode
> before suspend, and go back later after resume.

Why do you let user-mode programs access the hardware directly?
You don't do this with network devices (there you have syscalls), you 
don't do this with sound devices (alsa).
IMO it makes a proper power managment implementation impossible.

You can say that there are two different drivers for screen-cards in the 
kernel. One is the VGA which enables the card during early boot time to 
display the first text messages and the other is fb/DRI or even an 
nvidia/ati kernel module which is enabled later on.
Last time I've tried a LiveCD distro I've seen a nice boot console with 
background picture, high resolution (1024x768) and nice small font. That 
means that the framebuffer driver had to be initialized at that time. I 
don't have framebuffer drivers compiled into my kernel so I don't know 
at which point these are initialized, but it must be at a quite early 
point in the boot process.
When looking at the output of dmesg I can see that the first thing that 
is initialized are the CPU's, ACPI, IRQ's and then the PCI bus is 
scanned. Did anyones machine crash during these steps? I don't think a 
healthy box will crash here. And at this point you can initialize your 
graphics card driver like it is done in the LiveCD distro.

tom

  reply	other threads:[~2004-10-22  4:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19 22:10 my opinion about VGA devices Tomas Carnecky
2004-10-20 11:18 ` Oliver Neukum
2004-10-20 12:31   ` Tomas Carnecky
2004-10-20 12:56     ` Richard B. Johnson
2004-10-20 14:14       ` Tomas Carnecky [this message]
2004-10-20 14:34         ` Richard B. Johnson
2004-10-20 15:01           ` Tomas Carnecky
2004-10-20 16:58             ` Matthew Garrett
     [not found]             ` <4178F276.2040501@globalintech.pl>
2004-10-22 11:58               ` Tomas carnecky
2004-10-22 19:13         ` Geert Uytterhoeven
2004-10-20 20:16     ` Oliver Neukum
2004-10-20 17:27 ` Kendall Bennett
2004-10-22  8:29   ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2004-10-19 18:51 Tomas Carnecky
2004-10-23 16:11 ` Blizbor

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=417672BF.5040708@dbservice.com \
    --to=tom@dbservice.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=root@chaos.analogic.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.