From: Jun Sun <jsun@mvista.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Steven J. Hill" <sjhill@realitydiluted.com>,
"Kevin D. Kissell" <kevink@mips.com>,
Linux/MIPS Development <linux-mips@oss.sgi.com>
Subject: Re: PCI Graphics/Video Card for Malta Board?
Date: Tue, 28 May 2002 09:58:19 -0700 [thread overview]
Message-ID: <3CF3B72B.4020600@mvista.com> (raw)
In-Reply-To: Pine.GSO.4.21.0205271534430.15706-100000@vervain.sonytel.be
Geert Uytterhoeven wrote:
> On Mon, 27 May 2002, Steven J. Hill wrote:
>
>>Kevin D. Kissell wrote:
>>
>>>I'd like to get a video-capable graphics card up
>>>and running on a MIPS Malta board (therefore
>>>PCI), ideally something mainstream like ATI.
>>>Does anyone on the list have any positive or
>>>negative recommendations in terms of cards
>>>and particularly in terms of the degree to which
>>>the drivers (and PCI set-up) have been ported
>>>to MIPS/Linux? I'll do what I must, but I hate
>>>re-inventing the wheel.
>>>
>>>
>>I can think of two things. First, a lot of graphics cards
>>rely on BIOS calls to be set up before the operating system
>>even boots. Second, I would stick to graphics cards that
>>have framebuffer support in the kernel as you stand at least
>>half a chance that those cards don't rely so heavily on a
>>peecee bios. Just my $.02.
>>
>
> Even then, most frame buffer device drivers rely on the firmware (PC BIOS or
> SPARC/PPC Open Firmware) having set up the video card.
>
> One of the exceptions is matroxfb,
Steve Longerbeam has a fb driver with BIOS init for ATI Xpert98 card, which
you can still buy. Dan Malek also wrote a driver for MQ200. If you ask
around, I am sure you can the patch somewhere.
For a while, I also had 3dfx voodoo3 working. Not sure about its status now.
You can find the patch at http://www.medex.hu/~danthe/tdfx/.
Jun
next prev parent reply other threads:[~2002-05-28 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 9:49 PCI Graphics/Video Card for Malta Board? Kevin D. Kissell
2002-05-27 9:49 ` Kevin D. Kissell
2002-05-27 13:25 ` Steven J. Hill
2002-05-27 13:37 ` Geert Uytterhoeven
2002-05-27 14:09 ` Kevin D. Kissell
2002-05-27 14:14 ` Geert Uytterhoeven
2002-05-28 16:58 ` Jun Sun [this message]
2002-05-28 17:43 ` Kevin D. Kissell
2002-05-28 22:19 ` Dan Malek
2002-05-28 23:54 ` Alan Cox
2002-05-29 8:17 ` Geert Uytterhoeven
2002-05-29 12:49 ` Alan Cox
2002-05-31 20:25 ` James Simmons
2002-05-31 20:24 ` James Simmons
2002-05-31 20:19 ` James Simmons
2002-06-04 1:09 ` Dan Malek
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=3CF3B72B.4020600@mvista.com \
--to=jsun@mvista.com \
--cc=geert@linux-m68k.org \
--cc=kevink@mips.com \
--cc=linux-mips@oss.sgi.com \
--cc=sjhill@realitydiluted.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