Hi all,
I'm trying to write a simple virtual hardware for QEMU. This hw must only return the value 0 every time I read at 0x6f8 address.
It looks like simple but I'm not sure... this is what I do...
I wrote a file in hw dir called hwfitt.c and implements hwfitt_ioport_read and *hwfitt_init
Hi Paul,
Does this mean that qemu-arm should be able to run the binaries that are
produced by RVCT? I am trying to run a simple helloworld, compiled and
linked with rvct2.2 (armcc -g -o hello hello.c) into a ELF 32-bit LSB
executable, ARM, version 1 (SYSV), statically linked, not stripped
On Monday 12 June 2006 15:09, Wolfgang Schildbach wrote:
Hi Paul,
Does this mean that qemu-arm should be able to run the binaries that are
produced by RVCT? I am trying to run a simple helloworld, compiled and
linked with rvct2.2 (armcc -g -o hello hello.c) into a ELF 32-bit LSB
executable,
Hi,
I need to start qemu with mips target, and I'm building a linux image for mips. But when I try:
qemu-system-mips myimage.img
I get this :
mips_r4k_init: load BIOS '/usr/local/share/qemu/mips_bios.bin' size 131072
qemu: fatal: Trying to execute code outside RAM or ROM at 0xbfc2
On Tue, 16 May 2006, Ben Taylor wrote:
(ITU), such as the DiskUpdate on tools.de/solaris/itu/DU.zip which
has a modifed RTL8029 driver that works with Qemu on SolarisX86.
Obviosly, if you boot a Solaris 10/x86 install with -B
acpi-user-options=0x0, you will not see the floppy. (I see that a
Thanks much Paul -- that did the trick! (Well, almost.)
For the benefit of other ADS/RVCT users that try this, here is what I did:
- figured out the file offset of the executable region in the axf file
(readelf -l foo.axf|grep LOAD).
For me, the offset appears to always be 0x34, and the
Where would I (start to) look for the reasons behind this? Is this
something that needs to be fixed on the ARM side (i.e. fix the location
where the ARM code looks for the environment)?
Look at the code in load_elf_binary that uses target_mmap to map the loadable
segments into memory. The
Wanted to know about individuals that provides support and custom
development for QEUM.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
interestingly enough, qemu-img is compiled with large file support, yet
on win32/mingw (gcc 3.4.5) qemu-img cannot manage images bigger
than 2Gb
anyone ever succeded this on win32 host ? large file support using
mingw ?
On 6/9/06, Paul Brook [EMAIL PROTECTED] wrote:
On Friday 09 June 2006
I'm sure you're doing something bad.
I used qemu-img and qemu with mingw32 and files not just bigger than
2Gb but bigger than 6Gb even.
El 12/06/2006, a las 20:33, Christian MICHON escribió:
interestingly enough, qemu-img is compiled with large file support,
yet
on win32/mingw (gcc 3.4.5)
Well,
Fabrice Bellard is main developer, and KQEMU whole developer.
Paul Brook maintains ARM system, and QVM86 whole developer.
Jocelyn Mayer (away) maintains PPC system.
Blue Swirl maintains Sparc system.
A couple of collaborators do development taks.
I maintain the OS compatibility list and do
I don't mind learning. Which version of msys/mingw/gcc/binutils do you have ?
On 6/12/06, Natalia Portillo [EMAIL PROTECTED] wrote:
I'm sure you're doing something bad.
I used qemu-img and qemu with mingw32 and files not just bigger than
2Gb but bigger than 6Gb even.
--
Christian
qemu-img.exe create -f raw test.raw 2G
should take a couple of minutes to run, yet completes in
less than 1s and test.raw is 0 bytes long.
On 6/12/06, Natalia Portillo [EMAIL PROTECTED] wrote:
I'm sure you're doing something bad.
I used qemu-img and qemu with mingw32 and files not just bigger
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-0.8.1-win32-imgover4g.patch
apparently fixes this. maybe Natalia mentionned no problem on qcow images,
not raw.
On 6/12/06, Christian MICHON [EMAIL PROTECTED] wrote:
qemu-img.exe create -f raw test.raw 2G
should take a couple of minutes to run,
Hi,
On Mon, 12 Jun 2006, Natalia Portillo wrote:
Fabrice Bellard is main developer, and KQEMU whole developer.
Paul Brook maintains ARM system, and QVM86 whole developer.
... and has commit rights to QEmu's main repository.
Jocelyn Mayer (away) maintains PPC system.
Blue Swirl maintains
Paul Jakma [EMAIL PROTECTED] wrote:
On Tue, 16 May 2006, Ben Taylor wrote:
(ITU), such as the DiskUpdate on tools.de/solaris/itu/DU.zip which
has a modifed RTL8029 driver that works with Qemu on SolarisX86.
Obviosly, if you boot a Solaris 10/x86 install with -B
16 matches
Mail list logo
