From: Dave Jones <davej@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: bob.montgomery@hp.com, Yinghai Lu <yinghai@kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vojtech@suse.cz" <vojtech@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
"chandru@in.ibm.com" <chandru@in.ibm.com>,
Joerg Roedel <joerg.roedel@amd.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Pavel Machek <pavel@ucw.cz>, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] disable CPU side GART accesses
Date: Wed, 29 Oct 2008 17:32:44 -0400 [thread overview]
Message-ID: <20081029213244.GD24794@redhat.com> (raw)
In-Reply-To: <21d7e9970810291424g369035d4h562b54c676d49aef@mail.gmail.com>
On Thu, Oct 30, 2008 at 07:24:34AM +1000, Dave Airlie wrote:
> This stops the CPU from using the aperture for most DRI things. I
> can't confirm this won't regress working systems
> though. The whole AMD GART thing scares me, esp if some of the host
> chipsets also have an AGP GART.
The easy cop-out for those in the past has been 'dont support them'.
It's why we removed some K8 chipset PCI IDs from the via driver for eg.
iirc, if we leave them unprogrammed, they're essentially irrelevant.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2008-10-29 21:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 21:48 [PATCH] disable CPU side GART accesses Bob Montgomery
2008-10-15 23:40 ` Linus Torvalds
2008-10-16 19:17 ` Bob Montgomery
2008-10-15 23:48 ` Ingo Molnar
2008-10-16 0:22 ` Yinghai Lu
2008-10-16 17:00 ` Bob Montgomery
2008-10-16 17:43 ` Yinghai Lu
2008-10-16 19:26 ` Bob Montgomery
2008-10-27 22:42 ` Bob Montgomery
2008-10-27 23:06 ` Yinghai Lu
2008-10-29 20:52 ` Bob Montgomery
2008-10-29 21:24 ` Dave Airlie
2008-10-29 21:32 ` Dave Jones [this message]
2008-10-29 21:40 ` Dave Airlie
2008-11-03 23:36 ` Bob Montgomery
2008-11-03 23:55 ` Dave Airlie
2008-11-19 22:12 ` Bob Montgomery
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=20081029213244.GD24794@redhat.com \
--to=davej@redhat.com \
--cc=airlied@gmail.com \
--cc=ak@linux.intel.com \
--cc=bob.montgomery@hp.com \
--cc=chandru@in.ibm.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jbarnes@virtuousgeek.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.org \
--cc=vojtech@suse.cz \
--cc=yinghai@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