From: Thomas Gleixner <tglx@linutronix.de>
To: "Hyok S. Choi" <hyok.choi@samsung.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [RFC] arm : ALIGNMENT_TRAP and MTD
Date: Fri, 23 Jun 2006 21:22:50 +0200 [thread overview]
Message-ID: <1151090570.25491.294.camel@localhost.localdomain> (raw)
In-Reply-To: <200606231635.40655.hyok.choi@samsung.com>
On Fri, 2006-06-23 at 16:35 +0900, Hyok S. Choi wrote:
> Dear MTD folks,
>
> In ARM arch, we're merging my uClinux/ARM tree into mainline.
> While merging a certain CPU support codes, we found a bit doubt on the
> conditional including of MTD configuration file in arch/arm/Kconfig.
> The CPU core has no H/W based alignment mechanism, thus can not handle unaligned access.
> However as many uClinux archs do, many of the platforms had supported MTD drivers.
>
> Currently, _only_ ARM arch includes MTD configuration file conditionally as follows:
>
> if ALIGNMENT_TRAP
> source "drivers/mtd/Kconfig"
> endif
MTD does unaligned accesses. This dependency is there since the early
2.4 kernels.
I really do not want to meddle in the ARM dependency problems. Just my
$0.02: removing this will simply open another round of bug reports
related to this problem. Search the MTD archives, we had plenty of them.
Is there a damn good reason, why the NOMMMU stuff cannot have this
active ? If it enables code which is not feasible on NOMMU there are
ways to solve such problems quite elegant.
It's not a MTD problem, it's an ARM specific requirement.
tglx
next prev parent reply other threads:[~2006-06-23 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 7:35 [RFC] arm : ALIGNMENT_TRAP and MTD Hyok S. Choi
2006-06-23 19:22 ` Thomas Gleixner [this message]
2006-06-27 13:30 ` David Woodhouse
2006-06-28 5:04 ` Hyok S. Choi
2006-06-28 9:05 ` David Woodhouse
2006-06-27 13:25 ` David Woodhouse
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=1151090570.25491.294.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=hyok.choi@samsung.com \
--cc=linux-mtd@lists.infradead.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