From: Jon Smirl <jonsmirl@gmail.com>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: 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 10:56:48 -0500 [thread overview]
Message-ID: <9e47339105021907561c4f408c@mail.gmail.com> (raw)
In-Reply-To: <E1D2TjV-0007r9-00@chiark.greenend.org.uk>
On Sat, 19 Feb 2005 12:29:13 +0000, Matthew Garrett
<mgarrett@chiark.greenend.org.uk> wrote:
> Jon Smirl <jonsmirl@gmail.com> wrote:
>
> > For example I'm looking at making changes to DRM such that DRM will
> > require the corresponding framebuffer driver to be loaded. If you back
> > up further this is part of fixing X so that it won't mess with the
> > hardware from user space. Mode setting would come from the framebuffer
> > driver instead of the X 2D XAA driver.
>
> Please don't until all the framebuffer drivers are able to deal with
> suspend and resume (which will also require some mechanism to switch
> backlights back on). Currently, it's far easier to restore some amount
> of state on a standard VGA or VESA mode. There's no real support for
> doing so with most accelerated framebuffers.
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.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Jon Smirl <jonsmirl@gmail.com>
To: Matthew Garrett <mgarrett@chiark.greenend.org.uk>
Cc: 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 10:56:48 -0500 [thread overview]
Message-ID: <9e47339105021907561c4f408c@mail.gmail.com> (raw)
In-Reply-To: <E1D2TjV-0007r9-00@chiark.greenend.org.uk>
On Sat, 19 Feb 2005 12:29:13 +0000, Matthew Garrett
<mgarrett@chiark.greenend.org.uk> wrote:
> Jon Smirl <jonsmirl@gmail.com> wrote:
>
> > For example I'm looking at making changes to DRM such that DRM will
> > require the corresponding framebuffer driver to be loaded. If you back
> > up further this is part of fixing X so that it won't mess with the
> > hardware from user space. Mode setting would come from the framebuffer
> > driver instead of the X 2D XAA driver.
>
> Please don't until all the framebuffer drivers are able to deal with
> suspend and resume (which will also require some mechanism to switch
> backlights back on). Currently, it's far easier to restore some amount
> of state on a standard VGA or VESA mode. There's no real support for
> doing so with most accelerated framebuffers.
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.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-02-19 15:56 UTC|newest]
Thread overview: 14+ 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 21:14 ` Jon Smirl
2005-02-18 22:58 ` Michel Dänzer
2005-02-18 22:58 ` [Linux-fbdev-devel] " Michel Dänzer
2005-02-18 23:35 ` Jon Smirl
2005-02-18 23:35 ` [Linux-fbdev-devel] " Jon Smirl
2005-02-19 12:29 ` Matthew Garrett
2005-02-19 15:56 ` Jon Smirl [this message]
2005-02-19 15:56 ` Jon Smirl
2005-02-19 16:51 ` Matthew Garrett
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=9e47339105021907561c4f408c@mail.gmail.com \
--to=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 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.