From: cov@codeaurora.org (Christopher Covington)
To: linux-arm-kernel@lists.infradead.org
Subject: [Qemu-devel] [PATCH] QEMU: ARM: boot: Load kernel at an Image friendly address
Date: Thu, 17 Apr 2014 09:34:52 -0400 [thread overview]
Message-ID: <534FD87C.4090708@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA96XGvwPM=OpqW8EU5nFksiEruGgncwqUPEWeU2ryCoJg@mail.gmail.com>
On 04/17/2014 06:02 AM, Peter Maydell wrote:
> On 2 April 2014 13:47, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 2 April 2014 13:11, Peter Crosthwaite <peter.crosthwaite@xilinx.com> wrote:
>>> Like others, I have been carrying this change locally. Good to see it up!
>>
>> Why are you all booting raw Images anyway (just out of curiosity)?
>
> Given the recent feedback from the kernel mailing list (viz "don't boot
> Image unless you really know what you're doing, the correct load
> image may change randomly depending what other board support
> is in a multikernel image, etc") maybe we should just remove the
> Image booting support instead? Clearly nobody who hasn't locally
> patched QEMU is using it at the moment...
An opportunity for a fresh start at low-level loading facilities, should
anyone be inclined to pursue it, sounds good to me.
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-04-17 13:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 3:34 [PATCH] QEMU: ARM: boot: Load kernel at an Image friendly address Joel Fernandes
2014-03-25 3:34 ` [Qemu-devel] " Joel Fernandes
2014-03-25 12:29 ` Christopher Covington
2014-03-25 12:29 ` Christopher Covington
2014-03-25 13:43 ` Joel Fernandes
2014-03-25 13:43 ` Joel Fernandes
2014-03-25 13:13 ` Peter Maydell
2014-03-25 13:13 ` [Qemu-devel] " Peter Maydell
2014-03-25 13:46 ` Joel Fernandes
2014-03-25 13:46 ` [Qemu-devel] " Joel Fernandes
2014-04-01 17:10 ` Peter Maydell
2014-04-01 17:10 ` [Qemu-devel] " Peter Maydell
2014-04-02 12:11 ` Peter Crosthwaite
2014-04-02 12:11 ` Peter Crosthwaite
2014-04-02 12:47 ` Peter Maydell
2014-04-02 12:47 ` Peter Maydell
2014-04-02 12:58 ` Peter Crosthwaite
2014-04-02 12:58 ` Peter Crosthwaite
2014-04-02 15:04 ` Christopher Covington
2014-04-02 15:04 ` Christopher Covington
2014-04-02 16:06 ` Joel Fernandes
2014-04-02 16:06 ` Joel Fernandes
2014-04-17 10:02 ` Peter Maydell
2014-04-17 13:34 ` Christopher Covington [this message]
2014-04-17 16:53 ` Joel Fernandes
2014-04-23 2:20 ` Peter Crosthwaite
2014-04-23 2:47 ` 答复: " lig.fnst at cn.fujitsu.com
2014-04-17 16:58 ` Rob Herring
2014-04-17 19:26 ` Peter Maydell
2014-04-23 2:07 ` Peter Crosthwaite
2014-04-28 16:19 ` Uwe Kleine-König
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=534FD87C.4090708@codeaurora.org \
--to=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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 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.