Hi,
I would like to modify Qemu code so that I can log guest memory
reads on certain area of memory. Guest is PPC PREP and area I like to
monitor is Residual data area. How should I do this? Where to start?
Tero
This patches residual data structures for OHW Prep.
ftp://ftp.software.ibm.com/rs6000/technology/spec/RESIDUAL.PS has been used as
reference document here. Now the Vital product data shows correctly with guest
Linux lsresidual utility.(instead of segmentation fault before patching). Also
memory
What is current condition of Qemu-PPC prep? I tried running debian sarge image
from Freeoszoo but it doesnt boot(freezes when figuring out PTYs). 0.9.0 seems
to boot this ok. Also there is a problem with Little endian mode since 0.9.0
boots OS/2 PPC edition over LE change and CVS version crashes
J. Mayer wrote:
Fabrice has a fix for this.
You can also edit hw/ide.c and comment the one-line Darwin hack (easy to
find).
If this is what you mean:
#ifdef TARGET_PPC
/* XXX: currently a workaround for Darwin/PPC. Need to check
the IDE spec to see if it is correct */
Hi,
I have been running debian 3.1r0a under Qemu-system-ppc(PREP). I just
noted few coupleof things:
1. Top gives really absurd values for processor % for few seconds then
it crashes see http://personal.inet.fi/koti/ekasorvaus/qemuppc.png
2. If I launch with -cdrom sarge.iso and start usin
Hi,
I have been trying to find out what is problem with changing
system-ppc to Little-endian here I have taken two examples from qemu
debug logs:
Example 1:
IN: MSR state here is (MSR 00012030)
0x00100860: stbr24,0(r26)
0x00100864: rfi
IN: MSR state here is(MSR 000
Tilman Sauerbeck wrote:
Hi,
I'm trying to run qemu-system-ppc on a x86 box (Linux 2.6.12, gcc
3.4.3), but the SDL window that qemu opens just stays black, there's no
output at all (nothing on stdout either).
For example, I tried to run qemu-system-ppc with the linux-ppc image
from freeoszoo.org
Hi,
I am currently trying to use GDB for debugging PPC guest. What I
would like to do is to step one instruction but if I give command
'nexti' from GDB affect is exactly same than if i give 'continue'.
Running does not stop after 1 instruction. My GDB config:
GD
Stefano Marinelli wrote:
On Sat, 25 Jun 2005 19:23:01 +0300, Tero Kaarlela wrote:
I've put a new updated image. It works. It's on the freeoszoo
Of reactos not linuxppc?
Reactos. If I'll have some time, in the next days, I could prepare a ppc
sarge image.
Stefano Marinelli wrote:
On Fri, 24 Jun 2005 14:21:04 -0500, <[EMAIL PROTECTED]> wrote:
We know for certain the ReactOS image doesn't work anymore and needs to be
replaced. I don't think anybody has gotten around to replacing it, though.
And since ReactOS is so small and installs so easily
Hi,
I tried to boot linuxppc image from freeoszoo with QemuCVS. kernel
boots ok but then I get errors that it cant read filesystem from dev hda.
Also tried with 0.7.0 and it freezes at: Freeing unused kernel memory
my boot command line was: 0.7.0 qemu-system-ppc -prep -kernel
zimage.pr
e 00 - 10 - 01.
Tero Kaarlela
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
ecs user wrote:
Tero Kaarlela wrote:
Well you might start Qemu with option -d in_asm
I do not see that "-d in_asm" option for running QEMU.
Is "-d in_asm" a run option or is a compile of qemu
option.
From Qemu manual section 3.3 Invocation:
`-d'
Ou
e a look at BOCHS emulator page
because Dimitri Froloff made few fixes to boot OS/2 under it(some of
these were memory handling related fixes). He made these fixes lately.
Tero Kaarlela
___
Qemu-devel mailing list
Qemu-devel@nong
many
others in this way:
Memory "filling" is started from "top" to "bottom"
?(highest address first)
Tero Kaarlela
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
ecs user wrote:
Tero Kaarlela wrote:
Could this be because OS/2 can't handle this much
ram(128mb).
eComStation can do at least 2GB and with updates 4GB
OS/2 Warp4 should be able to handle 256MB
Well I was talking about OS/2 PowerPC edition (Released december 1995)
During that
I am having problems with using GNU debugger with qemu. when I use
option -s qith qemu qemu gives:
waiting for gdb connection on port 1234
but it doesnt wait just goes on. System is latest Debian with loopback
networking only.
resolv.conf has following : nameserver 127.0.0.1
So any ideas w
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
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
0
SRR0 0xf0107068 SRR1 0x0031 DECR=0x22d014be
reservation 0x
invalid/unsupported opcode: 3c - 18 - 1c (f730) 0x0700 0
So any ideas what might be reason for this?
Tero Kaarlela
___
Qemu-devel mailing list
Qemu-devel@nongn
if (val & 0x02) {
printf("Switching to Little Endian mode...");
/* abort(); */
?
Tero Kaarlela
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
J. Mayer wrote:
2. on debug 2. What is this unaffected IO port 838 it tries to read &
write ?
This port is not documented in the PREP specification. You should check
in the Linux kernel to see if this port seems important. Or you may take
a look to Motorola PowerStack documentation: tho
Hi,
I have made some modifications to PPC PREP booting to get OS/2
bootloader working. Now I hopefully have made some progress (it isn't
working yet but has gone forward on my opinion). So I have few
questions at the moment:
1. on debug 1. Is the opcode really invalid or just unsuppor
2. Booted with qemu-system-ppc -dummy-net -nographic -prep -cdrom os2.iso
(and giving boot device ide_cdrom2 + filesystem FAT_HARDDISK)
Boot: 00ec0500 47ff0800
Bootinfos at : 20
Now boot it... (0)
stack: 5bfff70 malloc_base: 0 0x0580 0x0600
PREP boot... 15ea00 1000
Ok,
What I have made now:
1. Changed vendor id of PREP Pci bridge from 1011 to 1014 (ibm)
2. Tried booting and noticed that Bootloader did:
pci_config_read: PCI Bridge address:10 value: 0x
3. Found out that address 10 should have base adress in it.
J. Mayer wrote:
On Fri, 2005-04-15 at 23:58 +0300, Tero Kaarlela wrote:
Hi,
I am still trying to boot OS/2 PPC edition with Qemu. Non-contiguos
IO map & no support for Little-endian have been solved now thanks to J.
Mayer who sent me patches to work these out. Now bootloader give
Is this ok?(I just figured it out somehow)
Now bootloader gives me:
dma:command 0x24 not supported
dma:command 0x25 not supported
Just figuring out what these commands are
Turned on #debug DMA and here is the whole deal:
command: 0x24 not supported
Hi,
I am still trying to boot OS/2 PPC edition with Qemu. Non-contiguos
IO map & no support for Little-endian have been solved now thanks to J.
Mayer who sent me patches to work these out. Now bootloader gives me
following message:
IBM Microkernel bootloader press enter for manual boot(ente
28 matches
Mail list logo
