From: Keith Owens <kaos@ocs.com.au>
To: Stephen Torri <storri@ameritech.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, alan@lxorguk.ukuu.org.uk
Subject: Re: 2.4.9-ac15 (double entries for DRI cards)
Date: Thu, 27 Sep 2001 12:16:42 +1000 [thread overview]
Message-ID: <8203.1001557002@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 26 Sep 2001 13:48:26 -0400." <Pine.LNX.4.33.0109261340560.1820-100000@base.torri.linux>
On Wed, 26 Sep 2001 13:48:26 -0400 (EDT),
Stephen Torri <storri@ameritech.net> wrote:
>In "Character Devices" when configuring the kernel using xconfig there are
>double entries for video cards under Direct Rendering Manager. The
>following cards are reported twice:
>
>3dfx Banshee/Voodoo3+
>3dlabs GMX 2000
>ATI Rage 128
>ATI Radeon
>Intel I810
>Matrox G200/G400/G450
>
>They menu is correct when doing menuconfig. They are only reported once.
That is normal with xconfig, it displays all possible options and greys
out the ones that you cannot select. Trivial patch to make it more
obvious what is going on, against 2.4.9-ac15.
Index: 9.42/drivers/char/Config.in
--- 9.42/drivers/char/Config.in Sat, 22 Sep 2001 14:41:20 +1000 kaos (linux-2.4/b/c/3_Config.in 1.2.1.1.4.3.1.5 644)
+++ 9.42(w)/drivers/char/Config.in Thu, 27 Sep 2001 12:11:54 +1000 kaos (linux-2.4/b/c/3_Config.in 1.2.1.1.4.3.1.5 644)
@@ -219,8 +219,10 @@ bool 'Direct Rendering Manager (XFree86
if [ "$CONFIG_DRM" = "y" ]; then
bool ' Build drivers for new (XFree 4.1) DRM' CONFIG_DRM_NEW
if [ "$CONFIG_DRM_NEW" = "y" ]; then
+ comment 'DRM 4.1 drivers'
source drivers/char/drm/Config.in
else
+ comment 'DRM 4.0 drivers'
define_bool CONFIG_DRM_OLD y
source drivers/char/drm-4.0/Config.in
fi
prev parent reply other threads:[~2001-09-27 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 17:48 Stephen Torri
2001-09-27 2:16 ` Keith Owens [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=8203.1001557002@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=storri@ameritech.net \
/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®