From: Chris Newport <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: fix compile failure ("struct resource" related)
Date: Thu, 03 Mar 2005 16:25:16 +0000 [thread overview]
Message-ID: <42273A6C.4010704@netunix.com> (raw)
In-Reply-To: <20050301134440.05ae1152.akpm@osdl.org>
Dennis Jenkins wrote:
>Does this mean that I will be able to successfully
>compile a 2.6 kernel using gcc 3.3.5 on my sparc64
>gentoo box? Yeah!
>
>now.. If only I (or someone) could fix the fcal/socal
>driver. I even tried using the socal_asm.h firmware
>patch derived from the Solaris 10 "socal" firmware.
>No luck. :(
>
>
First check if you should be using the soc or socal drivers.
A handbook search at sunsolve for the barcode on your board will
tell you if it is FC/25 or FCAL - just take the first 7 chars and insert
a dash like this 501-1234. The SSA1xx arrays with 3 pull-out drawers
each containing 10 drives need the soc card and drivers. Later arrays
such as the A5000 need the socal card and drivers.
The soc/pluto stuff has not been maintained since 2.2.x and AFAIK this
is also true for socal.
Take a look at http://www.splack.org/fibrechan.html for the lowdown on
how to get soc working on 2.2.x, once you have that working it should
be possible to port the existing drivers to 2.4 and then 2.6.
next prev parent reply other threads:[~2005-03-03 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503012129.11840.adobriyan@mail.ru>
2005-03-01 21:44 ` [PATCH] sparc: fix compile failure ("struct resource" related) Andrew Morton
2005-03-01 21:44 ` Andrew Morton
2005-03-03 2:00 ` William Lee Irwin III
2005-03-03 2:00 ` William Lee Irwin III
2005-03-03 13:06 ` Dennis Jenkins
2005-03-03 16:25 ` Chris Newport [this message]
2005-03-03 17:19 ` Dennis Jenkins
2005-03-03 19:40 ` Baurzhan Ismagulov
2005-03-03 23:21 ` Chris Newport
2005-03-03 23:39 ` Dennis Jenkins
2005-03-04 7:06 ` David S. Miller
2005-03-04 11:10 ` Chris Newport
2005-03-04 14:25 ` Dennis Jenkins
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=42273A6C.4010704@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.