From: Michael Schmitz <schmitzmic@googlemail.com>
To: Greg Ungerer <gerg@snapgear.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, Greg Ungerer <gerg@uclinux.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] m68k: Make sure {read,write}s[bwl]() are always defined
Date: Wed, 18 Apr 2012 19:59:20 +1200 [thread overview]
Message-ID: <4F8E7458.8030301@gmail.com> (raw)
In-Reply-To: <4F8C08F1.5050907@snapgear.com>
Greg,
>> Or do you want musb_io.h to check for
>> "!(defined(CONFIG_M68K)&& defined(CONFIG_MMU))" instead?
>
> No, I would rather see just the defined(CONFIG_M68K), and no check for
> CONFIG_MMU. I am pretty sure there is some similarity between the way
> the Atari does ISA bus interfacing to what some of the ColdFire boards
> do.
I sure hope you are wrong :-) But I think I saw some non-MMU Atari use
attempts mentioned on the list, and the ROM port ISA adapter could well
be used on non-MMU Ataris (though I'm not sure what address the ROM port
would be mapped at on those - I'm sure Andreas will know the details
there).
Michael
next prev parent reply other threads:[~2012-04-18 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 19:00 [PATCH] m68k: Make sure {read,write}s[bwl]() are always defined Geert Uytterhoeven
2012-04-16 9:30 ` Felipe Balbi
2012-04-16 11:56 ` Greg Ungerer
2012-04-16 11:56 ` Greg Ungerer
2012-04-18 7:59 ` Michael Schmitz [this message]
2012-04-18 11:49 ` Andreas Schwab
2012-04-18 12:45 ` Greg Ungerer
-- strict thread matches above, loose matches on Subject: below --
2012-04-21 20:15 Geert Uytterhoeven
2012-04-21 20:15 Geert Uytterhoeven
2012-04-15 19:00 Geert Uytterhoeven
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=4F8E7458.8030301@gmail.com \
--to=schmitzmic@googlemail.com \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-m68k@vger.kernel.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.