From: Jeremy Fitzhardinge <jeremy@goop.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 11:54:57 -0800 [thread overview]
Message-ID: <42179991.6090808@goop.org> (raw)
In-Reply-To: <9e47339105021907561c4f408c@mail.gmail.com>
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.
>
Only if you want to see the output, surely? I have an application which
doesn't need a framebuffer (or more strictly, scan-out), but does use DRM.
J
next prev parent reply other threads:[~2005-02-19 19:54 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
2005-02-19 19:54 ` Jeremy Fitzhardinge [this message]
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=42179991.6090808@goop.org \
--to=jeremy@goop.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).