On 10/02/2013 12:09:58 PM, Anthony Liguori wrote:
All of Paul's emails are bouncing and he hasn't been active for
some time.
...
M68K
-M: Paul Brook p...@codesourcery.com
-S: Odd Fixes
+S: Orphan
F: target-m68k/
F: hw/m68k/
Laurent Vivier has an m68k gitorious branch to add the q800
On 10/02/2013 06:40:18 PM, Laurent Vivier wrote:
Le 02/10/2013 20:42, Rob Landley a écrit :
Laurent Vivier has an m68k gitorious branch to add the q800 target,
which
I've occasionally tested and would really really like to see
finished and
merged.
Alas, last time I tested it the sucker
On 09/30/2013 12:25:45 PM, Min LI wrote:
Dear all,
I am very interested in QEMU and trying to figure out the boot
process of guest VM. According to my understanding about QEMU code,
bochs BIOS is loaded into memory by pc_system_firmware_init(…).
However, I notice QEMU handles
On 10/01/2013 12:19:51 PM, Richard Henderson wrote:
On 09/25/2013 12:27 PM, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
---
Since the GCC compile farm took their hppa machine off-line, I have
no way
to test this port anymore. Worse, I can't find any
On 09/02/2013 11:07:03 AM, Aurelien Jarno wrote:
On Fri, Aug 23, 2013 at 12:47:43PM -0700, Richard Henderson wrote:
I've been thinking for a while about how to reliably test TCG
backends, and
maybe how to do regression testing on them. Having to begin the
test from a
guest binary,
On 09/11/2013 07:54:32 AM, Claudio Fontana wrote:
This is the aarch64 libvixl support patchset in the current state.
It provides (limited) support for disassembly output on aarch64.
Only host disassembly is enabled, since target for aarch64 is not in
yet.
An external objdump solution as
On 07/23/2013 12:16:53 AM, Renich Bon Ciric wrote:
Hello,
I am new to this...
I'm trying to run some rom file I got from a client. It's a sc2005
processor; supposedly compatible with 4k.
Anyway, I do this:
qemu-system-mips -M mips -pflash 301-3100\ -\ user\ specified\ -\
Full.bin -serial
On 07/31/2013 12:19:03 AM, Stefan Weil wrote:
Am 31.07.2013 03:50, schrieb Erik de Castro Lopo:
Hi all,
I have a patch I would like to submit and I am currently running it
past
my employer's legal department. The legal department has identified
10
different licenses in the Qemu codebase
On 07/04/2013 04:52:45 PM, Olivier Danet wrote:
On 29/06/2013 22:29, Olivier Danet wrote:
On 28/06/2013 23:44, Mark Cave-Ayland wrote:
On 28/06/13 03:08, Rob Landley wrote:
Commit 467b34689d27 upgraded the openbios image, and ever since my
linux
system images hang about the time they try
On 06/29/2013 03:29:08 PM, Olivier Danet wrote:
How embarrassing...
- QEMU 1.5.1 can boot Debian Etch (kernel 2.6.18), RedHat 4.2 (kernel
2.0.30), NetBSD 6.1 and OpenBSD 5.3.
- Your image (Linux 3.8) can be started with a TurboSparc CPU :
qemu -cpu Fujitsu MB86907.
Yay! That fixes it.
On 06/29/2013 06:03:26 AM, Peter Maydell wrote:
On 28 June 2013 08:01, Rob Landley r...@landley.net wrote:
Now that the next kernel's about to come out, I'm trying to get my
arm
versatile image to work under qemu 1.5.0. The old kernel doesn't
work, and
the current vanilla kernel doesn't
On 07/08/2013 08:01:08 PM, Richard Henderson wrote:
The recent changes for ioport memory regions is a blessing and a
curse for the simplified alpha machine model we have.
On the one hand, we can eliminate two hacks present in the tsunami
system chip emulation. We also now get machine checks
Prebulit binaries of all of the above are at:
http://landley.net/aboriginal/bin
The system-image tarballs are bootable system images, tested under
qemu 1.5.1, which provide a shell prompt on qemu's stdin/stdout and a
native compiler capable of building Linux From Scratch inside the
On 07/10/2013 08:49:35 AM, Richard Henderson wrote:
On 07/09/2013 10:43 AM, Rob Landley wrote:
Do you have a kernel .config that boots on this board? I'd really
like to try
this out myself...
I haven't worked on this in quite some time. But I've located two
branches
that look like
I intermittently get this from current kernels running under currentish
qemu-git. Look familiar to anybody?
reboot: machine restart
general protection fault: fff2 [#1]
CPU: 0 PID: 44 Comm: oneit Not tainted 3.10.0-rc7+ #3
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
task: 8800068fd500
Commit 467b34689d27 upgraded the openbios image, and ever since my
linux system images hang about the time they try to initialize
interrupts.
http://landley.net/aboriginal/bin/system-image-sparc.tar.bz2
Extract that and ./run-emulator.sh in the tarball. Using qemu 1.2.0
for example works
I have images that boot under qemu-system-sh4 at:
http://landley.net/aboriginal/bin/system-image-sh4.tar.bz2
But in order to get them to work with current kernels, I have to apply
the attached sh4.patch to qemu.
What I did with earlier kernels was apply the attached
linux-fixsh4-2.patch
On 04/08/2013 03:16:18 PM, Peter Maydell wrote:
On 8 April 2013 18:37, Rob Landley r...@landley.net wrote:
On 04/06/2013 10:44:25 AM, Peter Maydell wrote:
This patch series fixes a number of serious bugs in our emulation
of
the PCI controller found on VersatilePB and the early Realview
On 11/12/2013 08:30:39 AM, Peter Maydell wrote:
On 12 November 2013 14:27, Xin Tong trent.t...@gmail.com wrote:
Hi
I would like to know where i get can 32bit ARM image
For which board?
with appropriate network driver.
Appropriate for what?
http://people.debian.org/~aurel32/qemu/armel/
I'd like to install ubuntu for Power PC under qemu, which is one CD plus
network access so it seems pretty straightforward:
dd if=/dev/zero of=kubuntu-ppc.img bs=1M count=4096
qemu-system-ppc -hda kubuntu-ppc.img -cdrom kubuntu-5.10-install-powerpc.iso \
-boot d
But I can't get it to boot from
When I try to install kubuntu in a virtual x86-64 image, the emulator hangs at
seemingly random places, eating 100% cpu time but making no progress.
I've tried four different variants:
qemu 0.8.2 built with gcc-3.3
current cvs snapshot built with gcc-3.3
qemu 0.8.2 built with gcc-4.0
On Monday 09 October 2006 8:08 am, Jim C. Brown wrote:
On Mon, Oct 09, 2006 at 12:05:02AM -0400, Rob Landley wrote:
qemu is primarily a dynamic translator not a virtualizer.
That's an implementation detail. The end result is running programs in a
virtual environment, and qemu's system
On Tuesday 10 October 2006 5:26 am, Joshua Root wrote:
Part of the generally accepted definition of virtualization is that the
majority of guest instructions execute directly on the real CPU with no
intervention by the VMM. QEMU + qvm86 does count as virtualization if
the system spends most of
On Tuesday 10 October 2006 11:46 am, Markus Schiltknecht wrote:
Hi,
I get this error, when I don't give qemu a 'hda':
Use /dev/zero. (Several people have suggested that qemu should default
to /dev/zero when you give it a kernel but don't give it a hard drive, but
last I checked it still
On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
Is there any work going on now to add config file support?
Chuck Brazie
[EMAIL PROTECTED]
As a random end-user, I really like being able to run qemu without a config
file, configuring it entirely on the command line. I'd be highly
On Friday 20 October 2006 2:53 pm, K. Richard Pixley wrote:
Could someone please explain the issue with gcc4, please? Or point me
to an existing explanation?
I mean, I understand that qemu is believed to be building incorrectly
with gcc4. But what is the failure mode folks have been
On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
I've been considering a machine config file for a while, but haven't come up
with a coherent way of representing everything yet.
Do you at least have a list of everything that needs to be represented? (I
have a list but am fairly certain
On Monday 23 October 2006 1:50 pm, K. Richard Pixley wrote:
Rob Landley wrote:
On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
Is there any work going on now to add config file support?
Chuck Brazie
[EMAIL PROTECTED]
As a random end-user, I really like being
On Monday 23 October 2006 4:29 pm, Paul Brook wrote:
On Monday 23 October 2006 21:01, Rob Landley wrote:
On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
I've been considering a machine config file for a while, but haven't
come
up with a coherent way of representing everything yet
On Monday 23 October 2006 7:33 pm, Paul Brook wrote:
My intention is that a machine config file would remove the motherboard
bits
altogether. ie. the config file describes everything that pc_init_1 does.
The
first half of pc.c would remain because that's device emulation.
Sounds highly
On Monday 23 October 2006 8:12 pm, Paul Sokolovsky wrote:
Yes, machine config apparently would be a hierarchical structure,
with cross-references. And well, there's an industrial standard to
represent that - XML.
There's an interesting sort of natural selection at work in open source.
On Monday 23 October 2006 9:38 pm, Paul Sokolovsky wrote:
Maybe. But where are new chips in qemu? Why there're still only 2
ARM boards? How do I stick wi-fi card in one of them? So the concern
is not just if it's easy to add new devices or not, but if there're means
to actually support
On Tuesday 24 October 2006 6:47 am, Flavio Visentin wrote:
At this point it's really cleaner and maybe simpler to use XML
Have you ever implemented a validating XML parser? I have. It only
_looks_ clean and simple.
Rob
--
Perfection is reached, not when there is no longer anything to add,
On Monday 23 October 2006 2:37 pm, Paul Brook wrote:
It turn out that qemu already does most of the hard work, and a code
generation backend is fairly simple. The diff for my current implementation
is 2k lines of common code, plus 1k lines for each of x86, amd64 and ppc32
hosts.
My
On Wednesday 27 September 2006 4:27 am, Martin Guy wrote:
There are some statistics at freaknet.org/martin/QEMU for various
types of x86 processor, but giving only BogoMIPS, which are way
overrated.
I presume this is cos QEMU translates the kernel speed test loop once
then runs it as x86
On Tuesday 24 October 2006 8:24 pm, Paul Brook wrote:
ColdFire is the only target that uses it exclusively. Arm is currently a
hybrid of dyngen and the new backend. So is i386, to a lesser extent.
Other targets have minimal changes necessary to make them work.
Ok.
Do you have a quick
On Wednesday 25 October 2006 11:01 am, Paul Brook wrote:
Oh, c'mon, Rob! I really didn't want to ask Paul Brook that, but
sure you'll fix my cluelessness right here, right now - tell me, tell me,
why Linux has dynamic-loadable modules support, which clueless passers-by
like me call
On Thursday 26 October 2006 3:23 am, KazuyaMatsunaga wrote:
Hello,
It is impolite to write an unexpected letter.
Compared to the mountains of spam I get every day? Not really. :)
I am a college student in
Japan. I belong to information processing system laboratory, and I work on
On Friday 27 October 2006 7:09 pm, Paul Brook wrote:
It has been a really long time I have been working on a broken system
that did not default to signed.
The only thing that is broken is your knowlege of C.
Okay.
And what system did you encounter this behaviour on?
Common
On Saturday 28 October 2006 6:46 am, Martin Guy wrote:
gcc on ARM systems default to unsigned. The C standard specifically
states that char is either signed or unsigned at the whim of the
implementor
Or, more to the point, at the behest of the machine architecture.
Having to generate
On Monday 23 October 2006 1:58 pm, Paul Brook wrote:
Although, all told, it would seem to me that what might be called for
here is a new gcc target. A gcc target specifically for generating qemu
code. That would just simply generate whatever qemu wanted for function
postamble.
Better
On Monday 30 October 2006 9:56 am, Paul Brook wrote:
On Monday 30 October 2006 04:35, Rob Landley wrote:
On Monday 23 October 2006 1:58 pm, Paul Brook wrote:
Although, all told, it would seem to me that what might be called for
here is a new gcc target. A gcc target specifically
On Monday 30 October 2006 8:04 am, Jens Arm wrote:
Hi
If I try to start xubuntu/ubuntu (6.10) in qemu from cdrom
the isolinux 3.11 says Loading... but can not change to graphic mode.
How can I start ubuntu in qemu?
Are you trying the x86-64 version, or the x86 version? I haven't been
On Monday 23 October 2006 2:37 pm, Paul Brook wrote:
Better to just teach qemu how to generate code.
In fact I've already done most of the infrastructure (and a fair amount
of the legwork) for this. The only major missing function is code to do
softmmu load/store ops.
On Tuesday 31 October 2006 2:02 pm, Paul Brook wrote:
As an example take the arm instruction
add, r0, r1, r2, lsl #2
This is equivalent to the C expression
r0 = r1 + (r2 2)
...
When fully converted to the new system this would become:
int tmp = gen_new_qreg(); /* Allocate a
On Tuesday 31 October 2006 5:08 pm, Paul Brook wrote:
On Tuesday 31 October 2006 20:41, Rob Landley wrote:
Welcome to Stupid Question Theatre! With your host, Paul Brook. Today's
contestant is: Rob Landley. How dumb will it get?
Bonus round!
I thought what you were doing was replacing
On Tuesday 31 October 2006 7:29 pm, Paul Brook wrote:
Actually it sounds additive rather than multiplicative. Does each target
have an entirely unrelated set of ops, or is there a shared set of
primitive ops plus some oddballs?
The shared set of primitive ops is basically qops :-)
You
On Tuesday 31 October 2006 10:22 pm, Paul Brook wrote:
and glue them together like we do with dyngen. However once you've done
that you've implemented most of what's needed for fully dynamic qops, so
it doesn't really seem worth it.
I missed a curve. What's fully dynamic qops?
On Wednesday 27 December 2006 11:24 am, Ely Soto wrote:
Excellent, I had encountered that bug earlier on when trying to debug
using workbench.
Are you guys developing a BSP for qemu?
I have a partially working one.
I'm poking at something like that.
http://landley.net/code/firmware
On Thursday 04 January 2007 12:29 pm, Bernhard Fischer wrote:
Hi,
The attached patch moves the x_keycode_to_pc_keycode LUT from sdl.c into
an x_keycode.c. This struct is also used by the GGI backend (that is not
yet merged ¹).
Whatever happened to ggi? All I remember is that something over
On Tuesday 13 February 2007 4:44 pm, Hervé Poussineau wrote:
Hi,
Correct number formatting on Windows for 64 bit numbers is I64, while it
is ll on *nix.
Might I introduce you to the c99 PRIu64 macro (and friends)?
uint64_t bytes=1234;
printf(%PRIu64 bytes\n, bytes);
Rob
--
Perfection
On Thursday 15 February 2007 11:27 am, Paul Brook wrote:
On Thursday 15 February 2007 09:17, Thomas Petazzoni wrote:
Hi,
Le Tue, 13 Feb 2007 15:58:13 +0100,
andrzej zaborowski [EMAIL PROTECTED] a écrit :
Subject: don't require a disk image for network boot
BTW, is there a reason
Could make install do a qemu-system-x86 and then symlink the qemu name to
whatever the host platform happens to be? (So if you build qemu on x86-64
then qemu points to qemu-system-x86_64? Or if you build the sucker on a
PPC system...)
The relevant code seems to be is in Makefile.target, line
On Friday 23 February 2007 5:54 pm, Paul Brook wrote:
On Friday 23 February 2007 20:09, Rodrigo Vivi wrote:
Hi all,
Is there someone working on armv6 support?
I'm very interested to help this development...
I already have ARMv6 and ARMv7 implemented, but am unable to release the
code.
On Wednesday 07 March 2007 1:14 pm, Quentin Barnes wrote:
This is my first post to the list. Hopefully, it will go well.
I've been using the ARM qemu for Linux development for some basic
work, but wanted to expand and do more with it. I outgrew the
initrd limitation and needed a disk.
On Tuesday 13 March 2007 10:25 am, Ben Taylor wrote:
However, it's very wax-on, wax-off kind of thing. Without the patch,
arm-test and mips-test crash. With the patch, I can run both tests.
Could we get a reproduction sequence for the crashes please?
Rob
--
Vista: Windows Millenium Second
On Tuesday 13 March 2007 10:21 pm, Julian Seward wrote:
0.9.0, or that the compiler/host combination used to build the qemu
binary Julian is running generated bad code for the float compares.
I used gcc 3.4.6 bootstrapped as normal ('make bootstrap; make install')
on a 64-bit machine.
On Friday 16 March 2007 2:10 pm, Julian Seward wrote:
On Friday 16 March 2007 18:07, Rob Landley wrote:
On Tuesday 13 March 2007 10:21 pm, Julian Seward wrote:
0.9.0, or that the compiler/host combination used to build the qemu
binary Julian is running generated bad code for the float
On Tuesday 20 March 2007 6:19 pm, Julian Seward wrote:
Limited effort is always a problem, granted.
So here's a broader question, which I'm surprised nobody has asked
before (afaik). Think forward to a hypothetical QEMU 1.0 release.
What criteria are required for such a release?
*cough*
On Thursday 22 March 2007 7:00 pm, Johannes Schindelin wrote:
Hi,
On Thu, 22 Mar 2007, Rob Landley wrote:
On Tuesday 20 March 2007 6:19 pm, Julian Seward wrote:
Limited effort is always a problem, granted.
So here's a broader question, which I'm surprised nobody has asked
On Thursday 22 March 2007 7:29 pm, Thiemo Seufer wrote:
Do you mean you're asking me to break up Paul Brook's QOPS tree at
https://nowt.dyndns.org and submit it to mainline? I can do this thing,
if
you really think it would help. Seems a bit roundabout to submit Paul
Brook's work to
On Saturday 24 March 2007 8:32 am, Sunil Amitkumar Janki wrote:
Anyhow, I expect 32-bit hardware to gradually die because of wear and
tear in the next few years and the replacement will be 64-bit hardware so
the problem will solve itself that way.
Specifically, in 2008 32-bit x86 hardware
On Thursday 29 March 2007 4:05 am, Joakim Tjernlund wrote:
Hi Rob
I saw your change to powerpc crt1.S and I don't agree with it.
mr r8,r3 copies r3 to r8
r8 needs to maps to rtld_fini in __uClibc_main and that maps to
_dl_fini. Basically you have broken dynamic apps.
Sigh. Ok.
What does
I've been trying several variants of:
qemu-system-ppc -M prep -nographic -hda ext2.img -kernel zImage \
-append rw init=/tools/bin/sh panic=1 PATH=/tools/bin root=/dev/hda
console=/dev/ttyS0
My miniconfig is attached. (You can make a full-sized .config out of it with
make
On Monday 26 March 2007 1:14 pm, Axel Zeuner wrote:
Hi Avi,
On Sunday 25 March 2007 15:40, Avi Kivity wrote:
Axel Zeuner wrote:
A full featured converter (cvtasm) has a lot of dependencies: it has to
support all hosts (M) (with all assembler dialects M') and all targets
N,
i.e. in
On Tuesday 03 April 2007 8:48 pm, Jason Wessel wrote:
To boot the prep machine you need to configure the kernel for prep and
use the zImage.prep file. IE: CONFIG_PPC_PREP=y
Right now you selected CONFIG_PPC_CHRP
In 2.6.20.4 PPC_PREP depends on:
(PPC64 || CLASSIC32) PPC_MULTIPLATFORM
On Sunday 08 April 2007 4:43 pm, Natalia Portillo wrote:
Hi all,
I have a huge list of operating systems (both closed and open source, that
works and that doesn't work under QEMU) that can be used to check that QEMU
doesn't broke (or even, that it corrects a non-working state).
I vaguely
On Sunday 08 April 2007 7:19 pm, Paul Brook wrote:
Mr Paul Brook did break the PREP and heathrow machines while doing
changes in the PCI code. There were some posts on this list reporting
this and he never even tried to fix what he broke. And now he's
complaining I cannot test as it does
On Monday 09 April 2007 6:32 pm, J. Mayer wrote:
On Mon, 2007-04-09 at 17:26 -0400, Rob Landley wrote:
On Sunday 08 April 2007 7:19 pm, Paul Brook wrote:
[...]
AFAIK PPC emulation hasn't *ever* worked well enough to boot without at
least
building a custom linux kernel. In addition
I'm fighting with cvs and haven't been able to update my build directory yet.
(I've been spoiled by mercurial, where doing an update on a directory with
modifications in it doesn't _eat_ the directory. And my attempt to create a
mercurial copy of the cvs history with tailor so I could tracck
On Thursday 12 April 2007 11:49 am, Jason Wessel wrote:
J. Mayer wrote:
On Wed, 2007-04-11 at 17:49 -0400, Rob Landley wrote:
qemu-system-ppc -M prep -nographic -kernel zImage-powerpc -append \
console=/dev/ttyS0
You cannot append anything to the command line this way
On Thursday 12 April 2007 12:16 pm, eady wrote:
I'm still looking for any suggestions on how to save and restore the
target cpu state from within a custom instruction in op.c. I basically
want a custom instruction to save the cpu state to a data structure and
then continue on normally, a
On Tuesday 24 April 2007 2:23 am, Kitambi Leo wrote:
I've been using qemu using the Linux framebuffer console, on a machine
that's a bit too slow to support X. There have been more than a few snags,
but perhaps the most irritating one was that if qemu crashed (and received a
SIGSEGV), it
On Thursday 31 May 2007 6:06 pm, Christopher Friedt wrote:
Hi everyone,
I've just gotten qemu emulating an arm system on my laptop, which I'm
hoping to use for cross-compilation. I don't have a disk image to use
(is there any way to create a disk image from a directory tree??), so
I'm
In the 2.6.21 kernel the sym53c8xx_2 SCSI controller changed in a way that
QEMU's virtual SCSI controller doesn't handle this properly:
Here's what 2.6.20 does during boot:
Loading iSCSI transport class v2.0-724.
PCI: enabling device :00:0c.0 (0140 - 0143)
sym0: 895a rev 0x0 at pci
Before that commit, my mips kernel booted to a shell prompt. After, qemu
segfaults immediately.
To test this, you can grab my system image at
http://landley.net/aboriginal/downloads/binaries/system-image-mips.tar.bz2 and
./run-emulator.sh out off that.
Rob
--
GPLv3: as worthy a successor as
On Sunday 19 December 2010 09:04:00 Andreas Färber wrote:
For OpenBIOS to work, we need fw_cfg in ppc_prep.c and, independently,
patches to OpenBIOS. Unless of course we want to use another firmware
like OFW from the start. The main interest in PReP nowadays will be
proprietary firmware
On Monday 20 December 2010 03:04:38 Alexander Graf wrote:
On 19.12.2010, at 20:12, Andreas Färber wrote:
Am 19.12.2010 um 16:34 schrieb Alexander Graf:
On 19.12.2010, at 16:04, Andreas Färber wrote:
Am 19.12.2010 um 10:54 schrieb Alexander Graf:
On 14.12.2010, at 01:49, Andreas Färber
On Sunday 19 December 2010 09:34:24 Alexander Graf wrote:
On 19.12.2010, at 16:04, Andreas Färber wrote:
Am 19.12.2010 um 10:54 schrieb Alexander Graf:
On 14.12.2010, at 01:49, Andreas Färber wrote:
Hello,
Based on an earlier attempt of mine to make OpenBIOS work with -M prep,
with
On Tuesday 04 January 2011 15:00:12 Alexander Graf wrote:
I have this very issue with s390. The only host to run (and compile)
this on is an s390. And few people have those. So it breaks from time to
time.
I have some pages bookmarked hinting how to get S390 Linux to boot under
On Wednesday 05 January 2011 06:31:01 Alexander Graf wrote:
On 05.01.2011, at 13:07, Rob Landley wrote:
On Tuesday 04 January 2011 15:00:12 Alexander Graf wrote:
I have this very issue with s390. The only host to run (and compile)
this on is an s390. And few people have those. So it breaks
On 01/23/2011 06:59 AM, Dushyant Bansal wrote:
Hi all,
I have configured and built qemu with device tree support.
qemu-version: 0.13.50
I have built kernel image (uImage) for bamboo using powerpc-440 toolchain.
kernel-version: 2.6.37-rc6+
When I try to run this command,
#
On 01/23/2011 01:01 PM, Dushyant Bansal wrote:
I am also using
http://www.landley.net/aboriginal/downloads/binaries/cross-compiler-powerpc-440fp.tar.bz2cross-compiler-powerpc-440fp
from the aboriginal project
(http://www.landley.net/aboriginal/downloads/binaries/) to build the
kernel image
Using yesterday's -git, following the instructions in
http://wiki.qemu.org/Documentation/9psetup (which is missing a kernel
symbol, you need to add CONFIG_VIRTIO_PCI to your kernel too), I managed
to mount a read-only virtfs filesystem, adding this to the
qemu-system-x86_64 command line:
-virtfs
On 01/16/2011 10:01 AM, Raphaël Lefèvre wrote:
On Sun, Jan 16, 2011 at 11:21 PM, Stefano Bonifazi
stefboombas...@gmail.com wrote:
2. how can I check the number of target cpu cycles or target
instructions executed inside qemu-user (i.e. qemu-ppc)?
Is there any variable I can inspect for such
On 01/23/2011 01:52 PM, Dushyant Bansal wrote:
Those are board emulations. Does it have a 440 _cpu_ emulation?
./qemu-system-ppc -cpu ? | grep 440
This is the output.
PowerPC 440-Xilinx PVR 7ff21910
Is this right for my requirement?
I have no idea? Sounds worth a try...
On 01/23/2011 04:25 PM, Stefano Bonifazi wrote:
I am trying to shift in memory the target executable .. now the code is
supposed to be loaded by the elfloader at the exact start address set
at link time ..
Ah, elf loading. That's a whole 'nother bag of worms.
Oddly enough, I was deling with
On 01/24/2011 04:17 AM, Stefano Bonifazi wrote:
I read your post, and yup you also noticed the weird of load_bias.. and
wondered how it can work on x86..
But I think your work was on qemu-system.. I am working on qemu-user..
My post wasn't on qemu-anything, it was while I was trying to debug
On 01/24/2011 10:15 AM, Aneesh Kumar K. V wrote:
On Sun, 23 Jan 2011 13:33:14 -0600, Rob Landley r...@landley.net wrote:
Using yesterday's -git, following the instructions in
http://wiki.qemu.org/Documentation/9psetup (which is missing a kernel
symbol, you need to add CONFIG_VIRTIO_PCI to your
On 01/24/2011 03:16 PM, Stefano Bonifazi wrote:
Hi! Thanks for replying me!
The thing is, the kernel currently _does_ work, so studying the relevant
kernel code (and possibly the dynamic loader code) is one way to learn
how it currently works.
Sorry what kernel? Qemu's? Linux's?
QEMU isn't a
On 02/05/2011 08:39 AM, Stefan Weil wrote:
Currently, most QEMU code assumes that pointers and long integers have
the same size, typically 32 bit on 32 bit hosts, 64 bit on 64 bit hosts.
This is called the LP64 standard:
http://www.unix.org/whitepapers/64bit.html
Which was created for a
On Thursday 03 June 2010 02:52:03 Paul Brook wrote:
I'm trying to get arm big endian support to work. I patched the 2.6.33
kernel to pretend that good old versatilepb can have a big endian CPU
plugged into it (attached), and then I built a kernel with the attached
.config, and qemu went
a successor as The Phantom Meanace, as timely as Duke Nukem
Forever, and as welcome
as New Coke.
From vi...@kyllikki.org Fri Nov 27 05:17:32 2009
Return-Path: qemu-devel-bounces+rob=landley@nongnu.org
X-Original-To: r...@landley.net
Delivered-To: land...@grelber.thyrsus.com
Received: from lists.gnu.org
On Thursday 01 July 2010 16:50:29 Paul Brook wrote:
Here is the patch again. There may be more work to be done on top of
this, but this patch staying out of tree hasn't noticeably accelerated
that work in the past year and change. Could it please be merged?
As mentioned previously, V5
drivers to hardware.
Proposer:
Rob Landley
Description:
Currently, the QEMU is emulating system boards via hardwired .c files, which
explicitly set up the resources for each emulation in a separate C function.
In theory, QEMU could parse the same device tree data format the Linux kernel
uses
On Thursday 17 December 2009 14:29:47 Anthony Liguori wrote:
Rob Landley wrote:
For background of CELF project proposals, see:
http://elinux.org/CELF_Open_Project_Proposal_2010
Summary:
Integrate a flattened device tree parser into the emulator QEMU, so QEMU
can create board
Static binaries that run under the Linux kernel don't run under qemu-ppc. For
example, the prebuilt busybox binaries here:
http://busybox.net/downloads/binaries/1.16.0/busybox-powerpc
Don't run under qemu-ppc, but runs just fine under qemu-system-ppc with the
image at:
The -hda, -hdb, -hdc, and -hdd command line options for g3beige don't match
the order the kernel assigns the drives.
The reason is that the Linux kernel always initializes the cmd646 driver
before the pmac driver, thus if there's a cmd646 it gets /dev/hda and
/dev/hdb, and the pmac gets
On Saturday 13 February 2010 04:28:44 Alexander Graf wrote:
On 13.02.2010, at 09:02, Rob Landley wrote:
The -hda, -hdb, -hdc, and -hdd command line options for g3beige don't
match the order the kernel assigns the drives.
The reason is that the Linux kernel always initializes the cmd646
On Saturday 13 February 2010 06:04:03 Alexander Graf wrote:
Exactly, that's the issue to fix here, make DBDMA work with CD-ROM so we
can get rid of the cmd64x controller.
Speaking of which - in my PPC64 enabling series I use MacIO for all 4 IDE
devices. At least with recent kernels, Linux
1 - 100 of 330 matches
Mail list logo
