All of lore.kernel.org
 help / color / mirror / Atom feed
From: "B. Douglas Hilton" <bdhilton@charter.net>
To: Tobias Giesen <tobias_subscriber@tgtools.com>
Cc: 'palinux' <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Re: C200 Voodoo2 Progress Report
Date: Fri, 06 Sep 2002 21:06:32 -0400	[thread overview]
Message-ID: <3D795118.1060709@charter.net> (raw)
In-Reply-To: 000001c25607$c1fcdf90$0100a8c0@PLUTO

The C200 and probably C160, 180, 240, and 360
have two three different busses inside: the
Hewlett-Packard GSC bus, 5V/32bit PCI (dino),
and 3V/64bit PCI (cujo). Some PCI cards are
universal and have two punchouts. The 3V cards
have the punchout close to the outside edge of
the card, and 5V are the other way around.
You can use a 3V/32bit card in a 3V/64bit
slot with no problems. The Voodoo2 is 5V
only and will not fit into one of the Cujo slots.


Tobias Giesen wrote:
>>For one, the Voodoo2 is a 5V PCI card so it 
>>will not fit into the Cujo slots, only Dino.
> 
> 
> Which means some people can't use it? But you and I 
> have 5V slots allright, don't we.
> 

Right, C200 has both types. See above.

> 
>>programming video cards is a bit above my level
> 
> 
> Mine too!! Things always seem to be more difficult than
> you'd think at first. In any case I will now try to 
> repeat your initial steps, and I'll be very happy if I get
> to the checkerboard pattern.
> 

Yeah, not sure what did that. After rebuilding the sstfb
as a module and modprobe'ing it, I got a couple of colored
blocks, but not the checkerboard. I'm not sure of the exact
sequence as I haven't hooked up the spare monitor yet but
was switching the VGA cable back and forth. Further testing
seems warranted.

My C200 is back offline temporarily. I'm re-wiring my LAN
as it has gotten to be a horrendous mess of tangled wires
and cables after unplugging and replugging things for
several months. Need to straighten it out again :-)

I think I'll put the C200 onto my KVM switch with my X86 box
and reconsolidate it. I don't believe I'll be cracking the
case open anymore so it can be stowed away better than it is.
I put something like 370Mb RAM into it, a cdrom, an EEPro100,
and the Voodoo2. It is pretty well maxed out unless I run
low on HDD space which seems unlikely considering I just use
it as a hobby linux hacking box.

Thats it for now.

- Doug

  reply	other threads:[~2002-09-07  1:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 21:49 [parisc-linux] C200 Voodoo2 Progress Report B. Douglas Hilton
2002-09-05 21:58 ` Derek Engelhaupt
2002-09-05 23:15 ` Tobias Giesen
2002-09-06  2:46 ` [parisc-linux] " Matthew Wilcox
2002-09-07  0:09   ` B. Douglas Hilton
2002-09-07  0:09   ` B. Douglas Hilton
2002-09-07  0:44     ` Tobias Giesen
2002-09-07  1:06       ` B. Douglas Hilton [this message]
2002-09-07  2:04         ` Matthew Wilcox
2002-09-06  2:46 ` Matthew Wilcox

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=3D795118.1060709@charter.net \
    --to=bdhilton@charter.net \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=tobias_subscriber@tgtools.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.