From: Chris Meadors <clubneon@hereintown.net>
To: "thunder7@xs4all.nl" <thunder7@xs4all.nl>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [lkml]Re: [PATCH] matroxfb and mga XF4 driver coexistence...
Date: Thu, 12 Apr 2001 15:53:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.31.0104121546340.15715-100000@rc.priv.hereintown.net> (raw)
In-Reply-To: <20010412205303.A20394@middle.of.nowhere>
On Thu, 12 Apr 2001, thunder7@xs4all.nl wrote:
> Of course, but if we can fix the problem by making the kernel smaller,
> what possible motive could you have for opposing it other than 'but it
> doesn't solve _my_ problems!' ?
Agreed. The only thing I was thinking, was if the kernel is doing the
right thing now, it shouldn't be forced to work around a bug in XFree.
By not "fixing" the kernel, the XFree team would be forced to do the right
thing.
As for me, I'm going to see about getting the matroxfb working, so if the
patch goes in I'll be able to use a nice 132 character wide terminal
again. And I'm getting addicted to dual head in X, might be fun on the
console too.
-Chris
--
Two penguins were walking on an iceberg. The first penguin said to the
second, "you look like you are wearing a tuxedo." The second penguin
said, "I might be..." --David Lynch, Twin Peaks
next prev parent reply other threads:[~2001-04-12 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 13:01 [PATCH] matroxfb and mga XF4 driver coexistence Petr Vandrovec
2001-04-12 13:04 ` Rafael E. Herrera
2001-04-12 13:28 ` Chris Meadors
2001-04-12 18:53 ` [lkml]Re: " thunder7
2001-04-12 19:53 ` Chris Meadors [this message]
2001-04-15 14:50 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=Pine.LNX.4.31.0104121546340.15715-100000@rc.priv.hereintown.net \
--to=clubneon@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/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).