From: Dave Airlie <airlied@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
airlied@linux.ie, linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] fb/intelfb: conflict with DRM_I915 and hide by default
Date: Sat, 18 Jul 2009 13:34:34 +1000 [thread overview]
Message-ID: <21d7e9970907172034x40cbc65emb627ebc58b91a483@mail.gmail.com> (raw)
In-Reply-To: <20090717182212.4675d0e1@jbarnes-g45>
On Sat, Jul 18, 2009 at 11:22 AM, Jesse Barnes<jbarnes@virtuousgeek.org> wrote:
> On Fri, 17 Jul 2009 17:13:26 -0700
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> On Fri, 3 Jul 2009 11:24:46 -0700
>> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>>
>> > Users get confused by this driver. It's really a special purpose
>> > embedded driver, and causes a lot of problems if enabled. So hide
>> > it under EMBEDDED by default, and make sure it doesn't get enabled
>> > with the i915 DRM driver.
>> >
>> > Dave, I'm hoping you can feed this to Linus through your tree. It's
>> > appropriate for 2.6.31 I think.
>> >
>> > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>> >
>> > diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
>> > index d6d65ef..ec12f7a 100644
>> > --- a/drivers/video/Kconfig
>> > +++ b/drivers/video/Kconfig
>> > @@ -1117,12 +1117,13 @@ config FB_CARILLO_RANCH
>> >
>> > config FB_INTEL
>> > tristate "Intel
>> > 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support
>> > (EXPERIMENTAL)"
>> > - depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL
>> > + depends on EXPERIMENTAL && FB && PCI && X86 && AGP_INTEL
>> > && EMBEDDED select FB_MODE_HELPERS
>> > select FB_CFB_FILLRECT
>> > select FB_CFB_COPYAREA
>> > select FB_CFB_IMAGEBLIT
>> > select FB_BOOT_VESA_SUPPORT if FB_INTEL = y
>> > + depends on !DRM_I915
>> > help
>> > This driver supports the on-board graphics built in to
>> > the Intel
>> > 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM/965G/965GM
>> > chipsets.
>>
>> Nothing happened?
>>
>> I'll merge this next week(ish) unless given a reason not to.
>
> It's in Dave's tree, pull requested to Linus already, so it should land
> soon.
>
I suspect Linus isn't pulling from me post -rc2 anymore, or maybe
he just missed it.
Dave.
prev parent reply other threads:[~2009-07-18 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 18:24 Jesse Barnes
2009-07-18 0:13 ` Andrew Morton
2009-07-18 1:22 ` Jesse Barnes
2009-07-18 3:34 ` Dave Airlie [this message]
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=21d7e9970907172034x40cbc65emb627ebc58b91a483@mail.gmail.com \
--to=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®