From: Rob Landley <rob@landley.net>
To: linux-sh@vger.kernel.org
Subject: Re: Bootable sh4 qemu images.
Date: Mon, 11 Jan 2016 20:42:17 +0000 [thread overview]
Message-ID: <569413A9.6010301@landley.net> (raw)
In-Reply-To: <568FFC28.2010409@landley.net>
On 01/11/2016 12:02 PM, Peter Zijlstra wrote:
> On Fri, Jan 08, 2016 at 12:12:56PM -0600, Rob Landley wrote:
>> The sh4 images are "qemu-system-sh4.tar.gz", the current release (1.4.4)
>> is based on musl-libc and kernel 4.2
>
>> P.S. Sorry I've fallen a couple kernel versions behind, I'm trying to
>> catch up
>
> Ah, so you've not yet found if I broken SH in 4.3 with:
>
> b31fdac2a921 ("sched, sh: Fold finish_arch_switch() into switch_to()")
>
> :-)
It's working fine with 4.3, native compiling static binaries under musl
and everything:
(sh4:3) / $ gcc /usr/src/thread-hello2.c -lpthread --static
(sh4:3) / $ ./a.out
Hello world!
(sh4:3) / $ cat /proc/version
Linux version 4.3.0 (landley@halfbrick) (gcc version 4.2.1) #1 Mon Jan
11 13:24:23 CST 2016
(sh4:3) / $ cat /proc/cpuinfo
machine : RTS7751R2D
processor : 0
cpu family : sh4
cpu type : SH7751R
cut : unknown
cpu flags : fpu ptea
cache type : split (harvard)
icache size : 4KiB (2-way)
dcache size : 4KiB (2-way)
address sizes : 29 bits physical
bogomips : 120.00
(sh4:3) / $
(Dynamic linked binaries are segfaulting but that's something I did
wrong when switching to musl. My toolchain is the last gplv2 releases of
everything, patched until they work. Something needs a patch, apparently.)
I might cut a release with _just_ the new kernel version to catch up...
Rob
next prev parent reply other threads:[~2016-01-11 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 18:12 Bootable sh4 qemu images Rob Landley
2016-01-11 18:02 ` Peter Zijlstra
2016-01-11 20:42 ` Rob Landley [this message]
2016-01-12 7:19 ` Rob Landley
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=569413A9.6010301@landley.net \
--to=rob@landley.net \
--cc=linux-sh@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.