From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HZz4i-0006wc-7P
	for qemu-devel@nongnu.org; Fri, 06 Apr 2007 20:46:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HZz4f-0006vq-Vv
	for qemu-devel@nongnu.org; Fri, 06 Apr 2007 20:46:39 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HZz4f-0006vn-Qg
	for qemu-devel@nongnu.org; Fri, 06 Apr 2007 20:46:37 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5]
	helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <rob@landley.net>) id 1HZz17-0007HD-Nd
	for qemu-devel@nongnu.org; Fri, 06 Apr 2007 20:42:57 -0400
From: Rob Landley <rob@landley.net>
Subject: Re: [Qemu-devel] Is it possible to boot qemu-system-ppc with -kernel?
Date: Fri, 6 Apr 2007 16:57:41 -0400
References: <200704031821.46569.rob@landley.net>
	<4612F5C4.6080301@windriver.com>
In-Reply-To: <4612F5C4.6080301@windriver.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200704061657.41727.rob@landley.net>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Tuesday 03 April 2007 8:48 pm, Jason Wessel wrote:
> 
> To boot the prep machine you need to configure the kernel for prep and 
> use the zImage.prep file.  IE: CONFIG_PPC_PREP=y
> 
> Right now you selected CONFIG_PPC_CHRP

In 2.6.20.4 PPC_PREP depends on:
  (PPC64 || CLASSIC32) && PPC_MULTIPLATFORM && PPC32 && BROKEN

Broken?  Hmmm, removing that from arch/powerpc/Kconfig lets me select it, and 
then building...  And apparently, CONFIG_PPC_PREP doesn't create a zImage?

Ok, back up and try the prep defconfig.  cp prep_defconfig to .config, 
run "make ARCH=powerpc oldconfig" and...  yeesh, it prompted for a dozen 
screens full of stuff (hold down enter)...  Try the build...  Sigh, go into 
menuconfig and switch off:

 CONFIG_LOCALVERSION_AUTO - Hang build indefinitely waiting for git.

Second verse, same as the first...

Ok, that created arch/powerpc/boot/zImage, zImage.chrp, zImage.coff, 
zImage.lds, zImage.miboot, and zImage.pmac.

No zImage.prep.  How do you create this?

> In any kernel > 2.6.20 there is a bug where no PCI interrupts go to 
> sleep and the default prep loader has a size limit.
> 
> I worked around this by modifying the prep loader to accept a bigger 
> image, as well as to process the kernel arguments passed by QEMU.

How did you modify the loader?  (Are you talking about making changes to qemu, 
or to the kernel?)

And you didn't work around the PCI interrupts issue, but got it to boot 
anyway?  (Using initramfs?)

> So  
> yes it is definitely possible to boot a prep image, but there some 
> tricks.  I also only use the serial ports, so I am not certain if the 
> frame buffer actually works.

I'm just trying to get a serial console to work myself...

> Jason.

Thanks,

Rob
-- 
Penguicon 5.0 Apr 20-22, Linux Expo/SF Convention.  Bruce Schneier, Christine 
Peterson, Steve Jackson, Randy Milholland, Elizabeth Bear, Charlie Stross...