public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, thomas@winischhofer.net,
	linux-kernel@vger.kernel.org, jsimmons@infradead.org
Subject: Re: 2.6.1-mm1: drivers/video/sis/sis_main.c link error
Date: Mon, 12 Jan 2004 17:04:21 +0000	[thread overview]
Message-ID: <20040112170421.GN14674@redhat.com> (raw)
In-Reply-To: <200401121200.19166.gene.heskett@verizon.net>

On Mon, Jan 12, 2004 at 12:00:19PM -0500, Gene Heskett wrote:

 > Are you saying I should turn it on, but just not select a specific 
 > makers chip-boardset?  Or that I should go get a different card?

Might as well turn it off completely. You have an Nvidia card, and
that isn't supported by DRI. (AGPGART is just a soft-dependancy for AGP
based cards that DRI supports)

 > But, I'm thinking of building another, and certainly open for video 
 > card suggestions within the 'utility' price range.

Apart from the integrated chipsets from Intel/VIA etc sadly, there's really
not much in the graphics world that has 100% opensource drivers any more.
Basically, forget it for the high performance end of the market.
(And these days, even most of the commodity stuff (NVIDIA, ATI etc) falls
 into that bracket)
 
		Dave


  reply	other threads:[~2004-01-12 17:05 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09  9:40 2.6.1-mm1 Andrew Morton
2004-01-09 14:47 ` 2.6.1-mm1 Christoph Hellwig
2004-01-09 14:53 ` 2.6.1-mm1 Wojciech 'Sas' Cieciwa
2004-01-09 14:21   ` 2.6.1-mm1 Bartlomiej Zolnierkiewicz
2004-01-09 15:24 ` 2.6.1-mm1 (compile stats) John Cherry
2004-01-09 16:30 ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 21:20   ` 2.6.1-mm1 Andrew Morton
2004-01-09 21:24     ` 2.6.1-mm1 Prakash K. Cheemplavam
2004-01-09 23:04     ` 2.6.1-mm1 - nforce2 timer patch sum up cheuche+lkml
2004-01-09 19:31 ` 2.6.1-mm1: sound/pci/cmipci.c compile error Adrian Bunk
2004-01-09 22:43   ` Andrew Morton
2004-01-09 23:37 ` 2.6.1-mm1: drivers/video/sis/sis_main.c link error Adrian Bunk
2004-01-10  4:04   ` Thomas Winischhofer
2004-01-12  2:58     ` Linus Torvalds
2004-01-12  4:53       ` Gene Heskett
2004-01-12  5:42         ` Andrew Morton
2004-01-12  6:11           ` Valdis.Kletnieks
2004-01-12  6:47             ` Gene Heskett
2004-01-12  7:05               ` Andrew Morton
2004-01-12  7:20                 ` Gene Heskett
2004-01-12 12:38                 ` Gene Heskett
2004-01-12  6:21           ` Gene Heskett
2004-01-12  6:34             ` Andrew Morton
2004-01-12  6:58               ` Gene Heskett
2004-01-12  7:03               ` Gene Heskett
2004-01-12 16:33             ` Dave Jones
2004-01-12 17:00               ` Gene Heskett
2004-01-12 17:04                 ` Dave Jones [this message]
2004-01-12  8:58       ` Thomas Winischhofer
2004-01-12 14:32         ` Moritz Muehlenhoff
2004-01-12 10:36       ` Andrew Walrond
2004-01-13 19:04     ` Adrian Bunk
2004-01-14  0:35       ` Thomas Winischhofer
2004-01-15 11:32         ` Adrian Bunk
2004-01-15 11:42           ` Thomas Winischhofer

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=20040112170421.GN14674@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=gene.heskett@verizon.net \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@winischhofer.net \
    --cc=torvalds@osdl.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