Hi Rob,
CC linux-sh
On Wed, Jan 8, 2025 at 11:40 PM Rob Landley wrote:
> The sh2eb turtle board uses JCORE_EMAC which is still an out of tree
> driver. It's not secret, just too ugly to go upstream: done by a
> contractor and never cleaned up, full of half-finished IEEE-1588 support
> and so on.
On Wed, 8 Jan 2025, Rob Landley wrote:
On 1/8/25 08:59, Alex Bennée wrote:
Rob Landley writes:
On 1/7/25 12:05, Alex Bennée wrote:
Stafford Horne writes:
I have not used -hda before, do you have it working with other targets?
According to the qemu docs in qemu-options.hx. I see:
Us
On Wed, 8 Jan 2025, Rob Landley wrote:
On 1/8/25 07:01, BALATON Zoltan wrote:
On Tue, 7 Jan 2025, Rob Landley wrote:
What's the alternative to -hda you suggest for that?
Can I do "./run-qemu.sh -drive file=blah.img" without the rest? Perhaps
specify all the details in the script and then opti
On 1/8/25 07:01, BALATON Zoltan wrote:
On Tue, 7 Jan 2025, Rob Landley wrote:
What's the alternative to -hda you suggest for that?
Can I do "./run-qemu.sh -drive file=blah.img" without the rest?
Perhaps specify all the details in the script and then optionally add
an extra argument at the end
On 1/8/25 10:26, Geert Uytterhoeven wrote:
Hi Rob,
On Wed, Jan 8, 2025 at 5:23 PM Rob Landley wrote:
On 1/8/25 02:24, Geert Uytterhoeven wrote:
On Tue, Jan 7, 2025 at 11:53 PM Rob Landley wrote:
Microblaze has no /dev/?da (as in there's no device I could attach it to
even with the long opti
On 1/8/25 08:59, Alex Bennée wrote:
Rob Landley writes:
On 1/7/25 12:05, Alex Bennée wrote:
Stafford Horne writes:
I have not used -hda before, do you have it working with other targets?
According to the qemu docs in qemu-options.hx. I see:
Use file as hard disk 0, 1, 2 or 3 image o
Hi Rob,
On Wed, Jan 8, 2025 at 5:23 PM Rob Landley wrote:
> On 1/8/25 02:24, Geert Uytterhoeven wrote:
> > On Tue, Jan 7, 2025 at 11:53 PM Rob Landley wrote:
> >> Microblaze has no /dev/?da (as in there's no device I could attach it to
> >> even with the long option, I'd have to use NBD), sh4eb
On 1/8/25 02:24, Geert Uytterhoeven wrote:
Hi Rob,
On Tue, Jan 7, 2025 at 11:53 PM Rob Landley wrote:
Microblaze has no /dev/?da (as in there's no device I could attach it to
even with the long option, I'd have to use NBD), sh4eb has -hda is
working but it's having some endianness hiccup with
Rob Landley writes:
> On 1/7/25 12:05, Alex Bennée wrote:
>> Stafford Horne writes:
>>> I have not used -hda before, do you have it working with other targets?
>>>
>>> According to the qemu docs in qemu-options.hx. I see:
>>>
>>> Use file as hard disk 0, 1, 2 or 3 image on the default bus o
On Tue, 7 Jan 2025, Rob Landley wrote:
On 1/7/25 12:05, Alex Bennée wrote:
Stafford Horne writes:
I have not used -hda before, do you have it working with other targets?
According to the qemu docs in qemu-options.hx. I see:
Use file as hard disk 0, 1, 2 or 3 image on the default bus of
Hi Rob,
On Tue, Jan 7, 2025 at 11:53 PM Rob Landley wrote:
> Microblaze has no /dev/?da (as in there's no device I could attach it to
> even with the long option, I'd have to use NBD), sh4eb has -hda is
> working but it's having some endianness hiccup with the network card
> (works in sh4 but not
On 1/7/25 12:05, Alex Bennée wrote:
Stafford Horne writes:
I have not used -hda before, do you have it working with other targets?
According to the qemu docs in qemu-options.hx. I see:
Use file as hard disk 0, 1, 2 or 3 image on the default bus of the
emulated machine (this is for e
On 1/7/25 11:31, Stafford Horne wrote:
On Tue, Jan 07, 2025 at 05:56:52AM -0600, Rob Landley wrote:
On 12/31/24 19:19, Rob Landley wrote:
On 12/23/24 07:05, Stafford Horne wrote:
The kernel config looks like it should have virt block device
support, but
...
-device virtio-blk-device,driv
Stafford Horne writes:
> On Tue, Jan 07, 2025 at 05:56:52AM -0600, Rob Landley wrote:
>> On 12/31/24 19:19, Rob Landley wrote:
>> > On 12/23/24 07:05, Stafford Horne wrote:
>> > > > The kernel config looks like it should have virt block device
>> > > > support, but
>> ...
>> > > -device virtio
On Tue, Jan 07, 2025 at 05:56:52AM -0600, Rob Landley wrote:
> On 12/31/24 19:19, Rob Landley wrote:
> > On 12/23/24 07:05, Stafford Horne wrote:
> > > > The kernel config looks like it should have virt block device
> > > > support, but
> ...
> > > -device virtio-blk-device,drive=d0 -drive
> > >
On 12/31/24 19:19, Rob Landley wrote:
On 12/23/24 07:05, Stafford Horne wrote:
The kernel config looks like it should have virt block device
support, but
...
-device virtio-blk-device,drive=d0 -drive
file=${DISK},id=d0,if=none,format=qcow2
-drive file=file.img,format=raw,id=hd0 -device vi
On 12/23/24 07:05, Stafford Horne wrote:
The kernel config looks like it should have virt block device support, but
nether -hda README nor "-drive file=README,format=raw,id=hd0 -device
virtio-blk-device,drive=hd0" seem to be wiring it up in qemu where the
kernel can find it?
The default virt_de
On 11/24/24 00:50, Stafford Horne wrote:
Speaking of which, is there a way to get or1k to exit the emulator? I told
the kernel to reboot but it says "reboot failed, system halted" and hangs
instead of exiting qemu. (My testroot runs qemu under "timeout -i 10" to
kill it after 10 seconds of inacti
18 matches
Mail list logo
