Re: [Qemu-devel] u-boot on 'qemu-system-mips64 -M mips'

2010-06-22 Thread Rtp
KAWAKATSU Noritaka writes: > Hi, Hi, > > I have built u-boot binary for 'qemu-system-mips -M mips'. > It is fine to run ths u-boot binary. > But the same u-boot binary does not run on 'qemu-system-mips64 -M mips'. > > I do not understand what happends on the qemu-mips64 execution. > Is this a b

[Qemu-devel] [PATCH] hw/usb-msd: fix some usb requests

2010-03-10 Thread Rtp
The usb-msd device emulation needs some small tweaks in the requests emulations. For instance, the reset/maxlun requests are class/interface specific so requests for them with the type class and recipient interface bits sets have to be handled. Signed-off-by: Arnaud Patard --- diff --git a/hw/us

Re: [Qemu-devel] Adding support for MIPS64 as host

2010-02-05 Thread Rtp
pinery writes: Hi, > 於 四,2010-02-04 於 22:56 +0530,Utkarsh Sopan 提到: >> >> Can you tell me what is the status of adding MIPS64 support? >> as at the wiki page it showed Red earlier. >> On Wed, Feb 3, 2010 at 10:29 PM, Laurent Desnogues >> wrote: >> On Wed, Feb 3, 2010 at 5:53 PM, Utkars

Re: [Qemu-devel] [PATCH 14/14] Add -fstack-protector-all to CFLAGS

2009-12-31 Thread Rtp
"Kirill A. Shutemov" writes: Hi, > -fstack-protector-all emit extra code to check for buffer overflows, > such as stack smashing attacks. This is done by adding a guard > variable to functions with vulnerable objects. > > Signed-off-by: Kirill A. Shutemov > --- > configure |1 + > 1 files

Re: [Qemu-devel] [PATCH 12/14] linux-user/mmap.c: fix warnings with _FORTIFY_SOURCE

2009-12-31 Thread Rtp
"Kirill A. Shutemov" writes: Hi, > CCi386-linux-user/mmap.o > cc1: warnings being treated as errors > /usr/src/RPM/BUILD/qemu-0.11.92/linux-user/mmap.c: In function 'mmap_frag': > /usr/src/RPM/BUILD/qemu-0.11.92/linux-user/mmap.c:253: error: ignoring return > value of 'pread', declared wi

Re: [Qemu-devel] [PATCH] linux-user: use realpath for emulation dir paths

2009-12-04 Thread Rtp
Riku Voipio writes: Hi, > On Fri, Oct 02, 2009 at 02:25:36PM +0200, Paul Bolle wrote: >> Note that I have some reservations about the current init_paths() and >> path() code: >> - their names seem to confusing. Maybe those should be init_base() and >> base() or something similar; >> - why does i