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 15:31:22 -0500 [thread overview]
Message-ID: <1100809882.16897.34.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1100803840.26615.3.camel@helen.science.oregonstate.edu>
[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]
On Thu, 2004-11-18 at 10:50 -0800, Donnie Berkholz wrote:
> On Thu, 2004-11-18 at 09:08, Donnie Berkholz wrote:
> > 7. For x86 only, remove these video drivers: nsc, glint, tga, s3,
> > s3virge, rendition, neomagic, i740, cirrus, tseng, trident, chips, apm,
> > ark, cyrix, siliconmotion. I wasn't sure what was safe for other archs
> > and didn't want to play around without some more research.
> >
> > Of those, the only questionable ones to me are s3, s3virge and
> > especially siliconmotion. I could see the latter being popular on
> > systems that would otherwise use the "minimal" flag.
>
> After thinking about this a little, it occurred to me that for a truly
> minimal system, perhaps only the fbdev, vesa and vga drivers would be
> wanted.
That would definitely be cool. Along the same lines, would there be
some way to compile these drivers outside of the xorg-x11 ebuild? The
reason that I ask is USE="minimal" looks *perfect* for a GameCD, but
without some of the drivers, it would probably not work out too well.
Then again, I could just say that only cards that are supported via the
"nvidia-*" and "ati-drivers" are supported, which would make things much
easier... once ATI actually fixes their drivers to work with xorg 6.8.0,
that is... *rolleyes*
--
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 20:31 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 [this message]
2004-11-18 19:58 ` Donnie Berkholz
2004-11-18 21:08 ` Chris Gianelloni
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=1100809882.16897.34.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