From: thunder7@xs4all.nl
To: linux-kernel@vger.kernel.org
Subject: Re: [lkml]Re: [PATCH] matroxfb and mga XF4 driver coexistence...
Date: Thu, 12 Apr 2001 20:53:03 +0200 [thread overview]
Message-ID: <20010412205303.A20394@middle.of.nowhere> (raw)
In-Reply-To: <3AD5A7C4.D740ED74@neuronet.pitt.edu> <Pine.LNX.4.31.0104120922070.15715-100000@rc.priv.hereintown.net>
In-Reply-To: <Pine.LNX.4.31.0104120922070.15715-100000@rc.priv.hereintown.net>; from clubneon@hereintown.net on Thu, Apr 12, 2001 at 09:28:44AM -0400
On Thu, Apr 12, 2001 at 09:28:44AM -0400, Chris Meadors wrote:
> On Thu, 12 Apr 2001, Rafael E. Herrera wrote:
> > If the problem occurs whithout the frame buffer on, the problem seems to
> > be on the X server.
>
> Exactly. That is what I'm saying. I've seen the problem with the
> returning to VESA text modes from XFree 4.0 anytime I use the hallib, with
> 2.2 and 2.4 kernels. If I compile an X server without the hallib it's
> fine (G450 users don't have that option, and I like my dual head).
>
> If X changes the mode upon starting it should put it back when it is done.
>
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!' ?
Good luck,
Jurriaan
--
HORROR FILM WISDOM:
7. If you're running from the monster, you will most likely trip or
fall. If you are female you can bet on it.
GNU/Linux 2.4.3-ac4 SMP/ReiserFS 2x1743 bogomips load av: 0.03 0.01 0.02
next prev parent reply other threads:[~2001-04-12 18:58 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 ` thunder7 [this message]
2001-04-12 19:53 ` [lkml]Re: " Chris Meadors
-- strict thread matches above, loose matches on Subject: below --
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=20010412205303.A20394@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.