9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Alexander C. Deztroyer" <alex-sci@freenet.co.nz>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 3dfx banshee
Date: Thu, 21 Dec 2000 09:44:37 +0000	[thread overview]
Message-ID: <91r9nv$57m5r$1@ID-64718.news.dfncis.de> (raw)
In-Reply-To: <20001220140853.10BEA199E7@mail.cse.psu.edu>

I suggest you have a look at: vgadb(6) and vga(8)

I haven't play with the vgadb yet. But I think it might be the problem of
the kernel. Because it might need special driver to contorl the chip set(s).

Good luck
Alex

<jmk@plan9.bell-labs.com> wrote in message
news:20001220140853.10BEA199E7@mail.cse.psu.edu...
> vonstroheim@my-deja.com:
> Has anybody manage to use a 3dfx banshee PCI card with plan9 ?
>
> I modified the vgadb file to force the use of the voodoo3 driver but it
> failed.
> I got the following message (dumped in vgainfo.txt):
>
> main->snarf
> vga->snarf
> 3dfx->snarf
> sequencer->enter on
> sequencer->leave on
> 3dfx: unknown chip - DID 0003
>
> I've not tried this as I don't have a Banshee, but I believe it will
> work if you add the chip id in the two places it matters, i.e. in both
> /sys/src/9/pc/vga3dfx.c and /sys/src/cmd/aux/vga/3dfx.c look for all
> cases of
>
> case 0x0005: /* Avenger (a.k.a. Voodoo3) */
>
> and add
>
> case 0x0003: /* Banshee */
>
> (make sure tyou get them all, there's motre than one in the kernel
> driver).
>
> Let me know if it works and I'll add it into the distribution.
> Good luck.
>
> --jim


  reply	other threads:[~2000-12-21  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-20 14:08 jmk
2000-12-21  9:44 ` Alexander C. Deztroyer [this message]
     [not found] <20001220145503.C691D199F7@mail.cse.psu.edu>
2000-12-22  4:09 ` Naofumi Yasufuku
  -- strict thread matches above, loose matches on Subject: below --
2000-12-20 10:00 vonstroheim

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='91r9nv$57m5r$1@ID-64718.news.dfncis.de' \
    --to=alex-sci@freenet.co.nz \
    --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).