mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Eric Anholt <eric@anholt.net>
Cc: Alessandro Suardi <alessandro.suardi@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.28-git3 and i915 Kconfig new dependency on framebuffer
Date: Sat, 3 Jan 2009 00:02:15 +0100	[thread overview]
Message-ID: <20090102230215.GA9184@uranus.ravnborg.org> (raw)
In-Reply-To: <1230936608.6095.2.camel@gaiman.anholt.net>

On Fri, Jan 02, 2009 at 02:50:08PM -0800, Eric Anholt wrote:
> On Wed, 2008-12-31 at 19:55 +0100, Alessandro Suardi wrote:
> > make oldconfig from -git2 to -git3 doesn't build i915.ko unless
> >  one has CONFIG_FB enabled; this causes /dev/dri/card0 to
> >  be missing, and DRI disabled from within X.
> > 
> > Do I now (2.6.28-git3+) need CONFIG_FB to enable i915 DRM ?
> 
> Yes, the i915 driver now relies on fb code, though the new features are
> runtime optional.  I may have noviced the Kconfig bits -- my intention
> was "If you select I915, you also get all the CONFIG_FB-related bits
> necessary".
> 
> config DRM_I915
>         select FB_CFB_FILLRECT
>         select FB_CFB_COPYAREA
>         select FB_CFB_IMAGEBLIT
>         depends on FB
>         tristate "i915 driver"
> 
> I'm guessing that that "depends on FB" wants to be "select FB".

No - that would not fly...
You somehow need to educate the people that want to enable DRM_I915 that
they cannot do so before they enable framebuffer support.

When you consider using select on a symbol that has a prompt
you have a good sign that you do something wrong.

	Sam

      reply	other threads:[~2009-01-02 23:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 18:55 Alessandro Suardi
2009-01-02 22:50 ` Eric Anholt
2009-01-02 23:02   ` Sam Ravnborg [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=20090102230215.GA9184@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=alessandro.suardi@gmail.com \
    --cc=eric@anholt.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

all inboxes | Powered by JetHome®