Hello,
Can you confirm to me that if I have only one periodic timer on my
motherboard I can only have one qemu-instance running using hpet?
Thanks.
François.
Le mardi 21 août 2007 à 21:40 +0200, Luca a écrit :
> On 8/21/07, Matthew Kent <[EMAIL PROTECTED]> wrote:
> > On Sat, 2007-18-08 at 01:11
Anthony Liguori wrote:
> On Fri, 2007-08-31 at 22:13 +0200, [EMAIL PROTECTED] wrote:
>> Hi Anthony,
>>
>> I think passing only the directory name is better because it can be like a
>> "black box" : the user don't have to know how it is inside. And it is much
>> more simple to use "qemu my_pc" than
On 1 Sep 2007, at 21:26, Jorge Lucángeli Obes wrote:
I think the problem here is that the scope of this change is not
clear. I _really_ wish to keep this simple. I _really_ wish to avoid
having giant command lines and useless shell scripts.
Surely the small shell script /is/ the simple solution
On 3 Sep 2007, at 11:19, Philip Boulain wrote:
On 1 Sep 2007, at 21:26, Jorge Lucángeli Obes wrote:
I think the problem here is that the scope of this change is not
clear. I _really_ wish to keep this simple. I _really_ wish to avoid
having giant command lines and useless shell scripts.
Sure
On Mon, 2007-09-03 at 12:01 +0200, Christian Brunschen wrote:
> On 3 Sep 2007, at 11:19, Philip Boulain wrote:
> > What's the difference between having to hack about a plain-text,
> > few-lines configuration file, and a plain-text, few-lines shell
> > script?
> The same shells are not (at least
Am 03.09.2007 um 12:01 schrieb Christian Brunschen:
Saying that 'Q already handles this' means that any other program
that wants to offer a similar ease-of-use would have to be able to
read and interpret Q's configuration file format. If instead there
is a wrapper-neutral format, then each
Am 03.09.2007 um 13:40 schrieb Andreas Färber:
Do all frontends actually serialize the whole command line? I
noticed the port redirection was in both command line and special
sections for Q but I thought some info wasn't in...
Answering myself here: Obviously the architecture is not part o
On Monday 03 September 2007, Philip Boulain wrote:
> (Ok, the latter is needlessly Turing complete, so tools can't
> understand it, but "tools" are i) out of scope ii) better served by Q-
> style XML plists anyway.)
It's not if Qemu is the "shell":
#!qemu
Would just need to convince qemu to igno
On 9/2/07, Maria Zabolotnaya <[EMAIL PROTECTED]> wrote:
> 2-qemu-mplugin.patch
> Add -mplugin switch to allow loading of shared library and registering a
> machine declared in it.
Sorry to ruin your GSoC project, but the plugin system was discussed
last year, please see this thread:
http://thread.
M. Warner Losh wrote:
Is anybody working on N770 and/or N800 emulation for qemu?
Andrzej Zaborowski worked on OMAP310 for Palm Tungsten|E machine
emulation for qemu:
http://cvs.savannah.gnu.org/viewvc/qemu/hw/?root=qemu
Please note that N770/800 has other OMAP processors than Tungsten.
N77
On Sunday 02 September 2007, M. Warner Losh wrote:
> Is anybody working on N770 and/or N800 emulation for qemu?
Most of the OMAP (The main SoC used on the N770/N800) documentation is only
available under NDA, and some components don't even have open source drivers
(most notably the DSP and wirel
Hi Warner,
I've just started a project to implement the OMAP processor on QEMU.
This project is part of Mamona (http://dev.openbossa.org/trac/mamona)
and I'm continuing the Andrzej Zaborowski's work. I've already
implemented the OMAP 16xx interrupt handler, GPIO and other minor
things. I'm close t
On Mon, 2007-09-03 at 18:41 +0300, Blue Swirl wrote:
> On 9/2/07, Maria Zabolotnaya <[EMAIL PROTECTED]> wrote:
> > 2-qemu-mplugin.patch
> > Add -mplugin switch to allow loading of shared library and registering a
> > machine declared in it.
>
> Sorry to ruin your GSoC project, but the plugin syst
13 matches
Mail list logo
