From: "Michel Eyckmans (MCE)" <mce@pi.be>
To: James Simmons <jsimmons@infradead.org>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
nick black <dank@suburbanjihad.net>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 + matroxfb = unuusable VC
Date: Sat, 26 Jul 2003 12:33:29 +0200 [thread overview]
Message-ID: <200307261033.h6QAXTNh002916@jebril.pi.be> (raw)
In-Reply-To: Your message of "Fri, 25 Jul 2003 01:07:15 BST." <Pine.LNX.4.44.0307250106220.7845-100000@phoenix.infradead.org>
> > 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.
>
> Which drivers issues ?
Nothing to worry about anymore. There were some matroxfb ones
(oopses at boot only when actively using matroxfb, for instance)
but also a ton of non-video related stuff: whenever one thing got
fixed, something had been broken in the mean time. Some of it still
not solved, by the way, (aha152x anyone?).
The matrox oopses were solved already before I applied Petr's
matroxfb-2.5.72.gz patch.
MCE
next prev parent reply other threads:[~2003-07-26 10:23 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)
2003-07-25 0:07 ` James Simmons
2003-07-26 10:33 ` Michel Eyckmans (MCE) [this message]
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=200307261033.h6QAXTNh002916@jebril.pi.be \
--to=mce@pi.be \
--cc=VANDROVE@vc.cvut.cz \
--cc=dank@suburbanjihad.net \
--cc=jsimmons@infradead.org \
--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).