All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:21:15 +0000	[thread overview]
Message-ID: <42279BEB.5060609@netunix.com> (raw)
In-Reply-To: <20050301134440.05ae1152.akpm@osdl.org>

Dennis Jenkins wrote:

>>The soc/pluto stuff has not been maintained since
>>2.2.x and AFAIK this 
>>is also true for socal.
>>    
>>
>
>Yup, I read that too.  And immediately there after I
>downloaded the last 2.2 kernel and tried to compile
>it.  Unfortunately for me, GCC 3.3.5 choked heavily on
>it.  I will try again when I figure out how to get
>Gentoo to downgrade gcc.  The question is, what
>version should I downgrade to?
>  
>
I have no idea about Gentoo versions, but Splack 8.0 has a working 2.2 
kernel with soc and socal modules. Everything you need to experiment 
with 2.4 is there, but the toolset and compiler are too old for 2.6
In general, you should not need to have the Sun firmware in your
drivers, just upload them to the card and array from Solaris and they
will stay there in nvram. This avoids contaminating Linux with Sun's code.
The procedure for socal is similar to my procedure for soc, take a look 
at the Solaris man pages for luxadm etc.



  parent reply	other threads:[~2005-03-03 23:21 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
2005-03-03 17:19   ` Dennis Jenkins
2005-03-03 19:40   ` Baurzhan Ismagulov
2005-03-03 23:21   ` Chris Newport [this message]
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=42279BEB.5060609@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.