All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Stany MARCEL <smarcel@pactenovation.fr>,
	linux-m68k@vger.kernel.org, gerg@uclinux.org
Subject: Re: [PATCH 1/4] Add linux/io.h to make it compile
Date: Tue, 16 Oct 2012 14:58:03 +1000	[thread overview]
Message-ID: <507CE95B.5080602@snapgear.com> (raw)
In-Reply-To: <20121015143954.GA16696@frolo.macqel>

Hi Philippe,

On 16/10/12 00:39, Philippe De Muyter wrote:
> On Mon, Oct 15, 2012 at 04:06:47PM +0200, Stany MARCEL wrote:
>> Hello Philippe,
>>
>> It does not compile with my config (MMU on), io.h header is missing for __raw_* operations.
>
> Actually, the problem seems to be more in the .h files, that should
> provide the same set of macros/functions regardless of CONFIG_MMU
> or not.
>
> I have a similar problem with out_be32 available from asm/io.h in
> CONFIG_MMU mode, but not without CONFIG_MMU.
>
> Greg, Geert ?

Yeah, the m68k io.h family of headers is all a bit messy.
It is on my list of things to merge and clean up. It is intended
that they should supply the same set of definitions.

But in this case any driver that uses any of the read/write family
of functions should include linux/io.h. The m54xx_wdt.c code
doesn't, it is just getting definitions by accident. (As it turns
out it is getting it because asm/pgtable.h includes asm/pgtable_no.h
which includes asm/io.h -- asm/pgtable_mm.h doesn't).

Regards
Greg



>>
>> But it might compile with MMU disabled.
>>
>> Regards
>>
>> -----Message d'origine-----
>> Deá: Philippe De Muyter [mailto:phdm@macqel.be]
>> EnvoyÚá: lundi 15 octobre 2012 15:58
>> └á: Stany MARCEL
>> Ccá: linux-m68k@vger.kernel.org; gerg@uclinux.org
>> Objetá: Re: [PATCH 1/4] Add linux/io.h to make it compile
>>
>> Hello Stany,
>>
>> On Mon, Oct 15, 2012 at 02:54:37PM +0200, Stany MARCEL wrote:
>>
>>> [PATCH 1/4] Add linux/io.h to make it compile
>>
>> You could probably be more precise in your patch title :)
>>
>> What error message did you get without your patch ?
>>
>> I compile m54xx_wdt.c without CONFIG_MMU without error.
>>
>> Best regards
>>
>> Philippe
>


-- 
------------------------------------------------------------------------
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:[~2012-10-16  4:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 12:54 [PATCH 1/4] Add linux/io.h to make it compile Stany MARCEL
2012-10-15 12:54 ` [PATCH 2/4] Permit to read/write to shared page Stany MARCEL
2012-10-15 12:54 ` [PATCH 3/4] Add for MCF54xx a virtual non cached zone usable for data exchange with DMA Stany MARCEL
2012-10-15 13:22   ` [PATCH 3/4 V2] " Stany MARCEL
2012-10-16  5:15     ` Greg Ungerer
2012-10-16 10:46       ` Stany MARCEL
2012-10-16 11:23         ` Philippe De Muyter
2012-10-16 12:29         ` Greg Ungerer
2012-10-16 13:57           ` RE : " Stany MARCEL
2012-10-15 12:54 ` [PATCH 4/4] Set ACR1 cache mode depending on kernel configuration Stany MARCEL
2012-10-15 13:22   ` [PATCH 4/4 V2] " Stany MARCEL
2012-10-16  5:27     ` Greg Ungerer
2012-10-16  8:12       ` Philippe De Muyter
2012-10-16 12:06         ` Greg Ungerer
2012-10-15 13:58 ` [PATCH 1/4] Add linux/io.h to make it compile Philippe De Muyter
2012-10-15 14:06   ` Stany MARCEL
2012-10-15 14:39     ` Philippe De Muyter
2012-10-16  4:58       ` Greg Ungerer [this message]
2012-10-15 14:08 ` [PATCH 1/4 V2] Add linux/io.h to make m54xx_wdt.c compile with MMU enabled Stany MARCEL
2012-10-16  5:04   ` Greg Ungerer
2012-10-16 10:47     ` Stany MARCEL

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=507CE95B.5080602@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=phdm@macqel.be \
    --cc=smarcel@pactenovation.fr \
    /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.