archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <>
To: James Simmons <>
Cc: linux-kernel mailing list <>,
	Linux Fbdev development list 
	Pavel Machek <>
Subject: Re: [Linux-fbdev-devel] [PATCH] Framebuffer: 2nd try: client notification mecanism & PM
Date: 07 Aug 2003 11:38:22 +0200	[thread overview]
Message-ID: <1060249101.1077.67.camel@gaston> (raw)
In-Reply-To: <>

On Thu, 2003-08-07 at 01:52, James Simmons wrote:
> > James, if you are ok, can you get that upstream to Linus asap so
> > I can start pushing the driver bits for radeon & aty128 ?
> Working on it. I'm thinking about also how it effects userland and how 
> userland affects the console if present. Basically the logic will go 
> pci suspend ->  framebuffer driver supend function -> call each client
> Just give me a few days to piece it together.

Right now, we don't have a proper userland notification. So far, the
main affected thing is XFree, but this is ok as it will have received
a suspend request via /dev/apm_bios (which we emulate on PowerMacs),
and so won't touch the framebuffer until resumed.

There isn't much we can do against a userland client tapping the
framebuffer that it mmap'ed previously. I don't know how feasible it
would be to sort of "hack" this process mapping on the fly (would
involve some nasty SMP synchronisation issues) so that the userland
process is just put to sleep on fb access while the fb is suspended
(or get a SEGV). We probably want to extend the notification mecanism
to userland in some way, but this isn't something i cover in this


  reply	other threads:[~2003-08-07  9:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29 13:13 [PATCH] Framebuffer: client notification mecanism & PM Benjamin Herrenschmidt
2003-07-29 17:49 ` Pavel Machek
2003-07-30 12:14   ` Benjamin Herrenschmidt
2003-07-30 13:10     ` [PATCH] Framebuffer: 2nd try: " Benjamin Herrenschmidt
2003-07-30 13:14     ` Benjamin Herrenschmidt
2003-08-01 10:04       ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-06 23:52         ` James Simmons
2003-08-07  9:38           ` Benjamin Herrenschmidt [this message]
2003-08-07 10:03             ` Pavel Machek
2003-08-07 13:32               ` Benjamin Herrenschmidt
2003-08-07 17:26                 ` James Simmons
2003-08-07 21:38                 ` Nigel Cunningham
2003-08-07 21:51                   ` Pavel Machek
2003-08-07 14:37               ` Benjamin Herrenschmidt
2003-08-07 17:28                 ` James Simmons
2003-08-07 20:29                 ` Pavel Machek
2003-08-07 17:23               ` James Simmons
2003-08-07 20:29                 ` Pavel Machek

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1060249101.1077.67.camel@gaston \ \ \ \ \ \

* 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).