linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Chris Meadors <clubneon@hereintown.net>
Cc: alan@lxorguk.ukuu.org.uk, torvalds@transmeta.com,
	linux-kernel@vger.kernel.org, linux-fbdev@vuser.vu.union.edu
Subject: Re: [PATCH] matroxfb and mga XF4 driver coexistence...
Date: Thu, 12 Apr 2001 13:01:13 MET-1	[thread overview]
Message-ID: <4BEDDEE649D@vcnet.vc.cvut.cz> (raw)

On 11 Apr 01 at 14:55, Chris Meadors wrote:
> 
> I would like to see this fixed as much as anyone (even complained to the
> XFree people from SuSE last ALS).  But I don't think the fix should be in
> the kernel.  XF4 needs to be fixed.  The problem doesn't just effect the
> maxtroxfb, but also the vgacon video mode selection.

But only users using matroxfb complains to me and/or to linux-kernel ;-)
You know, it worked last week, but it does not work anymore today. And
only thing I changed was kernel. So it must be in kernel...
 
> If I put anything other than "normal" or "extended" in the "vga=" line of
> my lilo.conf the machine starts okay, but upon exiting X bad stuff

It is first time I see that other drivers than mga one has troubles.
 
> I don't use the matroxfb driver so this patch wouldn't help me, and is
> also why I say XFree 4.0 needs to be fixed.

Buy matrox and use matroxfb. It will fix problem for you, then...
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
                                                

             reply	other threads:[~2001-04-12 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-12 13:01 Petr Vandrovec [this message]
2001-04-12 13:04 ` [PATCH] matroxfb and mga XF4 driver coexistence 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
  -- strict thread matches above, loose matches on Subject: below --
2001-04-11 18:11 Petr Vandrovec
2001-04-11 18:55 ` Chris Meadors

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=4BEDDEE649D@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=clubneon@hereintown.net \
    --cc=linux-fbdev@vuser.vu.union.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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).