public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: vapier@gentoo.org
Subject: Re: [gentoo-dev] 2.6.22 stable plans
Date: Thu, 2 Aug 2007 16:55:58 -0700	[thread overview]
Message-ID: <20070802165558.515ef814@localhost> (raw)
In-Reply-To: <200708021931.10425.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Thu, 2 Aug 2007 19:31:09 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> if the driver blows dead goats and the vendor isnt willing to help
> and no Gentoo dev wants to touch it, what other solution is there ?

There's an open-source driver for the r5xx stuff called the avivo
driver [1]. It's still pretty rough, so I haven't packaged it yet. For
anyone interested, it should be pretty easy to make an ebuild for it
based on the xf86-video-ati ebuild and the git eclass.

For the present, je_fro's picked up ati-drivers and anarchy's been
sending changes for some of the newest stuff.

Thanks,
Donnie

1. http://gitweb.freedesktop.org/?p=avivo/xf86-video-avivo.git;a=summary

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-08-02 23:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 23:35 [gentoo-dev] 2.6.22 stable plans Daniel Drake
2007-07-31 23:51 ` William L. Thomson Jr.
2007-08-01  0:16   ` Jonathan Adamczewski
2007-08-01 12:08   ` Daniel Drake
2007-08-01 13:36     ` Doug Goldstein
2007-08-01 16:54       ` Chris Gianelloni
2007-08-01 22:00         ` William L. Thomson Jr.
2007-08-02 18:08           ` federico ferri
     [not found]           ` <46B21DC5.1060107@inwind.it>
2007-08-02 21:52             ` William L. Thomson Jr.
2007-08-02 23:31           ` Mike Frysinger
2007-08-02 23:55             ` Donnie Berkholz [this message]
2007-08-03  0:05               ` Mike Frysinger
2007-08-03  3:18                 ` William L. Thomson Jr.
2007-08-03  3:35                   ` Donnie Berkholz
2007-08-04 17:32                     ` William L. Thomson Jr.
2007-08-03  4:14                   ` Mike Frysinger
2007-08-03  4:37                     ` Donnie Berkholz
2007-08-03  8:24                       ` Marijn Schouten (hkBst)
2007-08-03 12:25                         ` Mike Frysinger
2007-08-03 13:02                       ` Daniel Drake
2007-08-03 13:16                         ` Mike Frysinger
2007-08-03 17:46                     ` Gustavo Zacarias
2007-08-04 17:35                     ` William L. Thomson Jr.
2007-08-04 18:32                       ` Mike Frysinger
2007-08-03  3:19               ` William L. Thomson Jr.
2007-08-03  3:29                 ` [gentoo-dev] " Duncan
2007-08-03  3:35                 ` [gentoo-dev] " Donnie Berkholz
2007-08-03 11:48                   ` Stephen P. Becker
2007-08-05 14:26                     ` Jan Kundrát
2007-08-05 14:41                       ` Stephen P. Becker
2007-08-04 19:03                   ` William L. Thomson Jr.
2007-08-01 22:57         ` Homer Parker
2007-08-01 18:29       ` Donnie Berkholz
2007-08-01 21:55 ` Greg KH
2007-08-01 22:35   ` Daniel Drake
2007-08-01 23:09     ` Greg KH
2007-08-02  0:27       ` Daniel Drake

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=20070802165558.515ef814@localhost \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=vapier@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