From: "C.Newport" <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: future of drivers/fc4/
Date: Wed, 25 Aug 2004 18:34:39 +0000 [thread overview]
Message-ID: <200408251934.39486.crn@netunix.com> (raw)
In-Reply-To: <412CB453.2050504@sms-softwaretechnik.de>
On Wednesday 25 August 2004 4:46 pm, Matthias Schulz wrote:
> Hi,
>
> I saw your posts on vger.kernel.org but it doesn't seem to find a lot of
> reaction there.
>
> I do have a lot of hardware to test this (S1000E, SSA 100, E5000,
> A5000). A while back, I had the 2.2.20 kernel running with my SS1000E
> and the SSA 100 attached. Worked fine. But any version of Linux later
> than 2.2.20 didn't do it.
>
> Could it be, that the mayjor changes from 2.2 -> 2.4 (SMP, scsi etc.)
> are the REAL reason for that ?
>
> I don't think it has to do woth hardware issues other than having the
> right firmwar on either the soc-board (1.33) and the SSA (3.??).
>
> Did you get any further ?
>
> Did you have it running with 2.2.??
I have the soc/pluto combination working here with 2.2.20 on the SS1000E
but I have not looked at this in a while. The problem is that there were major
changes to the scsi subsystem in the 2.2 to 2.4 transition and noboby did
any work on the soc or socal stuff. The changes are rather major so
someone with good kernel skills needs to spend some time updating this.
Does anyone know if the fcal based Ultrasparcs such as the SF1000 are
also affected ?.
next prev parent reply other threads:[~2004-08-25 18:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 15:46 future of drivers/fc4/ Matthias Schulz
2004-08-25 15:51 ` William Lee Irwin III
2004-08-25 18:34 ` C.Newport [this message]
2004-08-25 19:15 ` David S. Miller
2004-08-30 18:01 ` Aaron Wirtz
-- strict thread matches above, loose matches on Subject: below --
2004-06-20 16:03 Christoph Hellwig
2004-06-20 16:03 ` Christoph Hellwig
2004-06-20 18:40 ` David S. Miller
2004-06-20 18:40 ` David S. Miller
2004-06-20 20:05 ` C.Newport
2004-06-20 20:05 ` C.Newport
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=200408251934.39486.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.