From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Hotplug blacklist and video devices
Date: Sat, 19 Feb 2005 16:51:01 +0000 [thread overview]
Message-ID: <1108831861.4085.172.camel@tyrosine> (raw)
In-Reply-To: <9e47339105021907561c4f408c@mail.gmail.com>
On Sat, 2005-02-19 at 10:56 -0500, Jon Smirl wrote:
> I didn't say make framebuffer depend on DRM, you can still unload DRM
> before suspend. It's the other way around DRM needs framebuffer.
> Suspend/resume are part of this. In the current model there is no way
> for the DRM driver to see the suspend/resume events. I haven't tried
> it but I suspect a suspend/resume with DRM running has a bad outcome
> right now.
Right. But for most machines, it's not possible to successfully resume
if an accelerated framebuffer driver is loaded. Until that's fixed,
tying DRM functionality to the framebuffer will make it impractical to
use DRM on laptops. That's a regression from the current situation.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2005-02-19 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 20:51 Hotplug blacklist and video devices Jon Smirl
2005-02-18 21:08 ` Bill Nottingham
2005-02-18 21:14 ` Jon Smirl
2005-02-18 22:58 ` Michel Dänzer
2005-02-18 23:35 ` Jon Smirl
2005-02-19 12:29 ` Matthew Garrett
2005-02-19 15:56 ` Jon Smirl
2005-02-19 16:51 ` Matthew Garrett [this message]
2005-02-19 19:54 ` Jeremy Fitzhardinge
2005-02-21 19:08 ` Bill Nottingham
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=1108831861.4085.172.camel@tyrosine \
--to=mjg59@srcf.ucam.org \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgarrett@chiark.greenend.org.uk \
/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).