qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: ian.hilt@gmail.com (Ian Graeme Hilt)
To: Rob Landley <rob@landley.net>
Cc: QEmu Developers Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-system-m68k and booting m68k images
Date: Wed, 10 Oct 2007 23:20:41 -0400	[thread overview]
Message-ID: <20071011032041.GA32245@sys-0.hiltweb.site> (raw)
In-Reply-To: <200710101820.58501.rob@landley.net>

On Wed, Oct 10, 2007 at 06:20:57PM -0500, Rob Landley wrote:
> 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.

Have you tried

<http://fabrice.bellard.free.fr/qemu/coldfire-test-0.1.tar.bz2>

> 
> "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.

-- 
Ian Graeme Hilt

  reply	other threads:[~2007-10-11  3:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07  1:59 [Qemu-devel] qemu-system-m68k and booting m68k images Ian Graeme Hilt
2007-10-10 23:20 ` Rob Landley
2007-10-11  3:20   ` Ian Graeme Hilt [this message]
2007-10-11  7:15     ` Rob Landley
2007-10-11 19:10       ` Ian Graeme Hilt
2007-10-19  0:16       ` Rob Landley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071011032041.GA32245@sys-0.hiltweb.site \
    --to=ian.hilt@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).