J. Mayer wrote:
I failed to run Mips target test image on my amd64 machine and I now
found the reason of the bug:
the kernel loader code used in hw/mips_r4k.c and hw/mips_malta.c
implicitelly assumes that the ram_addr_t is 32 bits long.
Unfortunatelly, on 64 bits hosts, this won't be the case
On Wed, 2007-10-17 at 14:51 +0100, Thiemo Seufer wrote:
J. Mayer wrote:
I failed to run Mips target test image on my amd64 machine and I now
found the reason of the bug:
the kernel loader code used in hw/mips_r4k.c and hw/mips_malta.c
implicitelly assumes that the ram_addr_t is 32 bits
Jocelyn Mayer wrote:
On Wed, 2007-10-17 at 14:51 +0100, Thiemo Seufer wrote:
J. Mayer wrote:
I failed to run Mips target test image on my amd64 machine and I now
found the reason of the bug:
the kernel loader code used in hw/mips_r4k.c and hw/mips_malta.c
implicitelly assumes that
On 10/17/07, Jocelyn Mayer [EMAIL PROTECTED] wrote:
On Wed, 2007-10-17 at 14:51 +0100, Thiemo Seufer wrote:
J. Mayer wrote:
I failed to run Mips target test image on my amd64 machine and I now
found the reason of the bug:
the kernel loader code used in hw/mips_r4k.c and hw/mips_malta.c
On Wed, 2007-10-17 at 22:06 +0300, Blue Swirl wrote:
On 10/17/07, Jocelyn Mayer [EMAIL PROTECTED] wrote:
On Wed, 2007-10-17 at 14:51 +0100, Thiemo Seufer wrote:
J. Mayer wrote:
I failed to run Mips target test image on my amd64 machine and I now
found the reason of the bug:
the
J. Mayer wrote:
On Wed, 2007-10-17 at 22:06 +0300, Blue Swirl wrote:
On 10/17/07, Jocelyn Mayer [EMAIL PROTECTED] wrote:
On Wed, 2007-10-17 at 14:51 +0100, Thiemo Seufer wrote:
J. Mayer wrote:
I failed to run Mips target test image on my amd64 machine and I now
found the reason
I failed to run Mips target test image on my amd64 machine and I now
found the reason of the bug:
the kernel loader code used in hw/mips_r4k.c and hw/mips_malta.c
implicitelly assumes that the ram_addr_t is 32 bits long.
Unfortunatelly, on 64 bits hosts, this won't be the case and the kernel
load
