From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] full suspend/resume support for i915 DRM driver
Date: Wed, 24 Oct 2007 14:07:08 -0700 [thread overview]
Message-ID: <200710241407.08792.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20071024201712.GH30533@stusta.de>
On Wednesday, October 24, 2007 1:17 pm Adrian Bunk wrote:
> > diff --git a/linux-core/Kconfig b/linux-core/Kconfig
> > index 2d02c76..5e73fc7 100644
> > --- a/linux-core/Kconfig
> > +++ b/linux-core/Kconfig
> > @@ -50,7 +50,7 @@ config DRM_I810
> >
> > choice
> > prompt "Intel 830M, 845G, 852GM, 855GM, 865G"
> > - depends on DRM && AGP && AGP_INTEL
> > + depends on DRM && AGP && AGP_INTEL && !FB_INTEL
> > optional
> >...
>
> This sounds like a bad regression.
Well it's really documenting existing behavior. Unless you're very
careful, running custom applications, the Intel FB and DRM drivers will
conflict. IMO this is a long overdue change, but Dave has some custom
stuff that requires both drivers so he'd rather not see it go in, so
I'm fine with dropping this part.
Jesse
next prev parent reply other threads:[~2007-10-24 21:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 21:01 [RFC] full suspend/resume support for i915 DRM driver Jesse Barnes
2007-10-20 2:51 ` Jesse Barnes
2007-10-23 4:15 ` Jesse Barnes
2007-10-24 20:17 ` Adrian Bunk
2007-10-24 21:07 ` Jesse Barnes [this message]
2007-10-24 13:35 ` Pavel Machek
2007-10-24 15:18 ` Jesse Barnes
2007-10-24 21:22 ` Rafael J. Wysocki
2007-10-25 23:53 ` Jesse Barnes
2007-10-26 4:59 ` Greg KH
2007-10-26 16:57 ` Jesse Barnes
2007-10-26 17:10 ` Kay Sievers
2007-10-26 18:12 ` Jesse Barnes
2007-10-26 18:21 ` Kay Sievers
2007-10-26 18:40 ` fixing up DRM device model usage Jesse Barnes
2007-10-26 19:08 ` Kay Sievers
2007-10-26 21:31 ` Jesse Barnes
2007-10-27 21:12 ` Kay Sievers
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=200710241407.08792.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=bunk@kernel.org \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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