From: Chris Wulff
Signed-off-by: Chris Wulff
---
hw/Makefile.objs |5 ++
hw/altera_timer.c | 207 +
hw/altera_uart.c | 217
hw/altera_vic.c| 194 +
From: Chris Wulff
Signed-off-by: Chris Wulff
---
MAINTAINERS |5 +
arch_init.c |2 ++
arch_init.h |1 +
configure| 11 +++
cpu-exec.c | 12
From: Chris Wulff
This set of patches adds support for the Altera NiosII soft-core processor.
Included are support for the CPU core and the drivers needed to boot Linux
(Interrupt controller, Timer and Serial port.) There are quite a few changes
suggested by the first round review. These inclu
Bug is confirmed and at least one and a half year old, according to this blog
post, with a hack for solving it:
http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of q
Public bug reported:
qemu-system-x86_64 -m 1024 -nographic -cpu coreduo -icount auto -hdachs
980,16,32 -kernel asa842-vmlinuz -initrd asa842-initrd.gz -append
"ide_generic.probe_mask=0x01 ide_core.chs=0.0:980,16,32 auto nousb
console=ttyS0,9600 bigphysarea=65536 no-hlt" -net nic -serial
telnet
I have the exact same problem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1038136
Title:
lack of keycode 89 for br-abnt2 keyboards
Status in QEMU:
New
Bug description:
qemu-kvm-1.1.1
hos
Hi,
Philipp Hahn a écrit :
I tried to create a virtual VFAT floppy image on-the-fly with qemi(-kvm)-1.1.1
using the command line argument
-drive file=fat:floppy:"$WORK/floppy",if=floppy,index=0
Strange, I just tested today's QEMU git, and I have the opposite problem:
- it works with -M pc-0
Use the POSIX-specified stack_t type as the argument to sigaltstack()
rather than the legacy struct sigaltstack. This allows us to compile
on MacOSX with --with-coroutine=sigaltstack.
Signed-off-by: Peter Maydell
---
Tested on Linux and MacOSX.
coroutine-sigaltstack.c | 4 ++--
1 file changed,
Hello,
I bisected down a DOS boot problem with LSI 53C895A SCSI controller and
LSI option ROM to the following commit:
e93176d55f1eb4be1a366b51afeaf4f4c8c31d75
Core dumps aren't valid.
BTW: Nearly all KVM coredumps aren't valid anymore and have only a
garbage stack trace. Any ideas?
Thnx.
Thanks, applied.
On Mon, Oct 29, 2012 at 7:45 AM, Catalin Patulea wrote:
> This is setting the stage for a cleanup of FPREM and FPREM1 helpers while
> being
> sure that they behave same as bare metal.
>
> The test constructs operands using combinations of corner cases for the
> floating-point bi
Thanks, applied.
On Wed, Oct 31, 2012 at 9:49 AM, Jan Kiszka wrote:
> This makes "info mtree" output readable again.
>
> Signed-off-by: Jan Kiszka
> ---
> memory.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/memory.c b/memory.c
> index 243cb23..d5150f8 100644
Thanks, applied. Win2k initial display update is much faster now.
On Mon, Nov 5, 2012 at 3:45 PM, Jan Kiszka wrote:
> Cirrus is triggering this, e.g. during Win2k boot: Changes only on
> disabled regions require no topology update when transaction depth drops
> to 0 again.
>
> Signed-off-by: Jan
Thanks, applied.
On Sun, Nov 4, 2012 at 8:42 PM, Stefan Weil wrote:
> A compiler warning is caused by the unused local function reinit_timers
> on non-POSIX hosts. Include that function only for POSIX hosts.
>
> Signed-off-by: Stefan Weil
> ---
> qemu-timer.c |2 ++
> 1 file changed, 2 inse
Thanks, applied.
On Sun, Nov 4, 2012 at 5:41 PM, BALATON Zoltan wrote:
> Keep saving display surface parameters at init and using these cached
> values instead of getting them when needed. Not sure why this is
> needed (maybe due to the interaction with the vga device) but not
> doing this broke
Thanks, applied. Fixes also Win2k boot.
On Sun, Nov 4, 2012 at 8:16 AM, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Since 0b57e287, cpu_memory_rw_debug already triggers a TB invalidation.
> As it doesn't (and cannot) set is_cpu_write_access=1 but "consumes" the
> currently executed TB, the tb_inval
Dear Gerhard Wiesinger,
> On 10.11.2012 00:52, Peter Maydell wrote:
> > On 10 November 2012 00:45, Marek Vasut wrote:
> >> Gerd Hoffmann wrote:
> >>> Question is just whenever we'll go silently fixup stuff in console.c or
> >>> use assert()s to enforce callers getting this correct. I'd tend to u
Hello
I'm trying to test linux kernel 2.6.29 for ARM in qemu. Iḿ using
qemu1.2.0, compiled with command
./configure --disable-sdl --disable-kvm
--target-list=arm-linux-user,arm-softmmu
sudo make install
I have compiled the kernel with Versatile configuration
make ARCH=arm CROSS_COMPILE=arm-none
On Fri, Nov 9, 2012 at 7:13 AM, Gerhard Wiesinger wrote:
> On 08.11.2012 22:07, Gerd Hoffmann wrote:
>>
>>Hi,
>>
>>> I think this is fixing this at the wrong level. Either we
>>> should require that drivers (in this case vmware_vga.c)
>>> must not call dpy_gfx_update() with out of range values
On Tue, Nov 6, 2012 at 4:41 AM, Evgeny Voevodin wrote:
> Signed-off-by: Evgeny Voevodin
> Reviewed-by: Richard Henderson
> ---
> target-alpha/translate.c |6 ++--
> target-arm/translate.c|6 ++--
> target-cris/translate.c |9 +++---
> target-i386/translate.c
On Tue, Nov 6, 2012 at 4:41 AM, Evgeny Voevodin wrote:
> Signed-off-by: Evgeny Voevodin
> Reviewed-by: Richard Henderson
> ---
> target-alpha/translate.c |8 ++---
> target-arm/translate.c|8 ++---
> target-cris/translate.c | 10 +++---
> target-i386/translate.c
On 10.11.2012 09:55, Paolo Bonzini wrote:
Il 10/11/2012 09:30, Gerhard Wiesinger ha scritto:
2.) Added debug code to block.c and to block/vmdk.c to verify
correctness
Same here. Also, please use the tracing infrastructure---a lot of the
debug
messages you're adding, though not all, are in fact
Hello,
I tried to create a virtual VFAT floppy image on-the-fly with qemi(-kvm)-1.1.1
using the command line argument
-drive file=fat:floppy:"$WORK/floppy",if=floppy,index=0
Everything worked fine until I added the additional "-M pc-0.14" command line
argument: Then I only get an empty floppy
Il 10/11/2012 09:30, Gerhard Wiesinger ha scritto:
>>> 2.) Added debug code to block.c and to block/vmdk.c to verify
>>> correctness
>> Same here. Also, please use the tracing infrastructure---a lot of the
>> debug
>> messages you're adding, though not all, are in fact already available
>> (not
>>
On 09.11.2012 09:26, Paolo Bonzini wrote:
Il 08/11/2012 20:05, Gerhard Wiesinger ha scritto:
Fixed a MAJOR BUG in VMDK files on file boundaries on reads
and ALSO ON WRITES WHICH MIGHT CORRUPT THE IMAGE AND DATA!!
Triggered for example with the following VMDK file (partly listed):
# Extent d
Fixed a MAJOR BUG in VMDK files on file boundaries on reads
and ALSO ON WRITES WHICH MIGHT CORRUPT THE IMAGE AND DATA!!
Triggered for example with the following VMDK file (partly listed):
# Extent description
RW 4193792 FLAT "XP-W1-f001.vmdk" 0
RW 2097664 FLAT "XP-W1-f002.vmdk" 0
RW 4193792 F
25 matches
Mail list logo
