linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Eyckmans (MCE)" <mce@pi.be>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
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 00:17:25 +0200	[thread overview]
Message-ID: <200307242217.h6OMHPFk002164@jebril.pi.be> (raw)
In-Reply-To: Your message of "Thu, 24 Jul 2003 01:50:00 +0200." <816FF467B0D@vcnet.vc.cvut.cz>


> Are you sure it was matroxfb and not DRI what changed?

Actually, no. I've been stuck at 2.5.46 for *ages* due to a never ending 
succession of driver issues (still not all solved by the way). 2.5.72 was 
the next kernel I could actually try to use. A lot of change takes place
over that many kernel revisions.

But "never mind" (although... :-), because...

>  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!

Thanks,

 MCE

  reply	other threads:[~2003-07-24 22:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 23:50 2.6.0-test1 + matroxfb = unuusable VC Petr Vandrovec
2003-07-24 22:17 ` Michel Eyckmans (MCE) [this message]
2003-07-25  0:07   ` James Simmons
2003-07-26 10:33     ` Michel Eyckmans (MCE)
2003-07-25 12:20   ` nick black
  -- strict thread matches above, loose matches on Subject: below --
2003-07-24 23:23 Petr Vandrovec
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=200307242217.h6OMHPFk002164@jebril.pi.be \
    --to=mce@pi.be \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=dank@suburbanjihad.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;
as well as URLs for NNTP newsgroup(s).