mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Landley <rob@landley.net>
Cc: Sam Ravnborg <sam@ravnborg.org>, Greg Ungerer <gerg@snapgear.com>,
	linux-kernel@vger.kernel.org, dwmw2@infradead.org,
	linux-next@vger.kernel.org
Subject: Re: make headers_install broken for ARCH=m68k in 2.6.29-rc7.
Date: Fri, 13 Mar 2009 09:25:15 +0100	[thread overview]
Message-ID: <10f740e80903130125u39abf6c2h2a61f6bb18e7500e@mail.gmail.com> (raw)
In-Reply-To: <200903122225.04560.rob@landley.net>

On Fri, Mar 13, 2009 at 04:25, Rob Landley <rob@landley.net> wrote:
> Keep in mind I still haven't found an emulator for m68k that actually boots a
> linux kernel, so my m68k support is purely theoretical.  (I poked at mess and
> uae a bit today, but they don't do the "qemu -kernel" thing I'm using for the
> other targets, and qemu itself only seems to support coldfire and not a full-
> blown m68k.)  I'm following up on this because it's a regression.  Under
> 2.6.28 the m68k target was building a kernel and root filesystem, but I don't
> have hardware to run it and have never been able to test it, so isn't really
> very useful for me.  It's really just there so that if qemu grows the rest of
> m68k support (patches have been submitted but not merged), I'll be ready.

An atari_defconfig kernel (at least the one from Linus-yesterday) boots fine on
aranym (http://aranym.org).

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  parent reply	other threads:[~2009-03-13  8:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  9:37 Rob Landley
2009-03-12  9:58 ` Sam Ravnborg
2009-03-12 20:03   ` Rob Landley
2009-03-12 20:58     ` Sam Ravnborg
2009-03-12 23:24       ` Stephen Rothwell
2009-03-12 21:02     ` Sam Ravnborg
2009-03-12 22:40       ` Geert Uytterhoeven
2009-03-13  3:25         ` Rob Landley
2009-03-13  7:04           ` Greg Ungerer
2009-03-13  8:25             ` Sam Ravnborg
2009-03-13  8:33               ` Geert Uytterhoeven
2009-03-13  8:59                 ` Sam Ravnborg
2009-03-13 10:52                   ` Greg Ungerer
2009-03-13 12:14                     ` Geert Uytterhoeven
2009-03-16 12:40                       ` Greg Ungerer
2009-03-16 20:20                         ` Rob Landley
2009-03-16 22:08                           ` Geert Uytterhoeven
2009-03-16 23:09                             ` Greg Ungerer
2009-03-16 23:10                           ` Greg Ungerer
2009-03-18  4:03                             ` Rob Landley
2009-03-18  5:34                               ` Greg Ungerer
2009-03-18 18:12                                 ` Rob Landley
2009-03-18 23:53                                   ` Greg Ungerer
2009-03-19  7:59                                   ` Geert Uytterhoeven
2009-03-19  8:41                                     ` Rob Landley
2009-03-13  8:25           ` Geert Uytterhoeven [this message]
2009-03-13  6:53         ` Greg Ungerer
2009-04-01 16:57 ` Lennart Sorensen
2009-04-01 19:03   ` Sam Ravnborg
2009-04-01 19:48     ` Lennart Sorensen
2009-04-01 20:23       ` Geert Uytterhoeven
2009-04-01 22:59         ` Lennart Sorensen
2009-04-02  2:14           ` Rob Landley
2009-04-02 21:59             ` Lennart Sorensen
2009-04-03  0:24               ` Rob Landley
2009-04-03  4:10                 ` Lennart Sorensen

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=10f740e80903130125u39abf6c2h2a61f6bb18e7500e@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=dwmw2@infradead.org \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®