public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: merge mmu and non-mmu bitops.h
Date: Fri, 24 Jun 2011 15:12:05 +1000	[thread overview]
Message-ID: <4E041CA5.1030302@snapgear.com> (raw)
In-Reply-To: <BANLkTimmPO3Vyt-rxD2_9B3rsS-DWtho8g@mail.gmail.com>

Hi Geert,

On 24/06/11 03:30, Geert Uytterhoeven wrote:
> On Thu, Jun 23, 2011 at 03:28,<gerg@snapgear.com>  wrote:
>> @@ -10,6 +10,9 @@ config ARCH_MAY_HAVE_PC_FDC
>> áconfig ARCH_USES_GETTIMEOFFSET
>> á á á ádef_bool y
>>
>> +config CPU_HAS_BITFIELDS
>> + á á á bool
>> +
>> áconfig EISA
>> á á á ábool
>> á á á á---help---
>> @@ -223,6 +226,7 @@ comment "Processor type"
>>
>> áconfig M68020
>> á á á ábool "68020 support"
>> + á á á select CPU_HAS_BITFIELDS
>> á á á áhelp
>> á á á á áIf you anticipate running this kernel on a computer with a MC68020
>> á á á á áprocessor, say Y. Otherwise, say N. Note that the 68020 requires a
>
> Upon second thought, this won't work for multi-CPU kernels, as there's
> no runtime
> check. The logic needs to be reverted, like:
>
> config CPU_HAS_NO_BITFIELDS
>          bool
>
> config M680000
>          bool "68000 support"
>          select CPU_HAS_NO_BITFIELDS
>
> so a kernel built to run on both 68000 and 68020 will not use the
> bitfield instructions.
> Sorry I didn't realize that earlier.

Yep, good point. I'll rework this again and lets see what that
comes out like.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

  reply	other threads:[~2011-06-24  5:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-23  1:28 [PATCH] m68k: merge mmu and non-mmu bitops.h gerg
2011-06-23 17:30 ` Geert Uytterhoeven
2011-06-24  5:12   ` Greg Ungerer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-24  5:45 gerg
2011-06-26 12:21 ` Geert Uytterhoeven
2011-06-27  2:10   ` Greg Ungerer
2011-06-03  6:51 gerg
2011-06-03 11:02 ` Finn Thain
2011-06-03 11:10   ` Greg Ungerer
2011-05-18  5:32 gerg

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=4E041CA5.1030302@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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