public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <ed.sweetman@wmich.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.5.68 state of matroxfb
Date: Tue, 22 Apr 2003 16:53:02 -0400	[thread overview]
Message-ID: <3EA5ABAE.1020009@wmich.edu> (raw)

I'm just wondering what the state of the matroxfb driver is and why it's 
an option in the kernel when it's completely uncompilable and has been 
for many months. I know it requires patches to work and i was under the 
assumption that these patches were at linux-fbdev.org but that site has 
been down for the past few days i've tried to access it and with no 
documentation updates about the new matroxfb driver since 2.4, I've been 
unable to verify if this is the only place to find the matroxfb patches. 
  So what i'm getting at is why is there a matroxfb option in the 
current kernel when the driver isn't there and what the future/current 
situation is with the framebuffer driver. I'd like to get the most 
hardware support for video output as possible and it seems like the mga 
(mplayer)  driver built on top of the fb driver is the way to do that 
and since my Nvidia card is twice as fast at X operations as my G450, I 
was assuming that the 2.5 fb code was just much better than the 2.4 fb 
code since I use the nvidia fb driver in 2.5 with X using the nvidia 
driver (Xfree's ). I've never been able to test that theory though 
because i've never been able to build 2.5's matroxfb.


             reply	other threads:[~2003-04-22 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:53 Ed Sweetman [this message]
2003-04-22 23:02 ` 2.5.68 state of matroxfb Matt Reppert
  -- strict thread matches above, loose matches on Subject: below --
2003-04-23  0:24 rwhron
2003-04-23 10:43 Petr Vandrovec

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=3EA5ABAE.1020009@wmich.edu \
    --to=ed.sweetman@wmich.edu \
    --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