From: Chris Newport <crn@netunix.com>
To: sparclinux@vger.kernel.org
Subject: Re: Patch: SILO/first-isofs/isofs.c (Fix Sun4c)
Date: Wed, 23 Feb 2005 01:00:19 +0000 [thread overview]
Message-ID: <421BD5A3.7030705@netunix.com> (raw)
In-Reply-To: <20050222162933.GA25092@internal>
I was getting too bogged down in the second/ code so I tried
simply using the second.b from older versions.
second.b from silo 1.2.6 works fine on all sun4c and sun4m
but fails on sun4u
second.b from silo 1.4.5 and 2.4.8 both screw up on sun4c
So it looks like the sun4c / prom v0 support got broken between
1.2.6 and 1.4.5
Does this point to any smoking guns ?.
Ben Collins wrote:
>Thanks. Committed to the repo. I'll try to get a new version out soon.
>
>As for the next error, it looks like it is trying to load it to the
>physical address of 0x0, which is a bad thing. That overwrites silo
>itself.
>
>So I guess there is an error in silo (not first-isofs). Check the
>memory_find() function in second/memory.c and see why it is using a
>physical address of 0x0.
>
>On Tue, Feb 22, 2005 at 04:55:10PM +0000, Chris Newport wrote:
>
>
>>This small patch fixes silo-1.4.8/first-isofs/isofs.c
>>Copying an int into a string is not a good idea.
>>
>>Sun4c now loads second.b and the kernel, but still
>>barfs loading the initrd.
>>
>>boot:
>>Loaded kernel version 2.4.27
>>Loading initial ramdisk (905216 bytes at 0x0 phys, 0x300000 virt)...
>>Data Access ExceptionType b (boot), c(continue), or n (new command mode)
>>
>>
>>Does anyone know what is wrong here ?
>>
>>
>>
next prev parent reply other threads:[~2005-02-23 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 16:29 Patch: SILO/first-isofs/isofs.c (Fix Sun4c) Ben Collins
2005-02-22 16:55 ` Chris Newport
2005-02-23 1:00 ` Chris Newport [this message]
2005-02-23 1:53 ` Ben Collins
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=421BD5A3.7030705@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.