From: Dave Airlie <airlied@linux.ie>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] DRM depends on ???
Date: Mon, 30 May 2005 12:19:09 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.58.0505301216500.31258@skynet> (raw)
In-Reply-To: <429AF53B.3080805@aitel.hist.no>
>
> Why is that case invalid? I may have DRM=y so I get DRM on my
> PCI graphichs card. Then I might load an agp module in order
> to use agp on *some other* agp card. I have no problem with DRM=y,AGP=m being
> invalid for the common
> single-card setup, but there are multi-card setups too. Not that
> I need this special case personally - I have two cards but don't use modules.
Yes but the support costs for me of allowing that second case aren't
worth it, if people have a special case they don't lose anything by having
AGP supported DRM in the kernel or AGP in the kernel all the time..
whereas I don't have to answer a load of questions from people whose AGP
cards stop working because they build DRM into the kernel and AGP as a
module...
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG
next prev parent reply other threads:[~2005-05-30 11:19 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
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 [this message]
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=Pine.LNX.4.58.0505301216500.31258@skynet \
--to=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=geert@linux-m68k.org \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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®