IMHO, I believe:
- python inside monitor is uncalled for (average python installation size is
big, no ?)
- xml is still too big a format for something we can do by shell script
(joke: why not yaml ?)
--
Christian
___
Qemu-devel mailing list
Qemu-devel
On Monday 23 October 2006 7:33 pm, Paul Brook wrote:
> My intention is that a machine config file would remove the "motherboard"
bits
> altogether. ie. the config file describes everything that pc_init_1 does.
The
> first half of pc.c would remain because that's device emulation.
Sounds highl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Brook wrote:
> ram {base=0; size=RAM_SIZE, physaddr=0}
> ram {base=0x8000; size=RAM_SIZE, physaddr=0}
> integrator_core{ram_size=RAM_SIZE};
> arm_cpu_pic {cpu_index=0, pic_name="CPU0"}
> integrator_pic {pic_name="PRIMARY", base=0x1400,pare
how about this ? (it's yaml, not xml)
the idea would be to store all cfg in one file and switch at boot time
which guest you want to boot...
This is just a draft, and your mileage may vary. More readings at:
http://yaml.org
http://www-128.ibm.com/developerworks/library/x-matters23.html
---
gues
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kazu wrote:
> It seems that ctrl left event before right alt makes something wrong for
> SDL_VIDEODRIVER=windib. I updated binary. SDL is patched and updated. SDL
> version is 1.2.11 so that windib is default. How about this one. It seems
> that Knoppi
Hi,
The attached patch adds IDE support on the mips target. It has been
written by Daniel Jacobowitz, and posted on [EMAIL PROTECTED],
along with another patch. He told me it is ok to submit it.
I am using it for a week, it works correctly. Could you apply it?
Thanks,
Aurelien
--
.''`. Au
I'd recommend Qemu Launcher (https://gna.org/projects/qemulaunch).
If Qemu gets a config file and a configuration utility, it should be similar
in my opinion.
_
Express yourself instantly with MSN Messenger! Download today it's FR
On 10/24/06, Blue Swirl <[EMAIL PROTECTED]> wrote:
I'd recommend Qemu Launcher (https://gna.org/projects/qemulaunch).
If Qemu gets a config file and a configuration utility, it should be similar
in my opinion.
I thought the qemu config file could be having the noble aim to be
multi-host. Usin
The current raw block drvice code fakes a TOC with one track covering
the entire disc. With this patch it attempts to read the TOC from a
cdrom device and make that information available to the ide driver
when the guest issues an ATAPI READ TOC/PMA/ATIP type 0 (read TOC)
command.
There is only su
This patch adds support for the dhcp broadcast flag to slirp's dhcp
server. If a DHCP DISCOVER/REQUEST packet is recieved with the
broadcast flag set then the response will be sent to 255.255.255.255.
-jre
Index: slirp/bootp.c
===
R
On Monday 23 October 2006 8:12 pm, Paul Sokolovsky wrote:
> Yes, machine config apparently would be a hierarchical structure,
> with cross-references. And well, there's an industrial standard to
> represent that - XML.
There's an interesting sort of natural selection at work in open source.
An
On Monday 23 October 2006 9:38 pm, Paul Sokolovsky wrote:
> Maybe. But where are new chips in qemu? Why there're still only 2
> ARM boards? How do I "stick" wi-fi card in one of them? So the concern
> is not just if it's easy to add new devices or not, but if there're means
> to actually support
On Tuesday 24 October 2006 6:47 am, Flavio Visentin wrote:
> At this point it's really cleaner and maybe simpler to use XML
Have you ever implemented a validating XML parser? I have. It only
_looks_ "clean and simple".
Rob
--
"Perfection is reached, not when there is no longer anything to add
On Monday 23 October 2006 2:37 pm, Paul Brook wrote:
> It turn out that qemu already does most of the hard work, and a code
> generation backend is fairly simple. The diff for my current implementation
> is <2k lines of common code, plus <1k lines for each of x86, amd64 and ppc32
> hosts.
My un
Hello Rob,
Wednesday, October 25, 2006, 2:28:47 AM, you wrote:
> On Monday 23 October 2006 9:38 pm, Paul Sokolovsky wrote:
>> Maybe. But where are new chips in qemu? Why there're still only 2
>> ARM boards? How do I "stick" wi-fi card in one of them? So the concern
>> is not just if it's easy t
On Wednesday 25 October 2006 00:39, Rob Landley wrote:
> On Monday 23 October 2006 2:37 pm, Paul Brook wrote:
> > It turn out that qemu already does most of the hard work, and a code
> > generation backend is fairly simple. The diff for my current
> > implementation is <2k lines of common code, plu
16 matches
Mail list logo
