All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Greg KH <greg@kroah.com>
Cc: "Tolentino, Matthew E" <matthew.e.tolentino@intel.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"Patterson, David H" <david.h.patterson@intel.com>,
	"Carbonari, Steven" <steven.carbonari@intel.com>,
	"Abel, Michael J" <michael.j.abel@intel.com>,
	"Tarabini, Anthony" <anthony.tarabini@intel.com>,
	"'andreasW@ati.com'" <andreasW@ati.com>,
	"Abdul-Khaliq, Rushdan" <rushdan.abdul-khaliq@intel.com>
Subject: Re: [PATCH] GART driver support for generic AGP 3.0 device detection/ enabling & Intel 7505 chipset support
Date: Fri, 18 Oct 2002 16:04:17 +0100	[thread overview]
Message-ID: <20021018150417.GA23741@suse.de> (raw)
In-Reply-To: <20021018035720.GA3326@kroah.com>

On Thu, Oct 17, 2002 at 08:57:20PM -0700, Greg KH wrote:

 > You should probably not build agp3.o unless i7505-agp.o is built too, or
 > do some of the other drivers need functions in agp3.c?

The AMD 8151 is AGP 3.0 compliant too, but the current driver is just
the page remapping support.  It's possible that some functionality
implemented both there and in agp3.c can be propagated both ways.

I'll look into this next week.
Despite it being support for a major protocol version bump, it's
still just another driver, which means it could go in after the
freeze if needbe.

Looks fine for merging afaics though.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk

      reply	other threads:[~2002-10-18 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 18:13 [PATCH] GART driver support for generic AGP 3.0 device detection/ enabling & Intel 7505 chipset support Tolentino, Matthew E
2002-10-18  3:57 ` Greg KH
2002-10-18 15:04   ` Dave Jones [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=20021018150417.GA23741@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=andreasW@ati.com \
    --cc=anthony.tarabini@intel.com \
    --cc=david.h.patterson@intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.com \
    --cc=michael.j.abel@intel.com \
    --cc=rushdan.abdul-khaliq@intel.com \
    --cc=steven.carbonari@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.