All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Michael Schmitz <schmitzmic@googlemail.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 22:45:58 +1000	[thread overview]
Message-ID: <4F8EB786.8000000@snapgear.com> (raw)
In-Reply-To: <4F8E7458.8030301@gmail.com>

On 04/18/2012 05:59 PM, Michael Schmitz wrote:
> 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).

I wasn't referring to the ROM port exactly as it is on Atari playtforms.
But some ColdFire based boards I have seen do ISA busses with some
pretty funky wiring of addresses and data lines to be able to do 8bit
accesses on even and odd boundaries, but also allow 16bit accesses.

Regards
Greg


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

  parent reply	other threads:[~2012-04-18 12:45 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
2012-04-18 11:49     ` Andreas Schwab
2012-04-18 12:45     ` Greg Ungerer [this message]
  -- 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=4F8EB786.8000000@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitzmic@googlemail.com \
    /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.