Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] m68k: flat one memory region works with small kernel patch
Date: Wed, 17 Aug 2016 08:57:08 +0300	[thread overview]
Message-ID: <20160817055708.GI3368@tarshish> (raw)
In-Reply-To: <20160817054959.GA20899@waldemar-brodkorb.de>

Hi Waldemar,

On Wed, Aug 17, 2016 at 07:49:59AM +0200, Waldemar Brodkorb wrote:
> Greg Ungerer fixed recently a bug in the Linux kernel, which
> allows to use one memory region again.
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
>  arch/Config.in                                     |  2 +-
>  .../patches/linux/m68knommu-fix-signal.patch       | 45 ++++++++++++++++++++++
>  configs/qemu_m68k_mcf5208_defconfig                |  2 +
>  3 files changed, 48 insertions(+), 1 deletion(-)
>  create mode 100644 board/qemu/m68k-mcf5208/patches/linux/m68knommu-fix-signal.patch
> 
> diff --git a/arch/Config.in b/arch/Config.in
> index b980e05..73d240f 100644
> --- a/arch/Config.in
> +++ b/arch/Config.in
> @@ -331,7 +331,7 @@ choice
>  
>  config BR2_BINFMT_FLAT_ONE
>  	bool "One memory region"
> -	depends on !BR2_m68k
> +	depends on BR2_m68k || BR2_bfin

This change excludes other noMMU arches (e.g. ARM). Is that intended?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

      reply	other threads:[~2016-08-17  5:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  5:49 [Buildroot] [PATCH] m68k: flat one memory region works with small kernel patch Waldemar Brodkorb
2016-08-17  5:57 ` Baruch Siach [this message]

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=20160817055708.GI3368@tarshish \
    --to=baruch@tkos.co.il \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox