From: Nelson Abramson <pogtal@erols.com>
To: jingai@floatingpenguins.com
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Adaptec PowerDomain 29160N supported?
Date: Tue, 25 Jan 2000 20:54:02 -0500 [thread overview]
Message-ID: <388E53BA.5DC43A02@erols.com> (raw)
In-Reply-To: 200001260144.UAA27868@shell.faradic.net
jingai wrote:
> I'm ready to purchase an adaptec scsi card to replace my initio miles
> (doesn't work under linux/ppc), and I noticed that the 29160N is around the
> same price as the 2940UW... so, my question is, is it supported under
> LinuxPPC? and what exactly makes it 160MB/s? if anyone else owns this
> card, I'd like to hear your impressions..
Which initio card are you giving up on? There are device drivers for two
types of initio cards last time I looked in the kernel config files (I have no
idea if they work, I've just seen them in existance).
I don't know about that particular card, but AFAIK, the only scsi
standards capable of hitting 160mb/s are u2w lvd, which means that they have a
huge bandwith, and use extremely low amounts of energy Only u2w lvd drives
can get anywhere near that amount of data transfer, and the chain is only as
fast as your slowest device, so if you are migrating a regular ole scsi narrow
drive onto a u2w lvd chain, it's only going to go at scsi narrow speeds, which
is about 10mb/s max.
As a side comment, the state of scsi has gone down hill ever since Apple
stopped bundling one w/ every new mac...
HTH
--Nelson Abramson
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-26 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-26 1:44 Adaptec PowerDomain 29160N supported? jingai
2000-01-26 1:54 ` Nelson Abramson [this message]
2000-01-26 2:36 ` Justin Shore
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=388E53BA.5DC43A02@erols.com \
--to=pogtal@erols.com \
--cc=jingai@floatingpenguins.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.org \
/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).