Re: [Qemu-devel] bug in qemu last win32 snapshot (12132007)

2008-01-02 Thread Sebastien WILLEMIJNS
On Wed, 2 Jan 2008 01:09:09 -0700, c.w. Betts [EMAIL PROTECTED] said: You have to use double slashes, like \\. - Original Message - -hda ..\toto.img does not works moving toto.img to the directory and modify commandline to -hda toto.img works ! hello, thanks of your

Re: [Qemu-devel] [RFC] 64 bit i/o

2008-01-02 Thread Robert Reif
Paul Brook wrote: On Wednesday 02 January 2008, Robert Reif wrote: Sparc32 has a 64 bit counter that should be read and written as 64 bits but that isn't supported in QEMU. I did a quick hack to add 64 bit i/o and converted sparc32 to use it and it seems to work. I'm suppling the sparc

[Qemu-devel] Usb mouse fix

2008-01-02 Thread Daniel Godás
Hi, i think ive found a little bug on the usb mouse emulation (only with the mouse, not the tablet), the wheel doesnt seem to work (it just doesnt do anything). Ive tracked the problem down to usb-hid.c: static const uint8_t qemu_mouse_hid_report_descriptor[] = { 0x05, 0x01, 0x09, 0x02,

Re: [Qemu-devel] qemu cpu-all.h exec.c

2008-01-02 Thread Paul Brook
Also the opaque parameter may need to be different for each function, it just didn't matter for the unassigned memory case. Do you really have systems where independent devices need to respond to different sized accesses to the same address? Paul

Re: [Qemu-devel] qemu cpu-all.h exec.c

2008-01-02 Thread Blue Swirl
On 1/2/08, Paul Brook [EMAIL PROTECTED] wrote: Also the opaque parameter may need to be different for each function, it just didn't matter for the unassigned memory case. Do you really have systems where independent devices need to respond to different sized accesses to the same address? I

[Qemu-devel] qemu exec.c

2008-01-02 Thread Blue Swirl
CVSROOT:/cvsroot/qemu Module name:qemu Changes by: Blue Swirl blueswir1 08/01/02 19:45:26 Modified files: . : exec.c Log message: Fix dynamically changed memory callbacks and passed opaque parameter CVSWeb URLs:

Re: [Qemu-devel] [PATCH][PPC] Use float32/64 instead of float/double

2008-01-02 Thread Aurelien Jarno
On Sun, Dec 30, 2007 at 06:32:45PM +0200, Blue Swirl wrote: On 12/30/07, Aurelien Jarno [EMAIL PROTECTED] wrote: The patch below changes the float and double types into float32 and and float64 types in the PPC code. This doesn't change anything when using softfloat-native as the types are

Re: [Qemu-devel] qemu cpu-all.h exec.c

2008-01-02 Thread Paul Brook
On Wednesday 02 January 2008, Blue Swirl wrote: On 1/2/08, Paul Brook [EMAIL PROTECTED] wrote: Also the opaque parameter may need to be different for each function, it just didn't matter for the unassigned memory case. Do you really have systems where independent devices need to respond

[Qemu-devel] [PATCH] fix possible NULL pointer use in vl.c

2008-01-02 Thread Robert Reif
diff -p -u -r1.392 vl.c --- vl.c28 Dec 2007 20:59:23 - 1.392 +++ vl.c3 Jan 2008 02:20:42 - @@ -985,6 +985,8 @@ QEMUTimer *qemu_new_timer(QEMUClock *clo QEMUTimer *ts; ts = qemu_mallocz(sizeof(QEMUTimer)); +if (!ts) +return NULL; ts-clock

[Qemu-devel] [PATCH] fix possible NULL pointer use in hw/ptimer.c

2008-01-02 Thread Robert Reif
diff -p -u -r1.5 ptimer.c --- hw/ptimer.c 17 Nov 2007 17:14:47 - 1.5 +++ hw/ptimer.c 3 Jan 2008 02:27:18 - @@ -185,6 +185,8 @@ ptimer_state *ptimer_init(QEMUBH *bh) ptimer_state *s; s = (ptimer_state *)qemu_mallocz(sizeof(ptimer_state)); +if (!s) +return

Re: [Qemu-devel] [PATCH] fix possible NULL pointer use in hw/ptimer.c

2008-01-02 Thread Paul Brook
     s = (ptimer_state *)qemu_mallocz(sizeof(ptimer_state)); +    if (!s) +        return NULL; None of the callers bother to check the return value, And even if they did I don't think there's any point trying to gracefully handle OOM. Just abort and be done with it. I suggest guaranteeing

Re: [Qemu-devel] [PATCH] fix possible NULL pointer use in hw/ptimer.c

2008-01-02 Thread Robert Reif
Paul Brook wrote: s = (ptimer_state *)qemu_mallocz(sizeof(ptimer_state)); +if (!s) +return NULL; None of the callers bother to check the return value, And even if they did I don't think there's any point trying to gracefully handle OOM. Just abort and be done with it.

[Qemu-devel] the problem of booting linux kernel from NFS

2008-01-02 Thread new bee
Hi,All: I want to boot kernel from NFS, so I compile a kernel supported NFS TUN/TAP device and change the /etc/qemu-ifup like this: #!/bin/sh sudo -p Password for $0: /sbin/ifconfig $1 192.168.15.1 when I boot the new kernel, there is the message : IP-Config: No network device available