From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 needs testers
Date: Thu, 18 Nov 2004 16:08:36 -0500 [thread overview]
Message-ID: <1100812116.16897.38.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1100807880.27416.4.camel@helen.science.oregonstate.edu>
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
On Thu, 2004-11-18 at 11:58 -0800, Donnie Berkholz wrote:
> In theory, yeah if you build xorg with USE=sdk. See ati-gatos,
> linuxwacom or synaptics ebuilds for examples of things that take
> advantage of this. In reality, some of the drivers are problably broken
> WRT compiling against the SDK. Only way to know is to test. But having
> only the binary drivers as options is a good possibility since they're
> also the only ones that work with a number of recent GameCD candidate
> games.
Yeah, I'm mostly looking for a way to squeeze out some more space for
the GameCD, so I can make some CDs smaller and so I can fit some bigger
games (America's Army, anyone?) on a single CD.
> By the way, most games use fonts. So having them would be a plus. But
> it's worth testing just how bad the misc fonts look, I guess. I'm
> working on having them be the only ones built with "minimal."
I'm not sure that any of the binary released games use any fonts, but it
would be something to check out.
> I'm sure ATI will support 6.8 soon enough, unless they want everyone
> running to Nvidia.
Next release, they say, but I can't remember how long the ATI product
cycle is for driver releases. I think it is something like every 2
months, which means we're still something like 7 weeks away from a new
release.
--
Chris Gianelloni
Release Engineering - Operational/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-18 21:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 23:01 [gentoo-dev] xorg-x11-6.8.0-r4 needs testers Donnie Berkholz
2004-11-18 0:14 ` Ciaran McCreesh
2004-11-21 14:41 ` Ned Ludd
2004-11-18 14:10 ` Chris Gianelloni
2004-11-18 15:39 ` Ciaran McCreesh
2004-11-18 16:21 ` Chris Gianelloni
2004-11-18 17:01 ` Ciaran McCreesh
2004-11-18 19:34 ` Chris Gianelloni
2004-11-18 17:08 ` Donnie Berkholz
2004-11-18 17:13 ` Donnie Berkholz
2004-11-18 20:57 ` Ferris McCormick
2004-11-18 18:50 ` Donnie Berkholz
2004-11-18 20:31 ` Chris Gianelloni
2004-11-18 19:58 ` Donnie Berkholz
2004-11-18 21:08 ` Chris Gianelloni [this message]
2004-11-18 21:18 ` Chris Gianelloni
2004-11-18 20:26 ` Donnie Berkholz
2004-11-18 21:32 ` Chris Gianelloni
2004-11-18 20:31 ` Joseph Booker
2004-11-18 20:28 ` Donnie Berkholz
2004-11-24 21:45 ` Henrik Brix Andersen
2004-11-19 10:02 ` Paul de Vrieze
2004-11-19 16:44 ` Donnie Berkholz
2004-11-21 23:31 ` Donnie Berkholz
2004-11-18 17:45 ` Michiel de Bruijne
2004-11-18 17:47 ` Donnie Berkholz
2004-11-18 17:58 ` Michiel de Bruijne
2004-11-18 17:58 ` Donnie Berkholz
2004-11-18 18:26 ` Marcus D. Hanwell
2004-11-19 23:13 ` Michiel de Bruijne
2004-11-23 6:50 ` Gábor Farkas
2004-11-23 12:19 ` Jason Stubbs
2004-11-24 6:01 ` [gentoo-dev] " Duncan
2004-11-24 11:41 ` Duncan
2004-11-24 17:00 ` Donnie Berkholz
2004-11-24 12:33 ` [gentoo-dev] " Aaron Walker
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=1100812116.16897.38.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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