All of lore.kernel.org
 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: Thu, 11 Oct 2007 15:10:52 -0400	[thread overview]
Message-ID: <20071011191052.GA5306@sys-0.hiltweb.site> (raw)
In-Reply-To: <200710110215.25947.rob@landley.net>

On Thu, Oct 11, 2007 at 02:15:25AM -0500, Rob Landley wrote:
> On Wednesday 10 October 2007 10:20:41 pm Ian Graeme Hilt wrote:
> > 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>
> 
> Er, yes.  "coldfire".  Not m68k.  Says so right on the tin.

Ok.

In my case, the target's processor is a MC68030 with a VME bus.
It was built by Microware back in the late 80s to early 90s and
has OSK (OS-9 for a MC680x0) installed.

> Back in July, Andreas Schwab posted a patch to
> upgrade the coldfire support to full m68k support
> (or at least the instructions output by gcc):
> http://lists.gnu.org/archive/html/qemu-devel/2007-07/msg00015.html
> 
> I thought it would have been merged by now (or that there would
> at least be some kind of follow up on it), but apparently not.
 
I've tried building QEmu current with gcc-3.4.6 and this patch
applied.  qemu-system-m68k hung when attempting to boot the kernel
image in coldfire-test-0.1.tar.bz2.

[...] 
 
> If there's a way to build a coldfire toolchain from the gcc 4.1.2
> release, Google isn't finding it.  gcc 4.1.2 was released Febuary
> 13, 2007, and the gcc developers announced the integration of
> coldfire support on March 9, 2007 so maybe it's in 4.2...

I think the Linux kernel supports a MC68030 and the VME option.
Even if gcc was capable of creating a kernel image for this
specific arch, I don't think this would help me(?) since I want
to boot the OSK OS floppy and harddrive images.

I've used OS9Exec from sourceforge to boot these images and it
works rather well.  A problem with it is when an OS9 command tries
to access hardware a bus error is generated.

The reason I was inquiring about the rationale behind the kernel
image is that I was going to try writing code to boot the floppy
images I have with QEmu.  Unfortunately I have very little
programming experience, so any information is helpful. 

-- 
Ian Graeme Hilt

  reply	other threads:[~2007-10-11 19:11 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
2007-10-11  7:15     ` Rob Landley
2007-10-11 19:10       ` Ian Graeme Hilt [this message]
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=20071011191052.GA5306@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.