From: Dave Jones <davej@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] Kconfig cleanups
Date: Thu, 15 Jan 2004 00:20:44 +0000 [thread overview]
Message-ID: <20040115002044.GH8468@redhat.com> (raw)
In-Reply-To: <20040114065742.GG10711@parcelfarce.linux.theplanet.co.uk>
On Wed, Jan 14, 2004 at 10:48:09PM +0000, Matthew Wilcox wrote:
> On Wed, Jan 14, 2004 at 10:05:58PM +0100, Adrian Bunk wrote:
> > On Wed, Jan 14, 2004 at 06:57:42AM +0000, Matthew Wilcox wrote:
> > >...
> > > --- drivers/char/drm/Kconfig 28 Sep 2003 04:05:17 -0000 1.3
> > > +++ drivers/char/drm/Kconfig 14 Jan 2004 06:44:45 -0000
> > > @@ -6,6 +6,7 @@
> > > #
> > > config DRM
> > > bool "Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)"
> > > + depends on PCI
> > > help
> > > Kernel-level support for the Direct Rendering Infrastructure (DRI)
> > > introduced in XFree86 4.0. If you say Y here, you need to select
> > > @@ -17,21 +18,21 @@ config DRM
> > >
> > > config DRM_TDFX
> > > tristate "3dfx Banshee/Voodoo3+"
> > > - depends on DRM
> > > + depends on DRM && PCI
> > > help
> > > Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
> > > graphics card. If M is selected, the module will be called tdfx.
> > >
> > >...
> >
> >
> > If you let DRM depend on PCI, everything depending on DRM already has an
> > implicit dependency on PCI.
>
>
> That's true. However, there's nothing *intrinsic* about DRM that depends on
> PCI. There's no reason that someone shouldn't do a DRM module for an SBUS
> or GSC card. When one exists, the menu should depend on (PCI || SBUS).
Sparc64 has a DRM module for Creator3D, which I *think* is SBUS.
Yes, Sparc* has to be different and put its DRM Kconfig stuff
in arch/sparc64/Kconfig instead.
Dave
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-01-15 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 6:57 [Kernel-janitors] Kconfig cleanups Matthew Wilcox
2004-01-14 19:46 ` Greg KH
2004-01-14 21:05 ` Adrian Bunk
2004-01-14 22:48 ` Matthew Wilcox
2004-01-15 0:20 ` Dave Jones [this message]
2004-01-15 4:24 ` Matthew Wilcox
2004-01-15 11:41 ` Adrian Bunk
2004-01-23 0:36 ` Bjorn Helgaas
2004-01-23 0:36 ` Bjorn Helgaas
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=20040115002044.GH8468@redhat.com \
--to=davej@redhat.com \
--cc=kernel-janitors@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 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.