From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: "Michel Eyckmans (MCE)" <mce@pi.be>
Cc: nick black <dank@suburbanjihad.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 + matroxfb = unuusable VC
Date: Fri, 25 Jul 2003 01:23:37 +0200 [thread overview]
Message-ID: <82E8EE527D4@vcnet.vc.cvut.cz> (raw)
On 25 Jul 03 at 0:17, Michel Eyckmans (MCE) wrote:
> > Anyway, can you try applying matroxfb-2.5.72.gz from
> > ftp://platan.vc.cvut.cz/pub/linux/matrox-latest to your tree (you can
> > enable only matroxfb after patching, no other fbdev will work) and retry
> > tests?
>
> YES! No more ghost X image, no more white rectangles, no more sudden
> jump scrolling, and a backspace key that actually works again. Please
> do consider pushing (some of) this to Linus for inclusion into the
> 2.6.0.test series!
Impossible. It reverts huge parts of the fbdev API almost completely to
the 2.4.x state, and I was already outvoted in that vote couple of
times since January.
BTW, with my patch accented characters works correctly only on VT1.
I'm not sure how it behaves on Linus tree...
And I'm not saying that there are no bugs in the matroxfb which is in
Linus's kernel. But as nobody even answered my question I sent out on
monday whether it is correct that FBIOGETCMAP ioctl can overwrite arbitrary
kernel memory, I kinda lost an interest in the stock fbdev...
Best regards,
Petr Vandrovec
next reply other threads:[~2003-07-24 23:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 23:23 Petr Vandrovec [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-23 23:50 2.6.0-test1 + matroxfb = unuusable VC Petr Vandrovec
2003-07-24 22:17 ` Michel Eyckmans (MCE)
2003-07-25 0:07 ` James Simmons
2003-07-26 10:33 ` Michel Eyckmans (MCE)
2003-07-25 12:20 ` nick black
2003-07-21 18:44 Petr Vandrovec
2003-07-21 20:02 ` nick black
2003-07-23 23:05 ` Michel Eyckmans (MCE)
2003-07-21 18:10 Petr Vandrovec
2003-07-21 18:33 ` nick black
2003-07-18 22:39 Michel Eyckmans (MCE)
2003-07-19 6:02 ` Jurriaan
2003-07-21 17:45 ` nick black
2003-07-24 23:39 ` James Simmons
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=82E8EE527D4@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=dank@suburbanjihad.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mce@pi.be \
/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;
as well as URLs for NNTP newsgroup(s).