public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Dave Jones <davej@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: via agp patches
Date: Sat, 31 May 2008 10:41:13 -0700	[thread overview]
Message-ID: <20080531174113.GA18996@suse.de> (raw)
In-Reply-To: <20080531144715.GA22616@redhat.com>

On Sat, May 31, 2008 at 10:47:15AM -0400, Dave Jones wrote:
> On Fri, May 30, 2008 at 05:32:50PM -0700, Greg KH wrote:
>  > 
>  > Looks like this adds a new device id, I have no idea why they remove
>  > another one at the same time...
> 
> I sent a patch adding the missing ident to airlied a few weeks back.
> I think it's currently in -mm.

Great.

> The removal of the other id is a mystery to me.

Here's what I got back from Via about this:
	VT3336 is a chipset for AMD Athlon/K8 CPU. Due to K8's unique
	architecture, the AGP resource and behavior are different from
	the traditional AGP which resides only in chipset. AGP is used
	by 3D driver which wasn't available for the VT3336 and VT3364
	generation until now.  Unfortunately, by testing, VT3364 works
	but VT3336 doesn't. That is why the subtraction. I think other
	options are leaving it in the AGP, but removing it from our DRI
	driver. Or, just leave it in both but warn people for issues in
	the release note.


So it sounds like it would be good to remove that id.

thanks,

greg k-h

  reply	other threads:[~2008-05-31 17:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  0:32 via agp patches Greg KH
2008-05-31  0:32 ` Greg KH
2008-05-31 14:47   ` Dave Jones
2008-05-31 17:41     ` Greg KH [this message]
2008-06-05 17:45       ` Dave Jones
2008-06-06  1:45         ` Greg KH
2008-05-31  0:33 ` Greg KH
2008-05-31 12:25   ` Alan Cox
2008-05-31 16:48     ` Jason L Tibbitts III
2008-05-31 17:43     ` Greg KH
2008-05-31 19:44       ` Alan Cox
2008-05-31  0:34 ` Greg KH
2008-05-31 22:50 ` Dave Airlie
2008-06-06  1:44   ` Greg KH

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=20080531174113.GA18996@suse.de \
    --to=gregkh@suse.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.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