All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] elf2flt: fix after conversion of binutils to package infrastructure
Date: Sun, 18 Mar 2012 23:30:04 +0100	[thread overview]
Message-ID: <20120318233004.0c835fa1@skate> (raw)
In-Reply-To: <87y5qxn131.fsf@macbook.be.48ers.dk>

Hello,

Le Sun, 18 Mar 2012 20:47:14 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :

> Great, sounds good. I don't have any experience with skyeye, any
> specific reasons to use that instead of qemu?

I might have missed something, but I haven't found any of the ARM
platforms emulated by Qemu to be noMMU platforms. I have tried to build
a kernel for the Versatile platform with MMU disabled, but the build
fails. It seems that the kernel does not support to be built for any
platform with MMU disabled, though I might be wrong. If anyone knows
about one of the ARM platforms supported by Qemu to be supported in a
noMMU variant by the kernel, that would be nice.

I have also started to build a m68k kernel. This one starts booting in
Qemu, but the boot hangs with an "attempted to kill idle" panic.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-03-18 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 13:44 [Buildroot] elf2flt blues Erland Lewin
2012-03-18 15:35 ` [Buildroot] [PATCH] elf2flt: fix after conversion of binutils to package infrastructure Arnout Vandecappelle
2012-03-18 15:58   ` Thomas Petazzoni
2012-03-18 19:47     ` Peter Korsgaard
2012-03-18 22:30       ` Thomas Petazzoni [this message]
2012-03-18 19:47   ` Peter Korsgaard

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=20120318233004.0c835fa1@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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.