From: Chris Newport <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: fix compile failure ("struct resource" related)
Date: Fri, 04 Mar 2005 11:10:31 +0000 [thread overview]
Message-ID: <42284227.9000308@netunix.com> (raw)
In-Reply-To: <20050301134440.05ae1152.akpm@osdl.org>
David S. Miller wrote:
>>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.
>>
>>
>
>Not true if you boot from the SOC/SOCAL disks, OBP will load it's
>own firmware which is very slow and has tons of debugging enabled
>in it.
>
>
Oook - that is EVIL.
We really do not want to taint the kernel with Sun's FCode.
I think we could work around this, the OBP is all in FORTH
so we should be able to replace the offending upload function
with a one line null function in nvramrc.
Would this work ?.
Caveat - this theory comes from the decaying memory of a 60
year old Fortran hacker and needs to be properly researched
in the OBP documentation. Significant ForthHackery maybe required.
next prev parent reply other threads:[~2005-03-04 11:10 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
2005-03-03 23:39 ` Dennis Jenkins
2005-03-04 7:06 ` David S. Miller
2005-03-04 11:10 ` Chris Newport [this message]
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=42284227.9000308@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.