From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Linux-SH <linux-sh@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: can someone solve string_32.h issue for SH ?
Date: Tue, 17 Dec 2019 09:43:37 +0100 [thread overview]
Message-ID: <CAMuHMdXX7wEBSmj-5G-Ya+n1FKMENRxpHuEhh1rmSV9zME_v=g@mail.gmail.com> (raw)
In-Reply-To: <8736djgxg2.wl-kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Tue, Dec 17, 2019 at 9:37 AM Kuninori Morimoto
<kuninori.morimoto.gx@renesas.com> wrote:
> Unfortunately, I can't test it :(
> Can someone test it ?
make rts7751r2dplus_defconfig
qemu-system-sh4 qemu-system-sh4 -M r2d -serial null -serial mon:stdio \
-nographic -no-reboot -m 256 \
-append "panic=1 HOST=sh4 console=ttySC1 noiotrap" \
-kernel arch/sh/boot/zImage
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-12-17 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 6:09 can someone solve string_32.h issue for SH ? Kuninori Morimoto
2019-12-17 8:29 ` Geert Uytterhoeven
2019-12-17 8:37 ` Kuninori Morimoto
2019-12-17 8:43 ` Geert Uytterhoeven [this message]
2019-12-17 8:40 ` Geert Uytterhoeven
2019-12-17 8:51 ` Kuninori Morimoto
2019-12-17 9:09 ` Karl Nasrallah
2019-12-17 22:16 ` Karl Nasrallah
2019-12-17 23:13 ` Rich Felker
2019-12-17 8:50 ` Geert Uytterhoeven
[not found] <339916914.636876.1576627652112.ref@mail.yahoo.com>
2019-12-18 0:07 ` Karl Nasrallah
2019-12-18 2:01 ` Kuninori Morimoto
2019-12-18 3:56 ` Karl Nasrallah
2019-12-18 5:21 ` Kuninori Morimoto
2019-12-18 6:06 ` Karl Nasrallah
2019-12-18 7:28 ` Kuninori Morimoto
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='CAMuHMdXX7wEBSmj-5G-Ya+n1FKMENRxpHuEhh1rmSV9zME_v=g@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=dalias@libc.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).