All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sean" <seanlkml@sympatico.ca>
To: "Discuss issues related to the xorg tree"  <xorg@lists.freedesktop.org>
Cc: jg@freedesktop.org,
	"Discuss issues related to the xorg tree" 
	<xorg@lists.freedesktop.org>,
	"Andreas Hauser" <andy@splashground.de>,
	"lkml" <linux-kernel@vger.kernel.org>
Subject: Re: State of Linux graphics
Date: Thu, 1 Sep 2005 17:29:26 -0400 (EDT)	[thread overview]
Message-ID: <39084.10.10.10.10.1125610166.squirrel@linux1> (raw)
In-Reply-To: <9e47339105090113381222c9d0@mail.gmail.com>

On Thu, September 1, 2005 4:38 pm, Jon Smirl said:

> We're not putting all of our eggs in one basket, you keep forgetting
> that we already have a server that supports all of the currently
> existing hardware. The question is where do we want to put our future
> eggs.

Amen!   All these arguments that we can't support an advanced future
design unless the new design also supports $10 third world video cards too
is a complete red herring.

Sean




  reply	other threads:[~2005-09-01 21:29 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 16:03 State of Linux graphics Jon Smirl
2005-08-30 17:26 ` David Reveman
2005-08-30 18:13   ` Jon Smirl
2005-08-30 22:38   ` Dave Airlie
2005-08-31  6:33   ` Allen Akin
2005-08-31  8:11     ` Anshuman Gholap
2005-08-31 17:20     ` David Reveman
2005-08-31 17:48     ` Jim Gettys
2005-08-31 18:23       ` Jon Smirl
2005-08-31 19:06       ` Allen Akin
2005-08-31 19:14         ` Jim Gettys
2005-08-31 18:29     ` Keith Packard
2005-08-31 20:06       ` Allen Akin
2005-08-31 20:20         ` Ian Romanick
2005-09-01  1:04           ` James Cloos
2005-08-31 21:06         ` Keith Packard
2005-09-01  1:58           ` Allen Akin
2005-09-01  3:11             ` Ian Romanick
2005-09-01  6:00               ` Antonio Vargas
2005-09-01 10:20                 ` Alan Cox
2005-09-01 13:57                   ` Antonio Vargas
2005-09-01  6:11               ` Allen Akin
2005-09-01  3:59             ` Keith Packard
2005-09-01 15:24               ` Brian Paul
2005-09-01 15:59                 ` Jim Gettys
2005-09-01 16:39                   ` Andreas Hauser
2005-09-01 20:18                     ` Jim Gettys
2005-09-01 20:38                       ` Jon Smirl
2005-09-01 21:29                         ` Sean [this message]
2005-09-01 16:09                 ` Alan Cox
2005-09-01 16:04                   ` Brian Paul
2005-09-01 17:21                     ` Ian Romanick
2005-09-01 17:26                       ` Keith Whitwell
2005-09-01 20:03               ` Allen Akin
2005-08-31  3:11 ` Daniel Stone
2005-08-31  4:29   ` Jon Smirl
2005-08-31  4:50   ` Jon Smirl
     [not found]     ` <1125464500.8730.68.camel@localhost.localdomain>
2005-08-31  5:17       ` Jon Smirl
2005-08-31  5:23       ` Jon Smirl
2005-08-31  5:40         ` Jon Smirl
2005-08-31  6:15 ` Eric Anholt
2005-08-31 13:38   ` Jon Smirl
  -- strict thread matches above, loose matches on Subject: below --
2005-09-02  2:44 rep stsb
2005-09-03  4:00 mcartoaje

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=39084.10.10.10.10.1125610166.squirrel@linux1 \
    --to=seanlkml@sympatico.ca \
    --cc=andy@splashground.de \
    --cc=jg@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xorg@lists.freedesktop.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 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.