J. Mayer wrote:
On Wed, 2005-05-25 at 21:59 +0300, Tero Kaarlela wrote:
I have just realized that when running in LE mode in_asm dump is not
useful because it shows code in BE-format. I'll try to make it print in
LE format. And those invalid opcodes is this because after OS/2 crashes
Qemu
On Wed, 2005-05-25 at 21:59 +0300, Tero Kaarlela wrote:
> I have just realized that when running in LE mode in_asm dump is not
> useful because it shows code in BE-format. I'll try to make it print in
> LE format. And those invalid opcodes is this because after OS/2 crashes
> Qemu tries to start
I have just realized that when running in LE mode in_asm dump is not
useful because it shows code in BE-format. I'll try to make it print in
LE format. And those invalid opcodes is this because after OS/2 crashes
Qemu tries to start its own code but crashes because before this
Processor should
Hi,
I took a look at qemu in_asm & cpu debugging with OS/2 bootloader
under Qemu -prep. And there is something weird happening in my opinion:
This happens after boot.cfg has been gone through and kernel bootstrap
task should start:
IN:
0xf0107068: .long 0x10009d81
0xf010706c: tdi0,
