From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Maxim Levitsky <maximlevitsky@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: linux-next: Tree for March 8 (mtd)
Date: Mon, 08 Mar 2010 09:25:18 -0800 [thread overview]
Message-ID: <4B9532FE.8030901@oracle.com> (raw)
In-Reply-To: <20100308152740.a007e8cb.sfr@canb.auug.org.au>
On 03/07/10 20:27, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20100305:
>
>
> The mtd tree still has its 2 build failures for which I applied patches.
drivers/mtd/sm_ftl.c:
sm_ftl.c:(.text+0x9c110): undefined reference to `__nand_calculate_ecc'
sm_ftl.c:(.text+0x9c123): undefined reference to `__nand_correct_data'
sm_ftl.c:(.text+0x9c14a): undefined reference to `__nand_calculate_ecc'
sm_ftl.c:(.text+0x9c15d): undefined reference to `__nand_correct_data'
sm_ftl.c:(.text+0x9c9ac): undefined reference to `__nand_calculate_ecc'
sm_ftl.c:(.text+0x9c9bf): undefined reference to `__nand_calculate_ecc'
CONFIG_SM_FTL=y
CONFIG_SM_FTL_MUSEUM=y
CONFIG_MTD_NAND=m
CONFIG_MTD_NAND_VERIFY_WRITE=y
CONFIG_MTD_NAND_ECC_SMC=y
but drivers/mtd/nand/Makefile does this:
obj-$(CONFIG_MTD_NAND) += nand.o nand_ecc.o
so having CONFIG_MTD_NAND_ECC_SMC different from CONFIG_MTD_NAND does not work.
Also:
config SM_FTL
tristate "SmartMedia/xD new translation layer"
depends on EXPERIMENTAL && BLOCK
select MTD_BLKDEVS
help
This enables new and very EXPERMENTAL support for SmartMedia/xD
EXPERIMENTAL
FTL (Flash tanslation layer)
end with .
Write support isn't yet well tested, therefore this code IS likely to
eat your card, so please don't use it together with valuable data.
Use readonly driver (CONFIG_SSFDC) instead.
config SM_FTL_MUSEUM
boolean "Additional Support for 1MiB and 2MiB SmartMedia cards"
depends on SM_FTL && MTD_NAND
select MTD_NAND_ECC_SMC
help
Very old SmartMedia cards need ECC to be calculated in the FTL
end with .
Such cards are very rare, thus enabling this option is mostly useless
end with .
Also this support is completely UNTESTED.
--
~Randy
next prev parent reply other threads:[~2010-03-08 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 4:27 linux-next: Tree for March 8 Stephen Rothwell
2010-03-08 17:25 ` Randy Dunlap [this message]
2010-03-09 2:49 ` linux-next: Tree for March 8 (mtd) David Woodhouse
2010-03-09 17:06 ` Randy Dunlap
2010-03-08 17:32 ` [PATCH -next] sound: fix opti92x-ad1848 build Randy Dunlap
2010-03-08 17:37 ` Takashi Iwai
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=4B9532FE.8030901@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).