Public bug reported:
Trying to run 'ls' (or, anything else as far as I can tell) from a SunOS
5.8 box under RHEL 6.4 linux, I get a segfault. I've tried qemu-1.5.3,
qemu-1.6.0, and I fetched git://git.qemu-project.org/qemu.git. I've
also tried a statically linked sh from /sbin/ and it also
Also this patch adds initial support for Canon
PowerShot A1100 IS compact camera.
Signed-off-by: Antony Pavlov antonynpav...@gmail.com
---
hw/arm/Makefile.objs | 1 +
hw/arm/digic_boards.c | 88 +++
2 files changed, 89 insertions(+)
create mode
[RFC v5 1/5] hw/arm: add very initial support for Canon DIGIC SoC
[RFC v5 2/5] hw/arm/digic: prepare DIGIC-based boards support
[RFC v5 3/5] hw/arm/digic: add timer support
[RFC v5 4/5] hw/arm/digic: add UART support
[RFC v5 5/5] hw/arm/digic: add NOR ROM support
Changes since v4:
1. digic.h:
Signed-off-by: Antony Pavlov antonynpav...@gmail.com
---
hw/arm/digic.c | 16
hw/arm/digic_boards.c | 7 ++
hw/char/Makefile.objs | 1 +
hw/char/digic-uart.c | 195 +
hw/char/digic-uart.h | 45
Signed-off-by: Antony Pavlov antonynpav...@gmail.com
---
hw/arm/digic_boards.c | 64 +++
1 file changed, 64 insertions(+)
diff --git a/hw/arm/digic_boards.c b/hw/arm/digic_boards.c
index cced229..a12b673 100644
--- a/hw/arm/digic_boards.c
+++
DIGIC is Canon Inc.'s name for a family of SoC
for digital cameras and camcorders.
There is no publicly available specification for
DIGIC chips. All information about DIGIC chip
internals is based on reverse engineering efforts
made by CHDK (http://chdk.wikia.com) and
Magic Lantern
Signed-off-by: Antony Pavlov antonynpav...@gmail.com
---
hw/arm/digic.c | 28
hw/timer/Makefile.objs | 1 +
hw/timer/digic-timer.c | 114 +
hw/timer/digic-timer.h | 36
include/hw/arm/digic.h | 6 +++
5
Output from valgrind running latest qemu downloaded from git. Qemu crashed of
course.
If I can check something more, please let me know.
==29109== Memcheck, a memory error detector
==29109== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==29109== Using Valgrind-3.7.0 and
On 7 September 2013 06:45, Antony Pavlov antonynpav...@gmail.com wrote:
But Canon A1100 firmware can use this routine:
1. wait TX_RDY bit in status register;
2. write TX_RDY and some other (unknown behaviour) bit to status register;
3. write byte to TX register.
IMHO the step 2 is
On 6 September 2013 21:47, Laurent Vivier laur...@vivier.eu wrote:
This series of patch allows to set the default CPU used by linux-user qemu.
When qemu is used in a container as a binfmt interpreter we can't use the
environment variable QEMU_CPU to set the CPU id.
I definitely don't like
On 6 September 2013 19:01, Richard W.M. Jones rjo...@redhat.com wrote:
Have you tried virtio-serial on ARM at all? The port never shows up.
I don't think I've tested the serial-device part of it, but I've
used it to provide virtio console with:
-append 'root=/dev/mmcblk0 rw console=hvc0
SIGSEGVs from qemu-linux-user are expected -- this is how we track self-
modifying code in the guest binary. We catch the SIGSEGV and handle it
appropriately. In particular, SPARC binaries do this a lot because their
dynamic-linking mechanism involves self-modifying code.
If you don't run the
Le 07/09/2013 10:43, Peter Maydell a écrit :
On 6 September 2013 21:47, Laurent Vivier laur...@vivier.eu wrote:
This series of patch allows to set the default CPU used by linux-user qemu.
When qemu is used in a container as a binfmt interpreter we can't use the
environment variable QEMU_CPU to
On 7 September 2013 10:13, Laurent Vivier laur...@vivier.eu wrote:
Le 07/09/2013 10:43, Peter Maydell a écrit :
In fact, I don't understand why a given CPU id has been chosen to be the
default value. I think there is a default value not because this is the
best/most used value but because we
On Sat, Sep 07, 2013 at 09:49:24AM +0100, Peter Maydell wrote:
On 6 September 2013 19:01, Richard W.M. Jones rjo...@redhat.com wrote:
Have you tried virtio-serial on ARM at all? The port never shows up.
I don't think I've tested the serial-device part of it, but I've
used it to provide
On 09/01/2013 06:07 PM, Richard Henderson wrote:
Drop the ld/st_trampolines, loading the return address into a
parameter register directly.
Signed-off-by: Richard Henderson r...@twiddle.net
---
include/exec/exec-all.h | 4 +-
tcg/ppc/tcg-target.c| 220
On Linux hosts are you using KVM? Does it make any difference?
Is there a freely downloadable image that we can use for debugging?
Thanks,
Paolo
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Public bug reported:
Hello it's my first time doing this, since the major round of
timer/block changes in August I have not been able to have audio working
in any guest with the spice protocol.
64 bit linux , AMD SVM, IOMMUv1 ASUS M5A99FX PRO R2.0
Example command line:
qemu-system-x86_64 -m
** Tags added: spice
** Tags added: sound
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1222034
Title:
QEMU + SPICE + AUDIO = FAILURE
Status in QEMU:
New
Bug description:
Hello it's my
Hi all,Inside qemu, there is block-migration feature, like migrate -b. There is also a migrate_set_speed feature inside the monitor to control the migration thread. I am wondering can we make some setting to let migration thread yield to Io thread, or let the migration thread has the higher
Am 25.07.2013 18:24, schrieb Stefan Weil:
Signed-off-by: Stefan Weil s...@weilnetz.de
---
Makefile |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 29f1043..80aeb18 100644
--- a/Makefile
+++ b/Makefile
@@ -237,7 +237,8 @@ clean:
KVM doesnt make any difference.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1191326
Title:
QNX 4 doesn't boot on qemu = 1.3
Status in QEMU:
New
Bug description:
I am using virtual
I started writing a blog post yesterday about virtualized smartcards here:
https://blogs.gnome.org/halfline/2013/09/08/another-smartcard-post/
and while testing what I was writing I noticed an invalid PIN worked when
it shouldn't have. It turns out that typing a valid PIN once in one program in
From: Ray Strode rstr...@redhat.com
When a process in a guest uses an emulated smartcard, libcacard passes
the PIN from the guest to the PK11_Authenticate NSS function. The first
time PK11_Authenticate is called the passed in PIN is used to unlock the
certificate database. Subsequent calls to
From: Ray Strode rstr...@redhat.com
vcard_emul_reset currently only logs NSS out, but there is a TODO
for potentially sending insertion/removal events when powering down
or powering up.
For clarity, this commit moves the current guts of vcard_emul_reset to
a new vcard_emul_logout function which
25 matches
Mail list logo
