From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
rmk@arm.linux.org.uk, Adrian Bunk <bunk@stusta.de>
Subject: Re: [RFC: 2.6 patch] let arm use drivers/Kconfig
Date: Fri, 21 Apr 2006 11:32:35 +0200 [thread overview]
Message-ID: <20060421093235.GA32710@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1145566451.11909.111.camel@pmac.infradead.org>
On Thu, 20 April 2006 21:54:11 +0100, David Woodhouse wrote:
> On Thu, 2006-04-20 at 14:06 +0200, Adrian Bunk wrote:
> > > This dependency is incorrect. It's only one or two chip-specific drivers
> > > which require that the architecture correctly handle alignment traps,
> > > and even then it's only actually apparent when used with JFFS2 which
> > > actually _gives_ it an unaligned buffer occasionally. Everything else
> > > works fine.
> >
> > Can anyone tell me which chip-specific drivers are affected by this
> > issue so that I can send a patch?
>
> Disabling those chip drivers isn't necessarily the answer, since they
> can still be used in most cases; just not for JFFS2. Perhaps we should
> just disable JFFS2 if BROKEN_UNALIGNED is set -- or disable JFFS2 on NOR
> flash if it's set.
mtd->flags would be a good place for that. Unlike many other things
previously in there, it is a device property that matters.
Jörn
--
Data expands to fill the space available for storage.
-- Parkinson's Law
prev parent reply other threads:[~2006-04-21 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 14:48 [RFC: 2.6 patch] let arm use drivers/Kconfig Adrian Bunk
2006-04-17 14:55 ` David Woodhouse
2006-04-20 12:06 ` Adrian Bunk
2006-04-20 20:54 ` David Woodhouse
2006-04-21 9:32 ` Jörn Engel [this message]
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=20060421093235.GA32710@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=bunk@stusta.de \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rmk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox