From: Kyle Moffett <mrmacman_g4@mac.com>
To: Dave Jones <davej@redhat.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@osdl.org>, David Airlie <airlied@linux.ie>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] DRM depends on ???
Date: Sun, 29 May 2005 00:25:10 -0400 [thread overview]
Message-ID: <1FA58BE7-0EE6-432B-9383-F489F9854DBE@mac.com> (raw)
In-Reply-To: <20050528215005.GA5990@redhat.com>
On May 28, 2005, at 17:50:05, Dave Jones wrote:
> On Sat, May 28, 2005 at 11:39:00PM +0200, Geert Uytterhoeven wrote:
>> config DRM
>> tristate "Direct Rendering Manager (XFree86 4.1.0 and higher
>> DRI support)"
>> - depends on AGP || AGP=n
>> + depends on (AGP || AGP=n) && PCI
>>
>
> The whole dependancy seems like nonsense to me.
> I think
>
> depends on PCI
>
> is a lot more sensible.
I think the original reasoning was something like this:
If DRM is built-in, then AGP _must_ be built-in or not included at
all, modular
won't work. If DRM is modular or not built, then AGP may be built-
in, modular,
or not built at all.
The "depends on AGP || AGP=n" means that if DRM=y, then AGP=y or
AGP=n, and if
DRM=m or DRM=n, then AGP=y or AGP=m or AGP=n.
Yes it's unclear and yes it should probably be documented in a
comment somewhere.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$
r !y?(-)
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2005-05-29 4:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 21:39 Geert Uytterhoeven
2005-05-28 21:50 ` Dave Jones
2005-05-29 4:25 ` Kyle Moffett [this message]
2005-05-29 7:11 ` Dave Airlie
2005-05-29 19:58 ` Geert Uytterhoeven
2005-05-29 23:00 ` Kyle Moffett
2005-05-30 8:03 ` Geert Uytterhoeven
2005-05-30 8:54 ` Dave Airlie
2005-05-30 9:12 ` Geert Uytterhoeven
2005-05-30 11:12 ` Helge Hafting
2005-05-30 11:19 ` Dave Airlie
2005-05-29 8:26 ` Christoph Hellwig
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=1FA58BE7-0EE6-432B-9383-F489F9854DBE@mac.com \
--to=mrmacman_g4@mac.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=geert@linux-m68k.org \
--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®