mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linux-kernel@vger.kernel.org,
	Linux Frame Buffer Device Development 
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: [PATCH] New radeonfb fork
Date: 06 Apr 2003 17:29:14 +0200	[thread overview]
Message-ID: <1049642954.550.41.camel@zion.wanadoo.fr> (raw)

Hi !

As I told a while ago, I'm forking radeonfb for now, at least
until Ani (current maintainer) either give me maintainership
or gets all that stuff in the official version.

I need testers, and I'd appreciate any patches people may have
for it as well since I know a bunch of ppl have been spreading
various radeonfb patches around, I want to take over all of these
and see what is worth getting in. For 2.5, I'm working on a
complete rewrite (& split) of the driver.

So far, I already have something to play with that fixes a
bunch of issues. Patches against 2.4.20 and 2.4.21-pre7 can
be found here: (too big to inline). Note that I also bring
in various other pci_ids.h updates but that shouldn't harm
you and is easier that way for me ;)

http://penguinppc.org/~benh/radeonfb-040603-2.4.20.diff
http://penguinppc.org/~benh/radeonfb-040603-2.4.21-pre7.diff

NOTE: It's known that radeonfb is incompatible with ATI binary
GL drivers (at least it crashes the machine on a friend's r300),
I'm investigating.

Ben.



             reply	other threads:[~2003-04-06 15:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 15:29 Benjamin Herrenschmidt [this message]
2003-04-10  8:46 ` Daniele Venzano
2003-04-10 14:26   ` Benjamin Herrenschmidt
2003-04-10 21:13     ` Daniele Venzano
2003-04-11  8:04       ` Benjamin Herrenschmidt
2003-04-11 18:23         ` James Simmons
2003-04-11 18:36           ` Benjamin Herrenschmidt
     [not found] <20030406170137.F0DB726AC@dreamland.darkstar.lan>
2003-04-06 17:50 ` Benjamin Herrenschmidt

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=1049642954.550.41.camel@zion.wanadoo.fr \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®