From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CD3Ku-0003iw-1b for qemu-devel@nongnu.org; Thu, 30 Sep 2004 11:59:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CD3Kt-0003iJ-30 for qemu-devel@nongnu.org; Thu, 30 Sep 2004 11:59:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CD3Ks-0003gp-0s for qemu-devel@nongnu.org; Thu, 30 Sep 2004 11:59:14 -0400 Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CD3Do-00062p-Ec for qemu-devel@nongnu.org; Thu, 30 Sep 2004 11:51:56 -0400 Message-ID: <415C2BE2.7070905@gmx.de> Date: Thu, 30 Sep 2004 17:53:06 +0200 From: Christian Wiese MIME-Version: 1.0 Subject: Re: [Qemu-devel] BeOS/Zeta eats 100% cpu time References: <415C0AE6.6000205@gmx.de> <2ad73a04093008366675a85f@mail.gmail.com> In-Reply-To: <2ad73a04093008366675a85f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org André Braga wrote: >That one is simple: you're booting in either monochrome or VESA mode, >because there's no native accelerated driver for the videocard QEMU >emulates, and BeOS does indeed use 100% CPU in this case. I don't know >what are the details under the hood, but this is a known fact. > > > Hmm. That could be a reason. But a strange thing is, that BeOS itself thought that it is using only little amount of cpu-time. And for example vmWare has no problem with this. So, could there be a second problem? Btw. I´ve found in the sources that now there is a Cirrus GraKa emulated. But before there were a S3 (?). Was the S3 running? Or is it possible to use the S3 emulation? I think there was a S3 driver for BeOS... Thanks so far, Chris