9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ByteMeDammit <bytemedammit@nowhere.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Trident9000i success?
Date: Tue, 21 Oct 2003 16:33:52 +0000	[thread overview]
Message-ID: <dtclb.196859$%h1.191072@sccrnsc02> (raw)
In-Reply-To: <b2748d9b3ccfea842f0ae3e3f28b31d1@plan9.bell-labs.com>

Thanks for the response, jmk.  Guess I need to dig up a card witha chipset
on the list!  Looks like I'll need an IDE HDD too.  Neither of these SCSI
controllers seems to be recognized...

ByteMeDammit

<jmk@plan9.bell-labs.com> wrote in message
news:b2748d9b3ccfea842f0ae3e3f28b31d1@plan9.bell-labs.com...
> That's a chip we have no support for. As far as I can tell it has no
> hardware cursor and pre-dates the generation of Trident chips we handle.


      reply	other threads:[~2003-10-21 16:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21  9:28 ByteMeDammit
2003-10-21 14:17 ` jmk
2003-10-21 16:33   ` ByteMeDammit [this message]

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='dtclb.196859$%h1.191072@sccrnsc02' \
    --to=bytemedammit@nowhere.net \
    --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).