All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: sparclinux@vger.kernel.org
Subject: Re: SILO Issues on an E4900
Date: Thu, 24 Nov 2016 22:04:57 +0000	[thread overview]
Message-ID: <c2bf1974-0c77-fbb9-3a94-d2e48cccecd5@ilande.co.uk> (raw)
In-Reply-To: <62477e32a682342782e652fcfdbf9fb5@triadic.us>

On 24/11/16 21:26, vincent@cojot.name wrote:

> A while back I stumbled onto an old post talking about the 'Illegal
> instruction' issue with SILO on serengeti machines:
> 
> http://helenos-blog.pavel-rimsky.cz/?p=3
> 
> Any thoughts?
> 
> Note that I have not personally verified that it works or not (I sold my
> US-IIICu sb2k some time ago already...)
> 
> My 2c,
> 
> Vincent

FWIW we have a similar hack in OpenBIOS for a.out binaries which rears
its head when trying to boot NextSTEP in QEMU:
https://github.com/openbios/openbios/blob/master/libopenbios/aout_load.c.
For a.out binaries we relocate the binary back down over its header
after load so we can execute directly at 0x4000 (load-base).

This was modelled after observing similar code in the official Sun
OpenBOOT implementation of init-program which can be found here:
https://github.com/openbios/openboot/blob/master/obp/arch/sun4u/go.fth.

Probably the first thing to check is that the a.out magic is being
generated correctly in SILO to match the above code in order to trigger
the relocation, which in itself is likely a hold-over from the very
early days of OpenBOOT.


ATB,

Mark.


  parent reply	other threads:[~2016-11-24 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  0:02 SILO Issues on an E4900 alexmcwhirter
2016-11-24  9:35 ` Louis Liu
2016-11-24 10:00 ` John Paul Adrian Glaubitz
2016-11-24 16:10 ` David Miller
2016-11-24 16:22 ` John Paul Adrian Glaubitz
2016-11-24 21:26 ` vincent
2016-11-24 22:04 ` Mark Cave-Ayland [this message]
2016-11-25  8:14 ` Louis Liu
2016-11-25 20:30 ` Louis Liu

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=c2bf1974-0c77-fbb9-3a94-d2e48cccecd5@ilande.co.uk \
    --to=mark.cave-ayland@ilande.co.uk \
    --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.