From: Martin Waitz <tali@admingilde.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
Gerd Knorr <kraxel@bytesex.org>,
linux-fbdev-devel@lists.sourceforge.net,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
penguinppc-team@lists.penguinppc.org
Subject: Re: [Linux-fbdev-devel] Generic VESA framebuffer driver and Video card BOOT?
Date: Tue, 19 Oct 2004 18:57:20 +0200 [thread overview]
Message-ID: <20041019165720.GF3618@admingilde.org> (raw)
In-Reply-To: <200410182242.04749.oliver@neukum.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Mon, Oct 18, 2004 at 10:42:04PM +0200, Oliver Neukum wrote:
> Am Montag, 18. Oktober 2004 22:21 schrieb Helge Hafting:
> > > On first access only, and even that only if the driver doesn't map the
> > > pages at mmap() time already. ?Not a single fb driver seems to map the
> > > pages lazy today, grepping in drivers/video for nopage handles shows
> > > nothing. ?I'm not sure you can actually do that for iomem mappings.
> > >
> > Isn't it possible for the driver to unmap the mapping when
> > suspending? ?Then you're guaranteed to get that first access.
>
> But what would you do then? Block everything that is using a terminal?
yes
but that wouldn't last long if you run the userspace helper as soon
as you are finished resuming.
One 'only' needs a method to give feedback while loading the image...
I guess we have to rely on the firmware here.
(Eighter it already sets an useable mode or provides a function that
can display test)
--
Martin Waitz
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-19 16:57 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 19:02 Generic VESA framebuffer driver and Video card BOOT? Kendall Bennett
2004-10-14 19:59 ` Zachary Smith
2004-10-15 23:36 ` Ian Romanick
2004-10-14 20:48 ` Zachary Smith
2004-10-15 18:05 ` Kendall Bennett
2004-10-15 18:55 ` Zachary Smith
2004-10-15 19:18 ` Geert Uytterhoeven
2004-10-15 22:22 ` Kendall Bennett
2004-10-15 0:27 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-15 0:27 ` Antonino A. Daplas
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-15 23:20 ` Jon Smirl
2004-10-15 23:51 ` Kendall Bennett
2004-10-15 23:58 ` Jon Smirl
2004-10-19 21:15 ` Pavel Machek
2004-10-16 1:50 ` Antonino A. Daplas
2004-10-16 1:50 ` Antonino A. Daplas
2004-10-16 2:03 ` Jon Smirl
2004-10-18 19:34 ` Kendall Bennett
2004-10-18 19:34 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-18 20:34 ` Richard Smith
2004-10-18 20:34 ` [Linux-fbdev-devel] " Richard Smith
2004-10-18 20:47 ` Kendall Bennett
2004-10-18 21:04 ` Richard Smith
2004-10-18 21:16 ` Jon Smirl
2004-10-18 22:34 ` Richard Smith
2004-10-18 22:34 ` [Linux-fbdev-devel] " Richard Smith
2004-10-18 23:28 ` Jon Smirl
2004-10-19 0:18 ` Richard Smith
2004-10-19 0:18 ` [Linux-fbdev-devel] " Richard Smith
2004-10-19 0:55 ` Kendall Bennett
2004-10-19 1:39 ` Richard Smith
2004-10-19 1:39 ` [Linux-fbdev-devel] " Richard Smith
2004-10-19 17:54 ` Kendall Bennett
2004-10-19 17:54 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:48 ` Pavel Machek
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 17:01 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 19:08 ` Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-21 19:36 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:42 ` Pavel Machek
2004-10-15 12:05 ` Gerd Knorr
2004-10-15 12:38 ` Geert Uytterhoeven
2004-10-15 12:45 ` Alan Cox
2004-10-19 21:54 ` Pavel Machek
2004-10-15 13:13 ` Gerd Knorr
2004-10-17 12:07 ` Martin Waitz
2004-10-18 8:36 ` Gerd Knorr
2004-10-18 8:36 ` [Linux-fbdev-devel] " Gerd Knorr
2004-10-18 11:39 ` Martin Waitz
2004-10-18 12:10 ` Gerd Knorr
2004-10-18 12:10 ` [Linux-fbdev-devel] " Gerd Knorr
2004-10-18 20:21 ` Helge Hafting
2004-10-18 20:42 ` Oliver Neukum
2004-10-19 16:57 ` Martin Waitz [this message]
2004-10-15 18:29 ` Venkatesh Pallipadi
2004-10-16 9:01 ` Nigel Cunningham
2004-10-16 9:01 ` [Linux-fbdev-devel] " Nigel Cunningham
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 13:48 ` Helge Hafting
2004-10-15 13:48 ` Helge Hafting
2004-10-15 18:36 ` Kendall Bennett
2004-10-15 21:44 ` Helge Hafting
2004-10-15 22:12 ` Kendall Bennett
2004-10-16 0:41 ` [Linux-fbdev-devel] " Antonino A. Daplas
2004-10-16 0:41 ` Antonino A. Daplas
2004-10-26 11:14 ` Paulo Marques
2004-10-26 11:14 ` Paulo Marques
2004-10-27 1:58 ` Kendall Bennett
2004-10-27 11:11 ` Paulo Marques
2004-10-27 19:52 ` Kendall Bennett
2004-10-27 19:52 ` Kendall Bennett
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-15 21:51 ` Antonino A. Daplas
2004-10-16 17:44 ` Jon Smirl
2004-10-16 17:44 ` Jon Smirl
2004-10-18 19:34 ` Kendall Bennett
2004-10-18 19:34 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-19 21:00 ` Pavel Machek
2004-10-19 21:11 ` Pavel Machek
2004-10-20 17:01 ` Kendall Bennett
2004-10-20 17:01 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 17:31 ` Pavel Machek
2004-10-20 18:44 ` Kendall Bennett
2004-10-20 18:44 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-20 19:10 ` Pavel Machek
2004-10-21 19:36 ` Kendall Bennett
2004-10-21 19:36 ` [Linux-fbdev-devel] " Kendall Bennett
2004-10-21 20:47 ` Richard Smith
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=20041019165720.GF3618@admingilde.org \
--to=tali@admingilde.org \
--cc=helgehaf@aitel.hist.no \
--cc=kraxel@bytesex.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=penguinppc-team@lists.penguinppc.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 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.