From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hc6oM-0000dM-0v for qemu-devel@nongnu.org; Thu, 12 Apr 2007 17:26:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hc6oK-0000ac-C9 for qemu-devel@nongnu.org; Thu, 12 Apr 2007 17:26:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hc6oK-0000aL-2L for qemu-devel@nongnu.org; Thu, 12 Apr 2007 17:26:32 -0400 Received: from mail.windriver.com ([147.11.1.11] helo=mail.wrs.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hc6k7-0000ht-3U for qemu-devel@nongnu.org; Thu, 12 Apr 2007 17:22:11 -0400 Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id l3CLM9bk008067 for ; Thu, 12 Apr 2007 14:22:09 -0700 (PDT) Message-ID: <461EA33C.9050607@windriver.com> Date: Thu, 12 Apr 2007 16:23:08 -0500 From: Jason Wessel MIME-Version: 1.0 Subject: Re: Qemu-PPC problems (was [Qemu-devel] Just to add one single point) References: <1176026443.1516.176.camel@rapid> <200704091726.13240.rob@landley.net> <1176157950.1516.360.camel@rapid> <200704111749.09810.rob@landley.net> <1176364573.6333.25.camel@rapid> <461E551E.9030803@windriver.com> <1176409219.6333.33.camel@rapid> In-Reply-To: <1176409219.6333.33.camel@rapid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 J. Mayer wrote: > On Thu, 2007-04-12 at 10:49 -0500, Jason Wessel wrote: > > A kernel > 4 MB ? Even on my amd64 I usually have kernels smaller than > this. Is there any need to have such a big kernel for anyone ? > Maybe no one else has the need but me... I built a kernel with nearly all built in code, and it just got too big, so I upped the limit. > > The problem with the frame-buffer is quite simple: it works (well, it > used to work, I did not check with such a recent kernel...) but the > kernel uses a black font on a black background. > Unfortunatelly, the reason of this bug seems not obvious (or I was not > so lucky to find it !). > > Then the frame buffer is probably grinding along just fine, eventually it will probably be fixed by someone who has the interest. > Did it really work before this patch ? Because IRQs were broken _before_ the IRQ scheme patches, for the PREP platform, which is the reason I cannot test it. > It seem to have been broken in September and the problem seems to be somewhere in the PCI bridge code... > Yes I have been able to boot the prep machine all with 2.6 kernels, since last May. My question is do you have it working now with some image on the prep machine? It is entirely possible that the 2.6.x kernel's implentation for talking to QEMU is wrong, but it was not obvious to me how it subtly changed so as to look where to fix it with the newly merged pic logic. Jason.