From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: Re: fc-al and A5000
Date: Tue, 15 Mar 2005 12:34:16 +0000 [thread overview]
Message-ID: <20050315123416.GA3857@internal> (raw)
Yep, I've been given access to an e4500 with a T3 array. So far, I've only
been able to try the drivers that are currently available. I've gone back
to 2.2.4 where socal first appeared, and still can't get things working. I
can only get the socal driver to recognize the live port. Proc shows that
the device (this T3) failed to respond, usually with a RJT.
Haven't gotten beyond that yet. I'm in the middle of buying a new house,
so I wont have time to work on this for another week or two. I do intend
to get it working though.
If anyone has information they want to dump on me about their experience
in this driver and trying to get this working, please do so. I'm going
into it blind, without any docs, and no reference point for a working
system.
On Mon, Mar 14, 2005 at 10:17:57PM -0800, David S. Miller wrote:
> On Tue, 15 Mar 2005 01:00:40 -0500
> Morten Pedersen <camaro468@gmail.com> wrote:
>
> > does anyone know where to find some information or know how to make my
> > E4500 talk to my A5000?
>
> Unfortunately, you are currently out of luck. The SBUS
> fc drivers are in a very poor state and don't work for
> most people.
>
> Ben Collins is trying to get the SOC/SOCAL driver working
> with his array on his E4500. He'll certainly post results
> if he makes any progress.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next reply other threads:[~2005-03-15 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 12:34 Ben Collins [this message]
2005-03-16 2:27 ` fc-al and A5000 Dennis Jenkins
2005-05-26 17:29 ` Patrick Finnegan
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=20050315123416.GA3857@internal \
--to=bcollins@debian.org \
--cc=sparclinux@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.