From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: socal
Date: Thu, 01 Jan 2004 00:54:50 +0000 [thread overview]
Message-ID: <200401010054.50573.crn@netunix.com> (raw)
In-Reply-To: <200312311429.26841.awirtz@novapointe.com>
On Wednesday 31 December 2003 11:57 pm, Aaron Wirtz wrote:
> I have a high suspicion that the reason the current drivers don't work may
> not be the version of the drivers, but the version of the ucode that I am
> trying to use with them. If the ucode I am using implememnts an API other
> than what whe driver expects, that might be the issue.
The fcode and ucode will not have changed significantly.
I would rather suspect that the drivers have not been updated to
keep up with the 2.4.x kernel changes.
drivers/fc4/socal.c was last updated in Feb 1999 which puts it
back in 2.2.x land somewhere.
There are also problems with soc.c in 2.4.x but I have not looked
at this because my SS1000E has other issues with 2.4 anyway
so it is still on 2.2.20
BTW, Pete, is there any chance that the sun4d issues might come
to the top of the todo list sometime ?.
It would be nice to get these boatanchors working, especially in
view of Solaris 8 being the last supported release for them.
next prev parent reply other threads:[~2004-01-01 0:54 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 ` socal C.Newport
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 ` C.Newport [this message]
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=200401010054.50573.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.