All of lore.kernel.org
 help / color / mirror / Atom feed
From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: socal
Date: Wed, 31 Dec 2003 23:07:09 +0000	[thread overview]
Message-ID: <200312312307.09851.crn@netunix.com> (raw)
In-Reply-To: <200312311429.26841.awirtz@novapointe.com>

On Wednesday 31 December 2003 10:29 pm, Aaron Wirtz wrote:
> I have a Sun e3500 and I am trying to get the linux socal/fcal drivers
> working.  I have done a bit of reasearch and have tried several different
> linux kernel versions and different socal microcode versions to no avail.
> Does anyone know of a patch that fixes the broken socal/fcal drivers under
> 2.4.x or, failing that, does anyone know what version of the linux kernel
> and the Solaris microcode Jakub was using in the past (1999) when he had
> the driver working?

Have you tried checking the firmware Fcode ?.
http://www.splack.org/fibrechan.html has the procedure for the soc
cards, the socal stuff is very similar.


  reply	other threads:[~2003-12-31 23:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 22:29 socal Aaron Wirtz
2003-12-31 23:07 ` C.Newport [this message]
2003-12-31 23:18 ` socal Keith M Wesolowski
2003-12-31 23:19 ` socal Aaron Wirtz
2003-12-31 23:26 ` socal Keith M Wesolowski
2003-12-31 23:35 ` socal Pete Zaitcev
2003-12-31 23:43 ` socal Aaron Wirtz
2003-12-31 23:43 ` socal Pete Zaitcev
2003-12-31 23:49 ` socal Aaron Wirtz
2003-12-31 23:57 ` socal Aaron Wirtz
2004-01-01  0:54 ` socal C.Newport
2004-01-01  1:26 ` socal C.Newport
2004-01-01  1:34 ` socal Aaron Wirtz
2004-01-01  2:06 ` socal C.Newport
2004-01-01  2:41 ` socal Pete Zaitcev
2004-01-01  2:57 ` socal C.Newport
2004-01-01  3:10 ` socal Aaron Wirtz
2004-01-06  3:06 ` socal Aaron Wirtz

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=200312312307.09851.crn@netunix.com \
    --to=crn@netunix.com \
    --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.