Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261548AbTEKOPt (ORCPT ); Sun, 11 May 2003 10:15:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261566AbTEKOPt (ORCPT ); Sun, 11 May 2003 10:15:49 -0400 Received: from pb148.mielec.sdi.tpnet.pl ([80.49.1.148]:23557 "EHLO enigma.put.mielec.pl") by vger.kernel.org with ESMTP id S261548AbTEKOPs (ORCPT ); Sun, 11 May 2003 10:15:48 -0400 Message-ID: <3EBE5E04.4020806@put.mielec.pl> Date: Sun, 11 May 2003 16:28:20 +0200 From: Grzegorz Wilk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; PL; rv:1.3) Gecko/20030312 X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Bartlomiej Zolnierkiewicz CC: linux-kernel@vger.kernel.org Subject: Re: [PATCH] SiS648 support for agpgart, kernel 2.4.21-rc2-ac1 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1058 Lines: 26 Uzytkownik Bartlomiej Zolnierkiewicz napisal: > [...] > It is a bit misleading, read once again and look at "GENERAL FEATURES", > 2X and 4X supported and 8X *compatible*. > Look also at R9200(PRO) spec, it is a R9000(PRO) with AGP3.0 support. You're right. The information provided by ATI is confusing. It dosen't make much differece to me. By the time a game or application capable of taking any benefits from agp8x will be released R9k will be too poor to work with it anyway... ;) Still I have enough of companies mixing my mind with such statements as ATI (I'm not really into hardware so together with my poor english results in such mistakes). > btw. R9100 is both faster/cheaper than R9000PRO. I bought my R9k at the end of 2002 when it's power/economy indicator used to be much higher than today is. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/