From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Framebuffer: client notification mecanism & PM
Date: Tue, 29 Jul 2003 19:49:19 +0200 [thread overview]
Message-ID: <20030729174919.GC2601@openzaurus.ucw.cz> (raw)
In-Reply-To: <1059484419.8537.19.camel@gaston>
Hi!
> There is room for improvement, but this is a first step that makes
> suspend/resume work more reliably on pmacs. I'll send aty128fb and
> radeonfb bits using this framework once it's merged.
> @@ -199,7 +199,8 @@
> if (!info || (info->cursor.rop == ROP_COPY))
> return;
> info->cursor.enable ^= 1;
> - info->fbops->fb_cursor(info, &info->cursor);
> + if (!info->suspended)
> + info->fbops->fb_cursor(info, &info->cursor);
> }
>
> y_break = p->vrows - p->yscroll;
Would not it be simpler to replace info->fbops with some dummy ones?
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...
next prev parent reply other threads:[~2003-07-30 6:28 UTC|newest]
Thread overview: 38+ 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 [this message]
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-07-30 13:14 ` Benjamin Herrenschmidt
2003-08-01 10:04 ` Benjamin Herrenschmidt
2003-08-01 10:04 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-06 23:52 ` James Simmons
2003-08-06 23:52 ` [Linux-fbdev-devel] " James Simmons
2003-08-07 9:38 ` Benjamin Herrenschmidt
2003-08-07 9:38 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-07 10:03 ` Pavel Machek
2003-08-07 10:03 ` [Linux-fbdev-devel] " Pavel Machek
2003-08-07 13:32 ` Benjamin Herrenschmidt
2003-08-07 13:32 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-07 17:26 ` James Simmons
2003-08-07 21:38 ` Nigel Cunningham
2003-08-07 21:38 ` [Linux-fbdev-devel] " Nigel Cunningham
2003-08-07 21:51 ` Pavel Machek
2003-08-07 21:51 ` [Linux-fbdev-devel] " Pavel Machek
2003-08-07 14:37 ` Benjamin Herrenschmidt
2003-08-07 14:37 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2003-08-07 17:28 ` James Simmons
2003-08-07 17:28 ` [Linux-fbdev-devel] " James Simmons
2003-08-07 20:29 ` Pavel Machek
2003-08-07 17:23 ` James Simmons
2003-08-07 20:29 ` Pavel Machek
2003-08-07 20:29 ` [Linux-fbdev-devel] " Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 13:39 [PATCH] Framebuffer: " Petr Vandrovec
2003-07-29 13:59 ` Benjamin Herrenschmidt
2003-07-29 16:55 ` James Simmons
2003-07-29 16:55 ` James Simmons
2003-07-29 20:22 ` Benjamin Herrenschmidt
2003-07-29 21:31 ` James Simmons
2003-07-29 21:31 ` James Simmons
2003-07-30 12:22 ` Benjamin Herrenschmidt
2003-07-30 12:22 ` Benjamin Herrenschmidt
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=20030729174919.GC2601@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.