existing mips targets, because nanoMIPS is
not designed for use alongside any other MIPS ISA.
QEMU contributors:
- QEMU
Yongbok Kim, Stefan Markovic, Aleksandar Rikalo, Dimitrije Nikolic
Aleksandra Karadzic, Matthew Fortune, Paul Burton, James Hogan
[1]
https://www.mips.com/press/new-mips
sys/eventfd.h was being guarded only by a check for linux but does
not exist on older distributions like CentOS 5. Move the include
into the code that uses it and add an appropriate guard.
Signed-off-by: Matthew Fortune
---
migration/postcopy-ram.c | 4 ++--
1 file changed, 2 insertions(+), 2
inotify_init1 usage was guarded by a check for linux but does not
exist on older distributions like CentOS 5 resulting in build
failures.
Signed-off-by: Matthew Fortune
---
hw/usb/dev-mtp.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/hw/usb/dev
CONFIG_EPOLL was being used to guard epoll_create1 which results
in build failures on CentOS 5.
Signed-off-by: Matthew Fortune
---
aio-posix.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/aio-posix.c b/aio-posix.c
index fa7f8ab..7fd565f 100644
--- a/aio-posix.c
Fam Zheng writes:
> On Mon, 02/22 17:21, Matthew Fortune wrote:
> > Hi,
> >
> > I've recently tried building qemu with a sysroot that has support
> > for epoll_create but not epoll_create1.
> >
> > New code introduced in the following commit uses epoll_
Hi,
I've recently tried building qemu with a sysroot that has support
for epoll_create but not epoll_create1.
New code introduced in the following commit uses epoll_create1 but
guards it using CONFIG_EPOLL rather than CONFIG_EPOLL_CREATE1.
Is there any reason for this or can the guard be changed
Aurelien Jarno writes:
> On 2015-06-19 11:08, Leon Alrae wrote:
> > From: Matthew Fortune
> >
> > The BEV flag controls whether the boot exception vector is still in
> > place when starting a kernel. When cleared the exception vector at
> > EBASE (or hard cod
Leon Alrae writes:
> On 15/04/2015 10:09, Liviu Ionescu wrote:
> > Peter/Leon,
> >
> > I'm planning for my future releases, and, to avoid incompatible
> versions, I would like to help with the semihosting configuration issue,
> to speed up things. is there any chance to close this issue in the nea
Liviu Ionescu writes:
> > On 02 Apr 2015, at 13:36, Leon Alrae wrote:
> >
> >> How would you pass arguments containing whitespaces via
> >> -semihosting-config cmdline without having to reinvent shell within
> QEMU?
> >
> > I missed the fact that you already provided the implementation for
> > th
Liviu Ionescu writes:
> > On 01 Apr 2015, at 16:18, Leon Alrae wrote:
> >
> > ... This simple patch adds "arg" sub-argument which in my opinion is
> > flexible enough to satisfy semi-hosting interfaces which allocate
> > buffers at runtime (so it is possible to pass any number of strings of
> > a
Leon Alrae writes:
> On 01/03/2015 22:17, Matthew Fortune wrote:
> >> +case UHI_plog:
> >> +GET_TARGET_STRING(p, gpr[4]);
> >> +p2 = strstr(p, "%d");
> >> +if (p2) {
> >> +int char_num = p
Hi Leon,
Many thanks for implementing this interface in QEMU. I haven't reviewed
in great detail as I am not familiar enough with QEMU internals to do
so. Overall it seems to match the UHI spec. The one potential issue is
translation of errno values, I suspect some do not map 1:1.
A couple of min
> Add new command line option "-semihosting-arg". It is used for passing
> input arguments to the guest in semihosting mode. The option can be used
> multiple times. If n arguments are passed, then argument count
> (semihosting_argc) will be equal to n+1 as semihosting_argv[0] points at
> the progr
13 matches
Mail list logo
