From: Tomas Carnecky <tom@dbservice.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: my opinion about VGA devices
Date: Wed, 20 Oct 2004 14:31:08 +0200 [thread overview]
Message-ID: <41765A8C.2020309@dbservice.com> (raw)
In-Reply-To: <200410201318.26430.oliver@neukum.org>
Oliver Neukum wrote:
> Am Mittwoch, 20. Oktober 2004 00:10 schrieb Tomas Carnecky:
>
>>I think this would make the suspend/resume/access/switching etc problems
>>much easier to solve since the kernel module could tell the library to
>>stop drawing/accessing mmap'ed memory etc. (or if the OpenGL rendering
>>is done in the kernel module it could just discard the render commands).
>>Since the user has no direct access to mmap'ed memory and other critical
>>sections of the device, the driver can implement proper power managment
>>for suspend/resume etc.
>>
>>Well... that's it.. any comments? I'm sure you have.. :)
>
>
> You are making damn sure that there will be no useful bug reports
> about problems with resuming from S3.
>
I guess that you are talking about the fact that displaying text
messages would be possible only after the first device driver has
initialized and registered with the kernel.
You could do the printing in two stages: at the begining the same way as
in the current kernel, but as soon as the first driver is registered,
the kernel switches to the function provided by the driver.
Something like this:
void print_message(...)
{
if (no_module_registered) {
use_print_function_provided_by_the_kernel();
} else {
if (!printing_disabled) {
use_print_function_provided_by_the_driver_module();
} else {
/* printing disabled by the userspace, we are not
* allowed to touch the hardware */
}
}
}
tom
next prev parent reply other threads:[~2004-10-20 12:36 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 [this message]
2004-10-20 12:56 ` Richard B. Johnson
2004-10-20 14:14 ` Tomas Carnecky
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=41765A8C.2020309@dbservice.com \
--to=tom@dbservice.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.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;
as well as URLs for NNTP newsgroup(s).