Henrik,
I had been trying to connect to /dev/pts/0 and am having trouble receiving
data. I'm running redhat 9 and have written a small program to open the
pty and read/write to it. First time I connect I receive the 'QEMU 0.7.0
monitor - type 'help' for more information' welcome message. From t
> Right, is this set according to some OF properties (which could be a
> cause of the bug) ?
> I didn't find anything like this in OF fb code, but I may have missed
> it
prom_init() sets it using calls to OF fb driver setcolreg method.
Ben.
_
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
On Mon, 2005-05-23 at 20:51 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2005-05-23 at 12:47 +0200, J. Mayer wrote:
> > On Mon, 2005-05-23 at 10:31 +1000, Benjamin Herrenschmidt wrote:
> > > > console=ttyS0 console=tty0
> > > > Note that the Open-Firmware frame-buffer support is broken in many 2.
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,
