> >> >> > I've been considering a machine config file for a while, but
> >> >> > haven't come up with a coherent way of representing everything yet.
> >>
> >>I'm glad this discussion was brought up on the list. And I'd like
> >> to also bring back another related issue - what about providing
>
Hello Paul,
Tuesday, October 24, 2006, 3:36:40 AM, you wrote:
> On Tuesday 24 October 2006 01:12, Paul Sokolovsky wrote:
>> Hello Paul,
>>
>> Monday, October 23, 2006, 11:29:52 PM, you wrote:
>> > On Monday 23 October 2006 21:01, Rob Landley wrote:
>> >> On Sunday 22 October 2006 2:27 pm, Paul Br
On Tuesday 24 October 2006 01:12, Paul Sokolovsky wrote:
> Hello Paul,
>
> Monday, October 23, 2006, 11:29:52 PM, you wrote:
> > On Monday 23 October 2006 21:01, Rob Landley wrote:
> >> On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
> >> > I've been considering a machine config file for a whi
> > The things are what I was asking about. Assuming that QEMU has support
> > for the appropriate processor type, support for the right bus
> > controller(s), and support for various devices that can attach to that
> > bus, what other information is needed to completely specify a machine?
> > (Y
Hello Paul,
Monday, October 23, 2006, 11:29:52 PM, you wrote:
> On Monday 23 October 2006 21:01, Rob Landley wrote:
>> On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
>> > I've been considering a machine config file for a while, but haven't come
>> > up with a coherent way of representing ev
On 24/10/06, Rob Landley <[EMAIL PROTECTED]> wrote:
On Monday 23 October 2006 4:29 pm, Paul Brook wrote:
> On Monday 23 October 2006 21:01, Rob Landley wrote:
> > On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
> > > I've been considering a machine config file for a while, but haven't
come
>
> > Not really. I guess a generic key/value pair is sufficient for most
> > things (base address, model number, etc).
>
> The things are what I was asking about. Assuming that QEMU has support for
> the appropriate processor type, support for the right bus controller(s),
> and support for various
On Monday 23 October 2006 4:29 pm, Paul Brook wrote:
> On Monday 23 October 2006 21:01, Rob Landley wrote:
> > On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
> > > I've been considering a machine config file for a while, but haven't
come
> > > up with a coherent way of representing everythin
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/10/23 21:37:34
Modified files:
target-sparc : op.c translate.c
Log message:
wrwim insn fix (Paul Robinson)
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/op.c?cvsro
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/10/23 21:31:01
Modified files:
linux-user : main.c
Log message:
sparc64 syscall fix (Blue Swirl)
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/linux-user/main.c?cvsroot=qemu&
Hi again,
Sorry I read the wrong line: it is qemu-sparc which is failing. I'll see
the issue with Blue Swirl.
Regards,
Fabrice.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/10/23 21:25:11
Modified files:
target-mips: op.c translate.c
Log message:
add support for cvt.s.d and cvt.d.s (Aurelien Jarno)
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/t
In message: <[EMAIL PROTECTED]>
Rob Landley <[EMAIL PROTECTED]> writes:
: > Seems to me they both address roughly the same
: > issues with roughly the same considerations.
:
: Using a *.PIF file is the Windows way. Using the command line is Linux.
Except for complicated things, lik
Rob Landley wrote:
What's the difference between a shell script to cover qemu and a
#!/bin/qemu config file?
The shell script works now, and you're proposing breaking it?
No, I'm not. I'm genuinely asking about functional differences.
Am I missing any significant
John Morris wrote:
On Mon, 2006-10-23 at 05:45, Xavier Gnata wrote:
Hi,
I have been asked to disable the capability to close qemu by clicking on
the SDL window x icon.
Any comments?
Totally disabling close is pretty drastic. When the VM has went wrong
closing it is a valid option.
> > Seems to me they both address roughly the same
> > issues with roughly the same considerations.
>
> Using a *.PIF file is the Windows way. Using the command line is Linux.
There's plenty of prior art for using config files on unix/linux systems.
I'm not saying we should remove all commandlin
On 10/23/06, K. Richard Pixley <[EMAIL PROTECTED]> wrote:
What's the difference between a shell script to cover qemu and a
#!/bin/qemu config file?
Not everyone may run QEMU under a POSIX-ish command-line shell. There
are several active operating systems in the world, and several people
fiddli
On Monday 23 October 2006 1:50 pm, K. Richard Pixley wrote:
> Rob Landley wrote:
> > On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
> >
> >> Is there any work going on now to add config file support?
> >>
> >> Chuck Brazie
> >> [EMAIL PROTECTED]
> >>
> > As a random end-user, I
On Monday 23 October 2006 21:01, Rob Landley wrote:
> On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
> > I've been considering a machine config file for a while, but haven't come
> > up with a coherent way of representing everything yet.
>
> Do you at least have a list of everything that need
On Mon, 2006-10-23 at 05:45, Xavier Gnata wrote:
> Hi,
> I have been asked to disable the capability to close qemu by clicking on
> the SDL window x icon.
> Any comments?
Totally disabling close is pretty drastic. When the VM has went wrong
closing it is a valid option. How about trapping close
On Sunday 22 October 2006 2:27 pm, Paul Brook wrote:
> I've been considering a machine config file for a while, but haven't come up
> with a coherent way of representing everything yet.
Do you at least have a list of everything that needs to be represented? (I
have a list but am fairly certain
On Monday 23 October 2006 19:04, K. Richard Pixley wrote:
> Paul Brook wrote:
> > Better to just teach qemu how to generate code.
> > In fact I've already done most of the infrastructure (and a fair amount
> > of the legwork) for this. The only major missing function is code to do
> > softmmu load/
"K. Richard Pixley" <[EMAIL PROTECTED]> wrote:
> Rob Landley wrote:
> > On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
> >
> >> Is there any work going on now to add config file support?
> >>
> >> Chuck Brazie
> >> [EMAIL PROTECTED]
> >>
> > As a random end-user, I really
K. Richard Pixley a écrit :
Well, perhaps. Except that with gcc, we get to leverage the ongoing gcc
optimizations, bug fixes, new cpu support, debugger support, etc.
Granted, not all of these are going to be relevant to the qemu
environment, but in a contest between gcc generated code and qe
On Sunday 22 October 2006 9:45 pm, Johannes Schindelin wrote:
> > I was pondered trying to get tcc to build qemu,
>
> (since tcc only supports x86 targets, this is not really a solution.)
No, it supports arm as well. (And I merged a recent patch to support arm
EABI.) I remember hearing about a
Paul Brook wrote:
Better to just teach qemu how to generate code.
In fact I've already done most of the infrastructure (and a fair amount of the
legwork) for this. The only major missing function is code to do softmmu
load/store ops.
https://nowt.dyndns.org/
Well, perhaps. Except that with gc
On Monday 23 October 2006 18:41, K. Richard Pixley wrote:
> Martin Guy wrote:
> >> Now, gcc4 can produce code with several return instructions (with no
> >> option to turn that of, as far as I understand). You cannot cut them
> >> out,
> >> and therefore you cannot chain the simple functions.
> >
>
Johannes Schindelin wrote:
On Sun, 22 Oct 2006, Rob Landley wrote:
Basically, gcc changed in a way that broke qemu.
Yes, they did. But even if I understand your frustration (which I share),
I also understand the gcc people. After all, using gcc to create the
blocks for
Rob Landley wrote:
On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
Is there any work going on now to add config file support?
Chuck Brazie
[EMAIL PROTECTED]
As a random end-user, I really like being able to run qemu without a config
file, configuring it entir
Martin Guy wrote:
Now, gcc4 can produce code with several return instructions (with no
option to turn that of, as far as I understand). You cannot cut them
out,
and therefore you cannot chain the simple functions.
...unless you also map return instructions within the generated
functions into
Wolfgang Schildbach wrote:
>I stumbled upon the same problem as Bill Rossi (see his post below):
>
>The current cvs version of qemu fails to compile on my machine because
>CLOCK_MONOTONIC is not defined in my glibc. According to clock_gettime(3),
>systems that define this functionality have _POS
On 23/10/06, Jonathan Dieter <[EMAIL PROTECTED]> wrote:
This is just a small (I hope) feature request. Is there any way that
there could be a "-vnc-and-sdl" option that would allow simultaneous VNC
and SDL access to the virtual machine?
Actually multiple interfaces shouldn't be very difficult
Hello list,
This patch implements the semihosting call to retrieve command line
arguments from the host environment. Without this patch, neither
arm-non-eabi-gcc compiled executables (which use semihosting) nor
ARM-compiler compiled executables can read command line arguments. It
works for bot
Paul Brook wrote:
We already do that. It doesn't stop gcc putting the return in the middle
of the function.
Paul
void f1();
void f2();
void f(int *z, int x, int y)
{
if (x) {
*z = x;
f1();
} else {
*z = y;
f2();
}
asm volatile ("");
}
wor
> > We already do that. It doesn't stop gcc putting the return in the middle
> > of the function.
> >
> > Paul
>
> void f1();
> void f2();
>
> void f(int *z, int x, int y)
> {
> if (x) {
> *z = x;
> f1();
> } else {
> *z = y;
> f2();
> }
> asm volatil
Paul Brook wrote:
That's exactly what my gcc4 hacks do.
It gets complicated because a x86 uses variable length insn encodings so
you don't know where insn boundaries are, and a jmp instruction is larger
than a ret instruction so it's not always possible to do a straight
replacement.
how
> > That's exactly what my gcc4 hacks do.
> >
> > It gets complicated because a x86 uses variable length insn encodings so
> > you don't know where insn boundaries are, and a jmp instruction is larger
> > than a ret instruction so it's not always possible to do a straight
> > replacement.
>
> how a
Paul Brook wrote:
On Monday 23 October 2006 09:16, Martin Guy wrote:
Now, gcc4 can produce code with several return instructions (with no
option to turn that of, as far as I understand). You cannot cut them out,
and therefore you cannot chain the simple functions.
...unless you also m
Hello,I would like to manage VM from the host by using the -serial pipe. I try this but that doesn't work:$: mknode command$: qemu -serial pipe:command debianThen I try to read the message from the command pipe :
$: cat commandNothing append..I try to send command to the vm$: echo "root" > commandN
Hi, Jan and Jeremie.
Thank you for your reply.
I think your result is for SDL_VIDEODRIVER=windib. I updated the binary. How
about this one? Does AltGr key work for you?
http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-20061023-keyboard.zip
Regards,
Kazu
Sent: Monday, October 23, 2006 7:35 PM
Xavier Gnata a écrit :
Hi,
Hi,
I have been asked to disable the capability to close qemu by clicking on
the SDL window x icon.
The goal is to avoid lay users to shutdown the running OS under Qemu in
a not clean way.
The patch is pretty simple. It adds a runtime -no-quit option.
This patc
On Monday 23 October 2006 12:48, Jan Marten Simons wrote:
> In my opinion config files should _always only_ be *an alternative* to a
> long command line.
>
> Basically you should be able to do anything with both configuration
> options, be it command line or a config file (or a combination of both)
On Monday 23 October 2006 09:16, Martin Guy wrote:
> > Now, gcc4 can produce code with several return instructions (with no
> > option to turn that of, as far as I understand). You cannot cut them out,
> > and therefore you cannot chain the simple functions.
>
> ...unless you also map return instru
In my opinion config files should _always only_ be *an alternative* to a
long command line.
Basically you should be able to do anything with both configuration
options, be it command line or a config file (or a combination of both).
Ciao,
Jan
Christian MICHON schrieb:
> On 10/22/06, Rob Landley
I stumbled upon the same problem as Bill Rossi (see his post below):
The current cvs version of qemu fails to compile on my machine because
CLOCK_MONOTONIC is not defined in my glibc. According to clock_gettime(3),
systems that define this functionality have _POSIX_MONOTONIC_CLOCK and
_POSIX_TI
This is just a small (I hope) feature request. Is there any way that
there could be a "-vnc-and-sdl" option that would allow simultaneous VNC
and SDL access to the virtual machine?
Thanks,
Jonathan Dieter
___
Qemu-devel mailing list
Qemu-devel@nong
On 10/22/06, Rob Landley <[EMAIL PROTECTED]> wrote:
As a random end-user, I really like being able to run qemu without a config
file, configuring it entirely on the command line. I'd be highly
disappointed if qemu turned into another Wine.
Rob
we've a lot to gain from it. Think twice: the she
On Sun, 22 Oct 2006, Aurelien Jarno wrote:
Could somebody please have a look to the patch (or even merge it)?
Looks ok to me.
Regards,
Marius
--
Marius Groeger <[EMAIL PROTECTED]>
SYSGO AG Embedded and Real-Time Software
Voice: +49 6136 9948 0 FAX: +49 6
Hi,
I have been asked to disable the capability to close qemu by clicking on
the SDL window x icon.
The goal is to avoid lay users to shutdown the running OS under Qemu in
a not clean way.
The patch is pretty simple. It adds a runtime -no-quit option.
Any comments?
Xavier.
--
##
Kazu schrieb:
> Hi,
>
> I made German language environment on Windows XP Japanese host.
> I investigated a problem of AltGr key.
>
> If you have a German keyboard, please use this binary and tell me the data
> which is displayed on console window when AltGr key is pressed.
>
> I want to know the re
Now, gcc4 can produce code with several return instructions (with no
option to turn that of, as far as I understand). You cannot cut them out,
and therefore you cannot chain the simple functions.
...unless you also map return instructions within the generated
functions into branches to the soon-
51 matches
Mail list logo
