From: Matthias Schulz <schulz@sms-softwaretechnik.de>
To: sparclinux@vger.kernel.org
Subject: Re: future of drivers/fc4/
Date: Wed, 25 Aug 2004 15:46:27 +0000 [thread overview]
Message-ID: <412CB453.2050504@sms-softwaretechnik.de> (raw)
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.??
Sincerly,
Matthias Schulz
C.Newport schrieb:
> On Sunday 20 June 2004 7:40 pm, David S. Miller wrote:
>
>>On Sun, 20 Jun 2004 18:03:53 +0200
>>
>>Christoph Hellwig <hch@lst.de> wrote:
>>
>>>The SUN FCAL support has been non-working for ages and needs major work
>>>to keep up with scsi API changes. Is anyone planning to ressurect it
>>>midterm? If not I'd like to remove it from the tree.
>>
>>Feel free to remove it, interested parties can resurrect the source
>>really easily.
>
>
> If it is that easy could someone tell me what needs doing please ?
> I am NOT a kernel programmer but given a little handholding and
> a list of what to do I can build and test it here.
>
> I also have a spare set of hardware if someone in the UK with the
> needed skills would like it. Sorry, but the disk array is a bit heavy to
> ship elsewhere. If someone already has the array I will mail a card
> anywhere.
>
> We need this if we are ever to get the Sun4D working again.
> Keith now has a contact for the missing info to get Sun4D working
> properly, but without the fc, soc and pluto it will be rather restricted in
> usefulness.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next reply other threads:[~2004-08-25 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 15:46 Matthias Schulz [this message]
2004-08-25 15:51 ` future of drivers/fc4/ William Lee Irwin III
2004-08-25 18:34 ` C.Newport
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=412CB453.2050504@sms-softwaretechnik.de \
--to=schulz@sms-softwaretechnik.de \
--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.