From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: adaplas@pol.net
Cc: James Simmons <jsimmons@infradead.org>,
Andrew Morton <akpm@osdl.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 3/3] [FBDEV]: Hardware State Notification
Date: Wed, 23 Jun 2004 21:35:49 -0500 [thread overview]
Message-ID: <1088044547.1855.185.camel@gaston> (raw)
In-Reply-To: <200406240750.28126.adaplas@hotpop.com>
On Wed, 2004-06-23 at 18:50, Antonino A. Daplas wrote:
> Thanks Ben, I see it now. I did not realize it was in the console_blank hook. (I did
> not follow this list for a time). And no, I don't think you missed a code path. The
> problem is that we are calling fb_set_var->set_par too early, before X has really
> given up on the hardware. We can fix this by setting some kind of flag while in
> fbcon_blank, and depending on the setting of this flag, force a set_par in
> fbcon_switch instead.
>
> I'll concoct a patch later. (I'll test James' new patch first).
That would be a bug in X
If console switching, the 'unblank' is done, afaik, after X calls the ioctl
to relinguish the console to the kernel.
When exiting X, I'm not sure, but that should be similar. If X still touches
the HW after that, it's an X bug (and yes, I does that, at least in the radeon
driver, afaik)
Ben.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next prev parent reply other threads:[~2004-06-24 2:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 22:39 [PATCH 3/3] [FBDEV]: Hardware State Notification Antonino A. Daplas
2004-06-21 22:51 ` Antonino A. Daplas
2004-06-23 16:02 ` Benjamin Herrenschmidt
2004-06-23 23:50 ` Antonino A. Daplas
2004-06-24 2:35 ` Benjamin Herrenschmidt [this message]
2004-06-24 20:46 ` Antonino A. Daplas
2004-06-28 22:09 ` Benjamin Herrenschmidt
2004-06-28 22:48 ` Antonino A. Daplas
2004-06-29 0:55 ` 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=1088044547.1855.185.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).