All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin Gonyou <austin@digitalroadkill.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matt_Domsch@Dell.com, dtroth@bellsouth.net, linux-kernel@vger.kernel.org
Subject: Re: DELL array controller access.
Date: 08 Jul 2002 17:13:37 -0500	[thread overview]
Message-ID: <1026166417.16788.0.camel@UberGeek> (raw)
In-Reply-To: <E17RdTp-0002re-00@the-village.bc.nu>

I know at a minimum...those cards can be put into a 154x mode, so it
will work. I remember that NetWare needed this feature.


On Mon, 2002-07-08 at 13:43, Alan Cox wrote:
> > > RedHat 7.0 and it does not see the board.  Where can I get a 
> > > EISA buss AHA-154x driver to access the array controller?
> > 
> > David, Dell never produced a Linux device driver for the Dell SCSI Array
> > card.  I had forgotten about the AHA-154x emulation feature, but since it
> > doesn't seem to work, it's unlikely that it ever will.  Everyone who worked
> > on that project 9 years ago has left for other opportunities.  The on-board
> > NCR SCSI controller should still work, and you can use software RAID quite
> > easily to accomplish similar functionality.
> 
> The EISA bus AHA154x equivalent is the AHA174x which we do support. I don't
> know what the Dell arrays used however
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
Austin Gonyou <austin@digitalroadkill.net>

  reply	other threads:[~2002-07-08 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-08 18:17 DELL array controller access Matt_Domsch
2002-07-08 18:43 ` Alan Cox
2002-07-08 22:13   ` Austin Gonyou [this message]
2002-07-09 10:10     ` Alan Cox
2002-07-09 15:55       ` Austin Gonyou
  -- strict thread matches above, loose matches on Subject: below --
2002-07-02  0:29 David T Roth

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=1026166417.16788.0.camel@UberGeek \
    --to=austin@digitalroadkill.net \
    --cc=Matt_Domsch@Dell.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dtroth@bellsouth.net \
    --cc=linux-kernel@vger.kernel.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 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.