Hello again list!
A few months ago I posted a patch to fix weird colors on the Hummingberd
eXceed X server. My patch never got into CVS and now it seems as others
have the same problem with Solaris. The approach in my patch is very
simple: let SDL take care of the bit shifting.
The patch is publi
--- vl.c.orig Wed May 3 15:32:58 2006
+++ vl.cWed May 17 19:38:07 2006
@@ -43,7 +43,8 @@
#include
#ifdef _BSD
#include
-#ifndef __APPLE__
+#include
+#if !defined(__APPLE__) && !defined(__OpenBSD__)
#include
#endif
#else
@@ -292,7 +293,7 @@
/*
Hi Lonnie,
>
> Sorry, but I can't believe that is your full and unaltered command-line.
> For instance, this
> particular piece of hardware (the es1370) is only enabled if you pass
> -soundhw es1370 to qemu.
> If you're using a GUI launcher to start qemu then please consult with them
> abou
Kazu wrote:
Tuesday, May 16, 2006 8:48 PM Lonnie Mendez wrote:
Kazu wrote:
If you set /proc/sys/dev/rtc/max-user-freq to 1024 and disable cpuspeed
service that is related to SpeedStep/PowerNow! on a host OS, the clock in
guest OS works fine.
I checked it on i686/x86_64 Linux host.
Mind
Sylvain Petreolle wrote:
Hi Lonnie,
I update qemu cvs daily (and more if found on qemu-devel ;)
Complete command line is :
qemu -no-acpi -cdrom /mnt/hdb/isos/frenzy_v03_release.iso
and default frenzy boot (no acpi)
qemu -cdrom /mnt/hdb/isos/frenzy_v03_release.iso
and acpi frenzy boot
I attach
Hi Lonnie,
I update qemu cvs daily (and more if found on qemu-devel ;)
Complete command line is :
qemu -no-acpi -cdrom /mnt/hdb/isos/frenzy_v03_release.iso
and default frenzy boot (no acpi)
qemu -cdrom /mnt/hdb/isos/frenzy_v03_release.iso
and acpi frenzy boot
I attached /tmp/hwinfo.html generat
Kazu wrote:
Here is values of ticks_per_sec on Athlon 64 3000+ .
i686 host:
1790803394
1790784284
1790774719
1790798849
1790814225
x86_64 host:
1790764763
1790815837
1790816089
1790803590
1790771017
Those are some very sane values.
I attached a patch that I modifed from your patch. It c
Tuesday, May 16, 2006 7:23 PM Christian MICHON wrote:
>On 5/16/06, Kazu <[EMAIL PROTECTED]> wrote:
>> It is normal that 2.4 kernel boots faster than 2.6 kernel, isn't it? I
don't
>> know why Solaris x86 10 doesn't work.
>solaris works, it's just painfully slow.
>lots of time is wasted in ide-prob
d a patch that I modifed from your patch. It can be applied by
patch -p0. I checked it works for Athlon 64 with cpuspeed service (Power
Now!). ticks_per_sec changed dynamically but a clock of win2k guest on
x86_64 Linux host works fine.
If your guest OS is Linux, it is necessary to set clock=p