From: "Russ Cox" <rsc@mit.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Shared memory graphic on cpu server
Date: Fri, 26 Sep 2003 10:33:34 -0400 [thread overview]
Message-ID: <0556a2cb886b9185e973f72d72873892@plan9.bell-labs.com> (raw)
In-Reply-To: <86llsbfxi1.fsf@gic.mteege.de>
> I'm not a great programmer but it maybe interesting to read the
> code. How can I make sure, that plan9 uses the correct driver?
Actually it may be a bit easier than that, as jmk said.
Run
pci | grep ' 03'
(That's a tab not a space before the 03.)
It will print a line like
0.3.0: 03.00.00 5333/8811 9 0:f8000000 67108864
the 5333/8811 is the vid/did (vendor and device id)
of the PCI device. That's the line for the video card
because field 2 is the type, and 03.xx.xx is video cards.
The vid will be 5333 (S3), but the did will be different.
Note it.
Then look in /lib/vgadb for the line
vid=0x5333 did=0x8D04 # ProSavage8 in P4M266 chipset
and add a line like it except with your did.
Finally, edit /sys/src/cmd/aux/vga/virge.c and everywhere
there is a "case 0x8D04:" add a "case your-did:" as well.
Then
cd /sys/src/cmd/aux/vga; mk install
and give it a try.
Russ
next prev parent reply other threads:[~2003-09-26 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 11:18 Matthias Teege
2003-09-26 12:49 ` Russ Cox
2003-09-26 13:03 ` Matthias Teege
2003-09-26 13:15 ` Russ Cox
2003-09-26 14:13 ` Matthias Teege
2003-09-26 14:33 ` Russ Cox [this message]
2003-09-26 14:06 ` jmk
2003-09-26 14:31 ` Matthias Teege
2003-09-26 14:47 ` jmk
2003-09-26 14:56 ` Matthias Teege
2003-09-26 15:06 ` Russ Cox
2003-09-26 15:55 ` Matthias Teege
2003-09-26 16:06 ` Russ Cox
2003-09-26 16:11 ` jmk
2003-09-26 17:19 ` Matthias Teege
2003-09-26 18:24 ` Matthias Teege
2003-09-26 18:31 ` Russ Cox
2003-09-29 3:02 ` okamoto
2003-09-29 6:12 ` Matthias Teege
2003-09-26 16:17 ` Charles Forsyth
2003-09-26 17:22 ` Matthias Teege
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=0556a2cb886b9185e973f72d72873892@plan9.bell-labs.com \
--to=rsc@mit.edu \
--cc=9fans@cse.psu.edu \
/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).