qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Rob Landley <rob@landley.net>,
	qemu-devel@nongnu.org, jeff@coresemi.io,
	peter.maydell@linaro.org, glaubitz@physik.fu-berlin.de
Subject: Re: Please put qemu-system-sh4eb back.
Date: Thu, 24 Oct 2024 07:44:35 +0200	[thread overview]
Message-ID: <9f8b2357-a28a-4b80-aa5c-ff1725e364d9@redhat.com> (raw)
In-Reply-To: <d6755445-1060-48a8-82b6-2f392c21f9b9@landley.net>

On 24/10/2024 02.11, Rob Landley wrote:
> I use it, and ship system images for it:
> 
>    https://landley.net/bin/mkroot/latest/sh4eb.tgz

Oh, that's interesting, I've been told that the r2d machine does not work in 
big endian mode:

  https://lore.kernel.org/qemu-devel/87a5fwjjew.wl-ysato@users.sourceforge.jp/

But yes, your binaries apparently work there, so sorry for the confusion.
I'll send a patch to revert the removal.

  Thomas

> And here's me recentish-ly debugging an issue via it:
> 
>   https://landley.net/notes-2024.html#24-05-2024
> 
> (Compile/test cycles are WAY easier there than copying files onto an sd card 
> to test on actual hardware.)
> 
> There was a big-endian issue breaking r2d last year, but it also broke big 
> endian mips and some other targets too, and it got fixed. The binary I built 
> a few months ago was working fine for me with vanilla qemu git source? (I 
> don't _think_ I had local changes?) I can try to build the version removed 
> to check that...
> 
> Yes I should be better about pushing local patches upstream. For example, 
> here's the kernel patch I use to run fdpic binaries under qemu:
> 
> https://landley.net/bin/mkroot/latest/linux-patches/0002-sh4-fdpic.patch
> 
> Which lets you enable the FDPIC loader on an mmu kernel, which is useful for 
> testing j-core userspace under qemu.
> 
> Rob
> 



  parent reply	other threads:[~2024-10-24  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  0:11 Please put qemu-system-sh4eb back Rob Landley
2024-10-24  0:14 ` Rob Landley
2024-10-24  5:44 ` Thomas Huth [this message]
2024-10-24  9:27   ` John Paul Adrian Glaubitz
2024-10-25 16:06   ` 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=9f8b2357-a28a-4b80-aa5c-ff1725e364d9@redhat.com \
    --to=thuth@redhat.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=jeff@coresemi.io \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    /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).