On Jul 12, 2020, at 10:02 PM, qemu-devel-requ...@nongnu.org wrote:
Message: 6
Date: Mon, 13 Jul 2020 00:17:30 -
From: JuanPabloCuervo <1887...@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1887318] [NEW] impossible to install in OSX Yosemite
10.10.5
Message-ID:
<159
On Sun, Mar 8, 2020 at 3:33 PM Volker Rümelin wrote:
> The review for patch ed2a4a7941 "audio: proper support for
> float samples in mixeng" suggested this would be a good idea.
>
> Acked-by: Markus Armbruster
> Signed-off-by: Volker Rümelin
> ---
>
>
> Your patch applied cleanly to the late
-- Forwarded message -
From: G 3
Date: Wed, Mar 4, 2020 at 1:35 PM
Subject: Re: [RFC PATCH v2] target/ppc: Enable hardfloat for PPC
To: BALATON Zoltan
On Mon, Mar 2, 2020 at 6:16 PM BALATON Zoltan wrote:
> On Mon, 2 Mar 2020, Richard Henderson wrote:
> > On 3/2/2
Accuracy is an important part of the IEEE 754 floating point standard. The
whole purpose of this standard is to ensure floating point calculations are
consistent across multiple CPUs. I believe referring to this patch as
inaccurate is itself inaccurate. That gives the impression that this patch
pro
So far we've been converting docs to Sphinx and assigning them
to manuals according to the division originally set out by
Paolo on the wiki: https://wiki.qemu.org/Features/Documentation
* QEMU User-mode Emulation User's Guide (docs/user)
* QEMU System Emulation User's Guide (docs/system)
* QEMU
> Date: Sat, 1 Feb 2020 17:05:34 +
> From: Peter Maydell
> To: qemu-devel@nongnu.org
> Cc: Gerd Hoffmann
> Subject: [PATCH] ui/cocoa: Drop workarounds for pre-10.12 OSX
> Message-ID: <20200201170534.22123-1-peter.mayd...@linaro.org>
>
> Our official OSX support policy covers the last two rel
> You can now access the latest QEMU HTML documentation built from
https://wiki.qemu.org/docs/qemu-doc.html
This is a welcome start. Could we add version support to the URL?
What I mean is add the version number to the path of the URL.
Like this:
https://wiki.qemu.org/docs/4.2/qemu-doc.html
Th
>
> Message: 9
> Date: Wed, 30 Oct 2019 01:46:54 -
> From: John Canada <1850...@bugs.launchpad.net>
> To: qemu-devel@nongnu.org
> Subject: [Bug 1850570] [NEW] Cannot use usb-host on Mac OS
> Message-ID:
> <
> 157240001496.28481.10507378472210680134.malone...@chaenomeles.canonical.com
>
On Tue, Sep 24, 2019 at 1:05 PM G 3 wrote:
> On top
>
>
> Message: 9
>> Date: Tue, 24 Sep 2019 10:56:53 -
>> From: Adrian Vladu
>> To: qemu-devel@nongnu.org
>> Subject: [Bug 1826175] Re: Compilation on MSYS2/MinGW-w64 fails with
>> e
Thank you for the suggestion.
For the added note, did you want specific places listed? If so please let
me know these places.
Thank you.
On Tue, May 21, 2019 at 11:30 PM Richard Henderson <
richard.hender...@linaro.org> wrote:
> On 5/21/19 8:06 PM, John Arbuckle wrote:
> > Implement the PowerPC
On Apr 19, 2019, at 3:10 AM, Thomas Huth wrote:
On 19/04/2019 00.47, John Arbuckle wrote:
Capstone is not necessary in order to use QEMU. Disable it by
default.
This will save the user the pain of having to figure why QEMU isn't
building when this library is missing.
Signed-off-by: John Ar
isn't being counted. When the operating system iterates thru the list it
might stop right before the custom resolution value, preventing its
inclusion.
On Fri, Mar 1, 2019 at 12:47 AM Gerd Hoffmann wrote:
> On Thu, Feb 28, 2019 at 11:53:43AM -0500, G 3 wrote:
> > On Thu, Feb 28, 20
On Mon, Feb 25, 2019 at 5:24 AM Peter Maydell
wrote:
> The OSX Mojave release is more picky about enforcing the Cocoa API
> restriction that only the main thread may perform UI calls. To
> accommodate this we need to restructure the Cocoa code:
> * the special OSX main() creates a second thread
On Mon, Feb 25, 2019 at 5:24 AM Peter Maydell
wrote:
> The Cocoa UI should run on the main thread; this is enforced
> in OSX Mojave. In order to be able to run on the main thread,
> we need to make sure we hold the iothread lock whenever we
> call into various QEMU UI midlayer functions.
>
> Sign
On Thu, Feb 28, 2019 at 12:01 AM Mark Cave-Ayland <
mark.cave-ayl...@ilande.co.uk> wrote:
> On 27/02/2019 05:27, Gerd Hoffmann wrote:
>
> > On Tue, Feb 26, 2019 at 04:11:06PM -0500, G 3 wrote:
> >> When I use edid=on, I do see a lot of extra resolutions available in
&
25, 2019 at 09:49:22PM -0500, Programmingkid wrote:
> >
> > > On Feb 25, 2019, at 10:26 AM, Gerd Hoffmann wrote:
> > >
> > > On Mon, Feb 25, 2019 at 09:05:30AM -0500, G 3 wrote:
> > >> Hi Gerd, I was wondering if you have made any documentation for y
Hi Gerd, I was wondering if you have made any documentation for your EDID
patches. If you have could you provide a link please?
Also could a feature be added that allows the user to specify resolutions
to be made available to the guest?
Maybe it could work like this: -device VGA,edid=on,res=1366x
On Jul 11, 2018, at 5:18 PM, Peter Maydell wrote:
On 9 July 2018 at 16:02, John Arbuckle
wrote:
The NSEvent class method scrollingDeltaY is available
for Mac OS 10.7 and newer. Since QEMU supports Mac OS
10.5 and up, we need to be using a method that is
available on these version of Mac OS
On Jul 6, 2018, at 5:11 AM, Peter Maydell wrote:
On 6 July 2018 at 03:53, John Arbuckle
wrote:
The NSEvent class method scrollingDeltaY is available
for Mac OS 10.7 and newer. Since QEMU supports Mac OS
10.5 and up, we need to be using a method that is
available on these version of Mac OS X
Hi, I noticed your RISC-V patches on the mailing list and had a
question that I think you may be able to answer. Has anyone defined a
RISC-V platform yet? What I mean is defining what devices would be
found on a RISC-V motherboard. I do hope to see RISC-V based desktop
systems one day. But
On Jun 26, 2018, at 9:49 AM, Richard Henderson wrote:
On 06/25/2018 03:23 PM, Programmingkid wrote:
On Jun 25, 2018, at 5:08 PM, Richard Henderson
wrote:
On Mon, Jun 25, 2018, 08:23 G 3 wrote:
Try
uint64_t expected_answer = 0xdeadbeef;
...
c.i = expected_answer
On Jun 24, 2018, at 11:47 PM, Richard Henderson wrote:
On 06/24/2018 11:38 AM, Programmingkid wrote:
void test_division_by_zero()
{
Converter c;
uint64_t expected_answer = 0x0;
uint32_t actual_fpscr, expected_fpscr = 0xc410;
reset_fpscr();
set_fpscr_bit(ZE);
asm vo
On Jun 24, 2018, at 8:46 PM, David Gibson wrote:
On Fri, Jun 22, 2018 at 10:22:58PM -0400, John Arbuckle wrote:
When the fdiv instruction divides a finite number by zero,
the result actually depends on the FPSCR[ZE] bit. If this
bit is set, the return value is zero. If it is not set
the resul
On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
On 15/08/2017 20:46, Programmingkid wrote:
On Aug 14, 2017, at 2:51 AM, Paolo Bonzini
wrote:
On 13/08/2017 21:13, Programmingkid wrote:
Lately I found out that Windows NT 4.0 seems to work well with the
486 and pentium processors. Using
On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
On 15/08/2017 20:46, Programmingkid wrote:
On Aug 14, 2017, at 2:51 AM, Paolo Bonzini
wrote:
On 13/08/2017 21:13, Programmingkid wrote:
Lately I found out that Windows NT 4.0 seems to work well with the
486 and pentium processors. Using
I have recent made a wiki page for the Moxie target in QEMU. I need
some more information on it. Would you know the build directions and
the suggested command-line for running this target? Any information
you could supply would be appreciated. Thanks.
Here is the page: http://wiki.qemu.org/
I have made a new documentation page for the MicroBlaze target in
QEMU. If there are any suggestions or additions anyone would like to
make I would be glad to help.
http://wiki.qemu.org/Documentation/Platforms/MicroBlaze
On Jul 5, 2017, at 12:42 PM, qemu-devel-requ...@nongnu.org wrote:
Hi,
An interesting bug was reported on #qemu today. It was bisected to
8d04fb55 (drop global lock for TCG) and only occurred when QEMU was
run
with taskset -c 0. Originally the fingers where pointed at mttcg
but it
occurs i
On Jun 24, 2017, at 8:14 AM, Peter Maydell wrote:
On 23 June 2017 at 21:05, Programmingkid
wrote:
This patch is incompatible with anything below Mac OS 10.10.
Oops. Thanks for the report.
We support Mac OS 10.5 and up. I was able to make this patch work
on Mac OS 10.6 by changing this li
On Jun 22, 2017, at 3:25 AM, Peter Maydell wrote:
On 22 June 2017 at 03:54, G 3 wrote:
The advantage a test image would have is the user doesn't have to
worry
about compiling a test using a cross compiler. Everything the user
would
need to test QEMU is already inside the image
On Jun 21, 2017, at 12:28 PM, Peter Maydell wrote:
On 21 June 2017 at 17:27, G 3 wrote:
On Jun 21, 2017, at 12:20 PM, Peter Maydell wrote:
We don't yet have any mechanism for having tests that need to
be compiled for the target architecture, do we?
I don't know about that but
On Jun 21, 2017, at 12:20 PM, Peter Maydell wrote:
On 21 June 2017 at 17:14, Philippe Mathieu-Daudé
wrote:
do you think you can add your test as a qtest, to run it with
check-qtest?
We don't yet have any mechanism for having tests that need to
be compiled for the target architecture, do w
On Jun 21, 2017, at 12:14 PM, Philippe Mathieu-Daudé wrote:
Hi John,
On 05/09/2017 10:58 AM, G 3 wrote:
On May 9, 2017, at 5:55 AM, BALATON Zoltan wrote:
On Tue, 9 May 2017, Aurelien Jarno wrote:
| main.c: In function 'print_fpscr_settings':
| main.c:73:26: warning: suggest p
On Jun 18, 2017, at 4:36 PM, alar...@ddci.com wrote:
G 3 wrote on 06/18/2017 09:45:25 AM:
From: Aaron Larson
To: ag...@suse.de, alar...@ddci.com, da...@gibson.dropbear.id.au,
qemu-devel@nongnu.org, qemu-...@nongnu.org
Date: 06/05/2017 12:22 PM
Subject: [PATCH v3] target-ppc: Enable open
On Jun 18, 2017, at 6:50 AM, qemu-devel-requ...@nongnu.org wrote:
On Fri, Jun 16, 2017 at 11:31:02AM -0500, alar...@ddci.com wrote:
Aaron Larson wrote on 06/05/2017 12:22:53 PM:
From: Aaron Larson
To: ag...@suse.de, alar...@ddci.com, da...@gibson.dropbear.id.au,
qemu-devel@nongnu.org, qemu
On May 30, 2017, at 8:01 AM, Peter Maydell wrote:
On 25 May 2017 at 21:05, wrote:
What do you think about sharing the same ppc64.risu file to ppc
and ppc64/ppc64le. Then, instead of:
PPC64LE 0...
we'd have:
PPC 0...
So, specific instructions would be:
PPC64LE 0...
PPC64
On May 22, 2017, at 4:32 AM, qemu-devel-requ...@nongnu.org wrote:
Message: 2
Date: Mon, 22 May 2017 12:33:29 +0530
From: Nikunj A Dadhania
To: Sandipan Das
Cc: qemu-devel@nongnu.org, peter.mayd...@linaro.org,
jos...@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH risu] ppc64: Fix
On May 13, 2017, at 11:58 AM, qemu-devel-requ...@nongnu.org wrote:
I had two problems with QEMU on macOS:
1) Sometimes when alt-tabbing to QEMU it would act as if the 'a' key
was pressed so I'd get 'a'.
2) Using Sikuli to programatically send keys to the QEMU window text
Hi,
We've got a task coming up to implement half-precision floating point
(FP16) for ARMv8.2. As you know pretty much all our floating point in
QEMU is handled by our internal fork of John R. Hauser's BSD SoftFloat
library. Our current implementation is based on version 2a which
doesn't
suppor
On May 9, 2017, at 5:55 AM, BALATON Zoltan wrote:
On Tue, 9 May 2017, Aurelien Jarno wrote:
| main.c: In function 'print_fpscr_settings':
| main.c:73:26: warning: suggest parentheses around comparison in
operand of '&' [-Wparentheses]
| if ((fpscr >> i) & 0x1 == 1) {
|
Here is version two of the floating point test program:
/
**
* File: main.c
* Date: 4-30-2017
* Description: Implement a test program for various floating point
instructions.
* Note: tests made to work
On May 8, 2017, at 6:13 PM, Aurelien Jarno wrote:
On 2017-05-07 17:48, G 3 wrote:
I made a diagnostic program for the floating point unit. It will test
various PowerPC floating point instructions for compatibility with
the
PowerPC G3 processor. It was tested on a PowerPC G3 and G5 system
On May 8, 2017, at 5:54 PM, Aurelien Jarno wrote:
On 2017-05-07 17:48, G 3 wrote:
I made a diagnostic program for the floating point unit. It will test
various PowerPC floating point instructions for compatibility with
the
PowerPC G3 processor. It was tested on a PowerPC G3 and G5 system
I made a diagnostic program for the floating point unit. It will test
various PowerPC floating point instructions for compatibility with
the PowerPC G3 processor. It was tested on a PowerPC G3 and G5
system. The results of the program in qemu-system-ppc were pretty
bad. About every instruct
I'm trying to test all the floating point instructions only. They
tend to begin with the letter f. Is there a way to have risugen only
use instructions that begin with the letter F?
A MIPS page has just been put up here: http://wiki.qemu.org/
Documentation/Platforms/MIPS
I have tried to give as much info as I could about MIPS and QEMU but
I am no MIPS expert. What I need are pictures of qemu-system-mips in
action and any other information that could be provided. Other t
On Apr 25, 2017, at 9:16 AM, Eric Blake wrote:
On 04/24/2017 10:17 PM, G 3 wrote:
Add the ppc.risu file. It defines the format for various PowerPC
instructions.
Your emails are missing In-Reply-To and References headers, which
means
you posted 10 top-level threads instead of 9 replies to
On Apr 25, 2017, at 4:36 AM, Peter Maydell wrote:
On 25 April 2017 at 04:18, G 3 wrote:
Add the risu_ppc.c file. It defines several functions used by risu.
Signed-off-by: John Arbuckle
---
risu_ppc.c | 41 +
1 file changed, 41 insertions(+)
create
On Apr 25, 2017, at 4:17 AM, Peter Maydell wrote:
On 25 April 2017 at 04:19, G 3 wrote:
Add the risu_reginfo_ppc.c file. It handles operations involving
the reginfo
structure.
+/* check each floating point register */
+for (i = 0; i < NUMBER_OF_FPR; i++) {
+if (r1->
On Apr 25, 2017, at 4:14 AM, Peter Maydell wrote:
On 25 April 2017 at 04:17, G 3 wrote:
Add the ppc.risu file. It defines the format for various PowerPC
instructions.
Signed-off-by: John Arbuckle
---
ppc.risu | 527
+++
1 file
Replace the comment "mismatch, or end of test" with "called for a
mismatch,
or for the end of a test". This describes what happens better.
Signed-off-by: John Arbuckle
---
risu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/risu.c b/risu.c
index e7cbd57..bd771b1 100644
Add an option that prints each instruction that is currently being
tested.
To use this option, just add "--v" to risu's command-line.
Signed-off-by: John Arbuckle
---
risu.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/risu.c b/risu.c
index 7e42160..ed5b605
Print the message "End of test" on the risu host end.
Signed-off-by: John Arbuckle
---
risu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/risu.c b/risu.c
index ed5b605..e7cbd57 100644
--- a/risu.c
+++ b/risu.c
@@ -63,6 +63,7 @@ void apprentice_sigill(int sig, siginfo_t *si, void
*uc)
Add ppc support to the configure script.
Signed-off-by: John Arbuckle
---
configure | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 055e6d6..7881b18 100755
--- a/configure
+++ b/configure
@@ -56,6 +56,8 @@ guess_arch() {
else
Add the risugen_ppc.pm file. It is used to generate the instructions
that risu
runs.
Signed-off-by: John Arbuckle
---
risugen_ppc.pm | 744 +++
++
1 file changed, 744 insertions(+)
create mode 100644 risugen_ppc.pm
diff --git a/risugen_p
Add the risu_reginfo_ppc.h file. It defines the reginfo structure.
Signed-off-by: John Arbuckle
---
risu_reginfo_ppc.h | 32
1 file changed, 32 insertions(+)
create mode 100644 risu_reginfo_ppc.h
diff --git a/risu_reginfo_ppc.h b/risu_reginfo_ppc.h
new file mo
Add the risu_reginfo_ppc.c file. It handles operations involving the
reginfo
structure.
Signed-off-by: John Arbuckle
---
risu_reginfo_ppc.c | 273 +++
++
1 file changed, 273 insertions(+)
create mode 100644 risu_reginfo_ppc.c
diff --git a/ri
Add the risu_ppc.c file. It defines several functions used by risu.
Signed-off-by: John Arbuckle
---
risu_ppc.c | 41 +
1 file changed, 41 insertions(+)
create mode 100644 risu_ppc.c
diff --git a/risu_ppc.c b/risu_ppc.c
new file mode 100644
index 00
Add the ppc.risu file. It defines the format for various PowerPC
instructions.
Signed-off-by: John Arbuckle
---
ppc.risu | 527 +
++
1 file changed, 527 insertions(+)
create mode 100644 ppc.risu
diff --git a/ppc.risu b/ppc.risu
n
Makes risu usable on a PowerPC Macintosh running Mac OS X.
John Arbuckle (9):
Add ppc.risu file.
Add risu_ppc.c file.
Add risu_reginfo_ppc.c file.
Add risu_reginfo_ppc.h file
Add risugen_ppc.pm file.
Add ppc support to configure
Add verbose option.
Add end of test message
Add mo
Is there a way to define a constant in a .risu file? Something like
this:
my $upper_imm_limit = 500;
On Apr 7, 2017, at 1:49 PM, luigi burdo wrote:
Tested on PowerMac G5 Quad and 380% of system load and working on
Fedora 25 PPC64 host and Ubuntu Mate 17.04 guest (patched the 2.9
rc3)
The machine configuration was this
sudo ./qemu-system-ppc64 -cpu POWER8 -vga none -machine
pseries-2.5
On Apr 7, 2017, at 3:08 AM, Jiahuan Zhang wrote:
On 7 April 2017 at 08:26, Jiahuan Zhang
wrote:
On 6 April 2017 at 19:58, G 3 wrote:
On Apr 6, 2017, at 12:00 PM, qemu-devel-requ...@nongnu.org wrote:
Dear QEMU developers,
I need multiple ARM-based hardware emulation runing
On Apr 6, 2017, at 1:08 PM, luigi burdo wrote:
Hi i can help test it too on my two Be machine.
If some one help me to find where is the patch or where i can
download the commits
Thanks
Luigi
Here are the patches:
1/3 https://patchwork.ozlabs.org/patch/747691/
2/3 https://patch
On Apr 6, 2017, at 12:00 PM, qemu-devel-requ...@nongnu.org wrote:
Dear QEMU developers,
I need multiple ARM-based hardware emulation runing simultaneously
in one
PC.
I wander if QEMU is capble to run two system emulation at the same
time.
Or I have to use two QEMU for two system emulatio
On Apr 6, 2017, at 9:32 AM, Cédric Le Goater wrote:
On 04/06/2017 03:28 PM, G 3 wrote:
On Apr 6, 2017, at 9:26 AM, Cédric Le Goater wrote:
Hello Nikunj,
On 04/06/2017 12:22 PM, Nikunj A Dadhania wrote:
The series enables Multi-Threaded TCG on PPC64
Patch 01: Use atomic_cmpxchg in store
On Apr 6, 2017, at 9:26 AM, Cédric Le Goater wrote:
Hello Nikunj,
On 04/06/2017 12:22 PM, Nikunj A Dadhania wrote:
The series enables Multi-Threaded TCG on PPC64
Patch 01: Use atomic_cmpxchg in store conditional
02: Handle first write to page during atomic operation
03: Generate
I was wondering if someone wrote a risugen_*.pm file in python and it
still worked with risugen, would you accept that patch?
On Mar 15, 2017, at 10:25 AM, qemu-devel-requ...@nongnu.org wrote:
On Wed, Mar 15, 2017 at 07:20:25PM +1300, Phil Dennis-Jordan wrote:
This updates the FADT generated for x86/64 machine types from
Revision 1 to 3. (Based on ACPI standard 2.0 instead of 1.0) As
previously, the goal is to mak
On Mar 9, 2017, at 3:08 PM, qemu-devel-requ...@nongnu.org wrote:
v2:
- applied code review
This patchset include initial support to PPC64 (Big-Endian), that
is pretty
much the same: only some fixes in configure and risugen.
Also, it adds a better random initialization of VSX registers.
J
Does Risu support the PowerPC 970? I tried compiling it but I saw
this error:
gcc -Wall -D_GNU_SOURCE -DARCH=ppc64 -g -o risu.o -c risu.c
In file included from risu.c:29:
risu.h:27:30: error: risu_reginfo_ppc64.h: No such file or directory
make: *** [Makefile:44: risu.o] Error 1
The PowerPC
On Mar 3, 2017, at 11:21 AM, Daniel P. Berrange wrote:
On Fri, Mar 03, 2017 at 10:55:01AM -0500, G 3 wrote:
On Mar 3, 2017, at 10:44 AM, Greg Kurz wrote:
On Fri, 3 Mar 2017 10:28:00 -0500
G 3 wrote:
On Mar 3, 2017, at 9:59 AM, qemu-devel-requ...@nongnu.org wrote:
On 02/03/17 17:40
On Mar 3, 2017, at 10:58 AM, Peter Maydell wrote:
On 3 March 2017 at 15:55, G 3 wrote:
Here is the patch. I think we should let Mark or some else test it
to see if
it does fix the problem before a real patch is submitted.
---
hw/9pfs/9p-util.h | 4
1 file changed, 4 insertions
On Mar 3, 2017, at 10:44 AM, Greg Kurz wrote:
On Fri, 3 Mar 2017 10:28:00 -0500
G 3 wrote:
On Mar 3, 2017, at 9:59 AM, qemu-devel-requ...@nongnu.org wrote:
On 02/03/17 17:40, Daniel P. Berrange wrote:
On Thu, Mar 02, 2017 at 05:28:24PM +, Mark Cave-Ayland wrote:
Does anyone else see
On Mar 3, 2017, at 9:59 AM, qemu-devel-requ...@nongnu.org wrote:
On 02/03/17 17:40, Daniel P. Berrange wrote:
On Thu, Mar 02, 2017 at 05:28:24PM +, Mark Cave-Ayland wrote:
Does anyone else see the following error when trying to build git
master?
cc -I/home/build/src/qemu/git/qemu/hw/9p
Hi, would anyone like to mentor for the possible Google Summer of
Code project of adding support for Mac OS 8.6 to QEMU?
On Feb 27, 2017, at 3:59 PM, qemu-devel-requ...@nongnu.org wrote:
Hello, my name is Sergio G?mez.
It seems that QEMU has been accepted into GSoC 2017. I'm interested in
working with QEMU due to my interest in virtual machines in general.
Particularly, taking into account that I have experience
Hi I was wondering if your MTTCG patches have been tested with a
PowerPC guest yet. Also do you have a repo someone could clone to
test out all your patches?
On Feb 23, 2017, at 9:09 AM, Stafford Horne wrote:
On Mon, Feb 13, 2017 at 10:33:09PM -0500, Programmingkid wrote:
On Feb 13, 2017, at 10:25 PM, Richard Henderson wrote:
On 02/10/2017 11:39 AM, Stafford Horne wrote:
On Thu, Feb 09, 2017 at 09:10:51AM -0500, G 3 wrote:
On Feb 8, 2017, at
On Feb 8, 2017, at 11:52 PM, qemu-devel-requ...@nongnu.org wrote:
Message: 6
Date: Wed, 8 Feb 2017 20:51:32 -0800
From: Richard Henderson
To: qemu-devel@nongnu.org
Cc: sho...@gmail.com
Subject: [Qemu-devel] [PATCH 00/22] target/openrisc updates
Message-ID: <20170209045154.16868-1-...@twiddle.
On Feb 1, 2017, at 6:17 PM, Paolo Bonzini wrote:
On 01/02/2017 14:50, G 3 wrote:
I was thinking maybe we should add Rich Text Format, or maybe even a
word processing format like OpenOffice, or Microsoft Word to the
list of
possible formats. These formats are super easy to use. No
I was thinking maybe we should add Rich Text Format, or maybe even a
word processing format like OpenOffice, or Microsoft Word to the list
of possible formats. These formats are super easy to use. No
formatting rules to have to learn. All the user needs to do is just
type up their contribut
On Jan 26, 2017, at 12:30 PM, Paolo Bonzini wrote:
On 26/01/2017 18:28, G 3 wrote:
On Jan 26, 2017, at 12:00 PM, qemu-devel-requ...@nongnu.org wrote:
Hi all,
as you may know I've been collecting some ideas about
documentation for
QEMU at http://wiki.qemu-project.org/Fea
On Jan 26, 2017, at 12:00 PM, qemu-devel-requ...@nongnu.org wrote:
Hi all,
as you may know I've been collecting some ideas about documentation
for
QEMU at http://wiki.qemu-project.org/Features/Documentation.
I've now prepared a poll to understand how familiars developers are
with
variou
-ppc version: 2.5.1.1
Ubuntu 14.04
gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
GTK 2.0, libsdl1.2-dev
./configure --target-list="ppc-softmmu" --disable-xfsctl
By zero meaning, do you mean this: decr = 0
Yes.
2016-12-27 21:16 GMT+03:00 G 3 :
When I type 'info registers', I
this problem, because I using VirtualBox->Ubuntu->Qemu?
This should not be a problem. An emulator can run anywhere.
2016-12-27 18:52 GMT+03:00 G 3 :
On Dec 27, 2016, at 10:38 AM, qemu-ppc-requ...@nongnu.org wrote:
Hello, devs!
I'm using ppc-softmmu target, and in my qemu monitor
On Dec 5, 2016, at 9:15 AM, Paolo Bonzini wrote:
On 05/12/2016 14:47, G 3 wrote:
So now I have to figure out which commands to use. This script would
have to work on all operating systems that QEMU is built on. This
page
has some pretty good information on how to do this:
http
On Dec 3, 2016, at 3:41 AM, Paolo Bonzini wrote:
On 02/12/2016 23:59, Programmingkid wrote:
I thought we could use a Hosts page to sort all the host
documentation we have. It is located here: http://wiki.qemu.org/Hosts
Here is what I have so far:
AIX
Darwin
FreeBSD, NetBSD, OpenBSD
Linux
On Nov 30, 2016, at 6:58 PM, Alistair Francis wrote:
On Fri, Nov 18, 2016 at 4:53 PM, Programmingkid
wrote:
On Nov 18, 2016, at 7:31 PM, Programmingkid wrote:
On Nov 18, 2016, at 4:10 PM, Alistair Francis wrote:
On Fri, Nov 11, 2016 at 8:53 AM, G 3
wrote:
On Nov 11, 2016, at 11:31
On Nov 25, 2016, at 9:26 AM, qemu-devel-requ...@nongnu.org wrote:
Hi all,
I've been experiencing issues when installing Mac OS 9.x using
qemu-system-ppc.exe in Windows 10. After booting from CD image,
partitioning a fresh disk image often hangs Qemu. When using a
pre-partitioned disk image, th
On Nov 21, 2016, at 3:36 PM, Eric Blake wrote:
On 11/21/2016 02:12 PM, G 3 wrote:
On Nov 21, 2016, at 5:02 AM, Paolo Bonzini wrote:
On 21/11/2016 07:30, G 3 wrote:
When I try to use qemu-system-i386, I see this error message:
qobject/qjson.c:69: failed assertion `obj != NULL'.
On Nov 22, 2016, at 10:13 AM, Eric Blake wrote:
On 11/22/2016 09:02 AM, G 3 wrote:
I did run make check. It fails here:
GTESTER tests/check-qjson
qobject/qjson.c:69: failed assertion `obj != NULL'
GTester: last random seed: R02S40df2b0a1486871a176bb83135c07c90
make: *** [/Users/john/de
On Nov 22, 2016, at 7:41 AM, Eric Blake wrote:
On 11/22/2016 04:06 AM, Markus Armbruster wrote:
Eric Blake writes:
On 11/21/2016 02:36 PM, Eric Blake wrote:
The source of your problem is that your platform defines PRId64
as 'qd',
but the qemu JSON parser only recognizes lld (POSIX) or I64
On Nov 22, 2016, at 2:45 AM, qemu-devel-requ...@nongnu.org wrote:
Message: 4
Date: Tue, 22 Nov 2016 13:50:04 +1100
From: Benjamin Herrenschmidt
To: BALATON Zoltan , Mark Cave-Ayland
Cc: David Gibson , qemu-...@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-p
On Nov 21, 2016, at 3:46 PM, Eric Blake wrote:
On 11/21/2016 02:36 PM, Eric Blake wrote:
but I'd argue that using qobject_from_jsonf() is already less-than-
useful.
In fact, we are down to only a handful of users of our modified
'jsonf'
format (that is, strings that mix JSON with % modifi
On Nov 21, 2016, at 5:02 AM, Paolo Bonzini wrote:
On 21/11/2016 07:30, G 3 wrote:
When I try to use qemu-system-i386, I see this error message:
qobject/qjson.c:69: failed assertion `obj != NULL'.
This is the function where the assertion fails:
/*
* IMPORTANT: This function abor
When I try to use qemu-system-i386, I see this error message:
qobject/qjson.c:69: failed assertion `obj != NULL'.
This is the function where the assertion fails:
/*
* IMPORTANT: This function aborts on error, thus it must not
* be used with untrusted arguments.
*/
QObject *qobject_from_jsonf
I tried making a suggested command-line section in your ARM wiki
page, but my lack of experience with ARM prevents me from testing it.
What do you think of this as the suggested command-line for qemu-
system-aarch64:
qemu-system-aarch64 -m -M -drive
if=none,file=,id=hd0 -device virtio-bl
Is there an official way to test any of the PowerPC floating point
instructions in QEMU?
On Nov 17, 2016, at 10:48 AM, Edgar E. Iglesias wrote:
On Thu, Nov 17, 2016 at 10:44:15AM -0500, G 3 wrote:
On Nov 17, 2016, at 8:39 AM, Thomas Huth wrote:
On 17.11.2016 03:25, Programmingkid wrote:
When I run this test disk image: http://wiki.qemu.org/download/
ppc-virtexml507-linux
1 - 100 of 169 matches
Mail list logo