Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-11-23 Thread Stafford Horne
On Sat, Nov 23, 2024 at 11:18:53PM -0600, Rob Landley wrote: ... > I'm attempting to regression test as many targets as I can to get consistent > basic behavior out of: > > https://landley.net/bin/mkroot/0.8.11/ > > I'm trying to get a new release out with the 6.12 kernel which is why I'm > rev

Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-11-23 Thread Rob Landley
On 11/23/24 02:28, Stafford Horne wrote: Just a guess, but given the alignment change, I suspect it's barfing on the statically linked initramfs? That seems the most likely step to go off the rails given the failing patch is a symbol alignment change in the flattened device tree plumbing, and I t

Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-11-23 Thread Stafford Horne
On Fri, Nov 22, 2024 at 06:54:21PM -0600, Rob Landley wrote: > On 11/22/24 10:35, Stafford Horne wrote: > > > I just regression tested linux-6.12 against qemu-9.2.0-rc1 and I'm still > > > getting no output from or1k, with the current image or the old or1k > > > release > > > image that worked und

Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-11-22 Thread Rob Landley
On 11/22/24 10:35, Stafford Horne wrote: I just regression tested linux-6.12 against qemu-9.2.0-rc1 and I'm still getting no output from or1k, with the current image or the old or1k release image that worked under old qemu versions. I tried applying your serial patch to current qemu, and it made

Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-11-22 Thread Stafford Horne
On Thu, Nov 21, 2024 at 04:32:25PM -0600, Rob Landley wrote: > On 9/16/24 02:21, Stafford Horne wrote: > > On Wed, Sep 11, 2024 at 12:42:58AM -0500, Rob Landley wrote: > > > Grab this tarball, extract it, and ./run-qemu.sh. It's a simple > > > linux+initramfs image that boots to a shell prompt. > >

Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-11-21 Thread Rob Landley
On 9/16/24 02:21, Stafford Horne wrote: On Wed, Sep 11, 2024 at 12:42:58AM -0500, Rob Landley wrote: Grab this tarball, extract it, and ./run-qemu.sh. It's a simple linux+initramfs image that boots to a shell prompt. https://landley.net/bin/mkroot/latest/or1k.tgz QEMU 7.0.0 ran that linux-o

Re: QEMU commit 0a923be2f642 broke my or1k image.

2024-09-16 Thread Stafford Horne
Hi Rob, Sorry, I haven't had much time to sit down and work on this mail in the last two weeks but wanted to get somethign back to you. Here it goes. On Wed, Sep 11, 2024 at 12:42:58AM -0500, Rob Landley wrote: > Grab this tarball, extract it, and ./run-qemu.sh. It's a simple > linux+initramfs i

QEMU commit 0a923be2f642 broke my or1k image.

2024-09-10 Thread Rob Landley
Grab this tarball, extract it, and ./run-qemu.sh. It's a simple linux+initramfs image that boots to a shell prompt. https://landley.net/bin/mkroot/latest/or1k.tgz QEMU 7.0.0 ran that linux-or1k image, but newer qemu does not. I besected the issue to qemu commit 0a923be2f642, and it's still brok