From: Dave Jones <davej@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Vasilyev <pavel@pavlinux.ru>, linux-kernel@vger.kernel.org
Subject: Re: GART_IOMMU without AGP
Date: Wed, 22 Jul 2009 18:28:07 -0400 [thread overview]
Message-ID: <20090722222807.GB20860@redhat.com> (raw)
In-Reply-To: <20090722231738.21de4deb@lxorguk.ukuu.org.uk>
On Wed, Jul 22, 2009 at 11:17:38PM +0100, Alan Cox wrote:
> On Wed, 22 Jul 2009 17:37:46 -0400
> Dave Jones <davej@redhat.com> wrote:
>
> > On Wed, Jul 22, 2009 at 07:26:49PM +0400, Pavel Vasilyev wrote:
> > > In the kernel configuration, if I choose x86_64 and PCI, then choose the item
> > > "Garth IOMMU support", which, in turn, chooses not to switch off, support for
> > > AGP. But many IOMMU system does not have AGP bus.
> >
> > The lack of AGP slots doesn't mean a lack of AGP bus.
> > It's part of the K8 on-CPU northbridge.
>
> And the user is selecting CONFIG_AGP to select AGP devices rather than to
> demonstrate their deep guru grade knowledge of K8 northbridges.
The user isn't selecting it at all. IOMMU is because it knows better than
the user. "I'll turn this on for you, so that I don't corrupt your hard
disk when you load a video driver" seems eminently sensible to me.
> Not only
> that but CONFIG_AGP controls the display of AGP video card options so it
> is a selection for offered devices not really an internal detail.
CONFIG_AGP has _nothing_ to do with video card options.
It's entirely about the aperture.
Dave
next prev parent reply other threads:[~2009-07-22 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 15:26 GART_IOMMU without AGP Pavel Vasilyev
2009-07-22 21:37 ` Dave Jones
2009-07-22 21:58 ` Pavel Vasilyev
2009-07-22 22:25 ` Dave Jones
2009-07-22 22:44 ` Alan Cox
2009-07-22 22:17 ` Alan Cox
2009-07-22 22:28 ` Dave Jones [this message]
2009-07-22 23:05 ` Pavel Vasilyev
2009-07-22 22:34 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2009-07-22 23:15 Pavel Vasilyev
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=20090722222807.GB20860@redhat.com \
--to=davej@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@pavlinux.ru \
/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