From: Knut_Petersen@t-online.de
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: cyberblade patch
Date: Fri, 12 Aug 2005 06:17:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0508120553160.2252@linux.site> (raw)
In-Reply-To: <20050811100108.GC1287@ws-gradcol1.icm.edu.pl>
At the end of 2003 I complained about a lot of serious bugs. Nobody cared
about that. Some people, even one of the linux gurus, just told me to use
epiafb (not included in the standard distribution), but that driver is
even more broken. I then wrote a dirty hack and used it for some time ...
a vesafb with integrated cyberblade acceleration. Not really clean enough
for release ;-) At the end of 2005 I had some time and wrote cyblafb, based
on tridentfb. Probably cyblafb will be extended to include support for
cyberblade/i7 and another "Blade 3D" graphics cores. But fixing tridentfb
for all chips without hardware access is a task too time consuming for me.
cu,
Knut
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-12 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 10:29 cyberblade patch Dominik 'Rathann' Mierzejewski
2005-08-04 15:13 ` Dominik 'Rathann' Mierzejewski
2005-08-10 13:11 ` Dominik 'Rathann' Mierzejewski
2005-08-10 17:41 ` Knut_Petersen
2005-08-11 10:01 ` Dominik 'Rathann' Mierzejewski
2005-08-12 4:17 ` Knut_Petersen [this message]
2005-08-16 13:34 ` Dominik 'Rathann' Mierzejewski
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=Pine.LNX.4.58.0508120553160.2252@linux.site \
--to=knut_petersen@t-online.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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