From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ifkrc-0001FG-Us
	for qemu-devel@nongnu.org; Wed, 10 Oct 2007 19:21:16 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Ifkrb-0001F3-Ac
	for qemu-devel@nongnu.org; Wed, 10 Oct 2007 19:21:16 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ifkrb-0001F0-57
	for qemu-devel@nongnu.org; Wed, 10 Oct 2007 19:21:15 -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 esmtp (Exim 4.60)
	(envelope-from <rob@landley.net>) id 1Ifkra-0006v2-U3
	for qemu-devel@nongnu.org; Wed, 10 Oct 2007 19:21:15 -0400
From: Rob Landley <rob@landley.net>
Subject: Re: [Qemu-devel] qemu-system-m68k and booting m68k images
Date: Wed, 10 Oct 2007 18:20:57 -0500
References: <20071007015902.GA29164@sys-0.hiltweb.site>
In-Reply-To: <20071007015902.GA29164@sys-0.hiltweb.site>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200710101820.58501.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
Cc: Ian Graeme Hilt <ian.hilt@gmail.com>

On Saturday 06 October 2007 8:59:02 pm Ian Graeme Hilt wrote:
> Two questions:
>
> 1. Why does qemu-system-m68k require a kernel image?

I'd actually be pretty happy if I could figure out which kernel image I could 
build that the sucker would boot.

"qemu-system-m68k -M ?" lists two boards: the mcf5208evb and arnewsh 5206 are 
both coldfire board.  I got gcc to build an m68k toolchain and want to run an 
actual m68k kernel, but the only Kconfig entries mentioning those are in the 
m68knommu architecture...

> 2. Is support planned for booting m68k bootable images, e.g. floppy
>    images, harddrive images?

First, is support planned for booting an m68k system at all, rather than a 
coldfire one?

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.