All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>, Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture
Date: Tue, 12 Feb 2008 11:51:57 +1000	[thread overview]
Message-ID: <47B0FBBD.9060009@snapgear.com> (raw)
In-Reply-To: <20080208104535.GF21852@flint.arm.linux.org.uk>


Russell King - ARM Linux wrote:
> On Fri, Feb 08, 2008 at 10:43:42AM +0000, David Woodhouse wrote:
>> On Fri, 2008-02-08 at 10:23 +0000, Russell King - ARM Linux wrote:
>>> That would be misleading though - !CPU_CP15_MMU does not mean we
>>> support unaligned accesses.  It means that we may have no way to
>>> support fixing up unaligned accesses.
>> Doesn't that mean you should disallow MTD (or at least 16-bit NOR flash)
>> if !CPU_CP15_MMU, then? But at the moment you allow it?
> 
> Ask Hyok or Greg Ungerer.

I would agree that it means disabling 16-bit NOR flash, but the 8-bit
case should be fine right?

A complete disable of MTD seems like overkill. A more fine grained
approach would be better.

Regards
Greg



------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
Secure Computing Corporation                PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

  reply	other threads:[~2008-02-12  1:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 12:38 [PATCH] arch/arm/Kconfig: Make UIO available on ARM architecture Hans-Jürgen Koch
2008-02-07 12:58 ` Christoph Hellwig
2008-02-07 13:01   ` Sam Ravnborg
2008-02-07 15:09     ` Marcin Juszkiewicz
2008-02-07 16:05       ` Russell King - ARM Linux
2008-02-07 20:23         ` Sam Ravnborg
2008-02-07 20:29           ` Russell King - ARM Linux
2008-02-07 21:05             ` Sam Ravnborg
2008-02-08  9:04           ` David Woodhouse
2008-02-08  9:45             ` Russell King - ARM Linux
2008-02-08 10:18               ` David Woodhouse
2008-02-08 10:23                 ` Russell King - ARM Linux
2008-02-08 10:43                   ` David Woodhouse
2008-02-08 10:45                     ` Russell King - ARM Linux
2008-02-12  1:51                       ` Greg Ungerer [this message]
2008-02-08 10:58             ` David Woodhouse
2008-02-08 18:46               ` Sam Ravnborg
2008-02-08 18:52                 ` David Woodhouse
2008-02-09 11:39           ` Sam Ravnborg
2008-02-07 14:21   ` Russell King - ARM Linux
2008-02-07 13:02 ` Russell King - ARM Linux
2008-02-07 13:12   ` Hans-Jürgen Koch
2008-02-11  8:25     ` Hans-Jürgen Koch
2008-02-11 14:39       ` Sam Ravnborg
2008-04-10 12:21       ` Uwe Kleine-König
2008-04-10 12:27         ` Russell King - ARM Linux
2008-04-10 12:57           ` Uwe Kleine-König
2008-04-10 13:10             ` Russell King - ARM Linux
2008-04-10 13:50               ` Uwe Kleine-König
2008-04-10 18:58           ` Sam Ravnborg

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=47B0FBBD.9060009@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.