linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Consistently enter the kernel in ARM state
Date: Mon, 20 Jun 2011 14:40:25 +0100	[thread overview]
Message-ID: <1308577229-23681-1-git-send-email-dave.martin@linaro.org> (raw)

This series rationalises the kernel entry requirements so that
Image is entered in ARM state, just like zImage.

This should enable Image to be booted reliably for Thumb-2 kernels,
just like zImage.

The Booting documentation is updated to describe the requirement:
this resolves the ARM/Thumb ambiguity for Thumb-2 kernels; for ARM
kernels there is no implied change.

Dave Martin (4):
  ARM: head: Always Enter the kernel in ARM state
  ARM: head-nommu: Always enter the kernel in ARM state
  ARM: zImage: Jump to the decompressed kernel entry point in ARM state
  ARM: Documentation: clarify entry requirements for ARM versus Thumb-2

 Documentation/arm/Booting       |    5 +++++
 arch/arm/boot/compressed/head.S |    3 ++-
 arch/arm/kernel/head-nommu.S    |    8 ++++++++
 arch/arm/kernel/head.S          |    8 ++++++++
 4 files changed, 23 insertions(+), 1 deletions(-)

-- 
1.7.4.1

             reply	other threads:[~2011-06-20 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 13:40 Dave Martin [this message]
2011-06-20 13:40 ` [PATCH 1/4] ARM: head: Always Enter the kernel in ARM state Dave Martin
2011-06-20 13:40 ` [PATCH 2/4] ARM: head-nommu: Always enter " Dave Martin
2011-06-20 13:40 ` [PATCH 3/4] ARM: zImage: Jump to the decompressed kernel entry point " Dave Martin
2011-06-20 13:40 ` [PATCH 4/4] ARM: Documentation: clarify entry requirements for ARM versus Thumb-2 Dave Martin
2011-06-20 14:01 ` [PATCH 0/4] Consistently enter the kernel in ARM state Nicolas Pitre
2011-06-20 14:17   ` Dave Martin

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=1308577229-23681-1-git-send-email-dave.martin@linaro.org \
    --to=dave.martin@linaro.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 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).