From: Rob Landley <rob@landley.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Ungerer <gerg@uclinux.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] m68k updates for 3.8
Date: Fri, 14 Dec 2012 03:08:54 -0600 [thread overview]
Message-ID: <1355476134.18402.5@driftwood> (raw)
In-Reply-To: <alpine.DEB.2.00.1212132040040.14664@ayla.of.borg> (from geert@linux-m68k.org on Thu Dec 13 13:44:14 2012)
On 12/13/2012 01:44:14 PM, Geert Uytterhoeven wrote:
> Hi Linus,
>
> The following changes since commit
> 29594404d7fe73cd80eaa4ee8c43dcc53970c60e:
> Linus Torvalds (1):
> Linux 3.7
Query: what's your test environment?
I've been trying to get m68k linux to boot in qemu on and off for years
(http://landley.net/aboriginal/bin/system-image-m68k.tar.bz2), but qemu
seems to be missing bits (mmu stuff mostly, some work's being done at
git://gitorious.org/qemu-m68k/qemu-m68k especially in the q800 branch,
but it throws a double MMU fault during kernel boot).
Somebody got one of my images to boot under aranym but they had to
patch the kernel fairly extensively to add the emulated device support
that emulator provided. It doesn't emulate real devices the way qemu
does, but qemu doesn't fully emulate the processor (just coldfire in
mainline)...
Rob
next prev parent reply other threads:[~2012-12-14 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 19:44 [git pull] m68k updates for 3.8 Geert Uytterhoeven
2012-12-14 9:08 ` Rob Landley [this message]
2012-12-14 12:04 ` Greg Ungerer
2012-12-14 21:48 ` Rob Landley
2012-12-15 0:01 ` Al Viro
2012-12-15 12:09 ` Greg Ungerer
2012-12-16 10:19 ` Geert Uytterhoeven
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=1355476134.18402.5@driftwood \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).