From: David Woodhouse <dwmw2@infradead.org>
To: Steve Kranz <skranz@ridgerun.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD/mtdblock.c uclinux 2.0.38?
Date: Wed, 11 Jul 2001 10:11:57 +0100 [thread overview]
Message-ID: <18484.994842717@redhat.com> (raw)
In-Reply-To: <3B49B4B2.87F7E8A5@ridgerun.com>
skranz@ridgerun.com said:
> 1. Anybody know if instruction exist for installing MTD and nftl into
> an uclinux 2.0.38 tree?
Should work. Probably doesn't. Give me individual instances of places I
broke the 2.0 compile, preferably with patches, and we'll deal with it.
> 2. I'm interested in getting the SmartMedia slot of this arm7 board
> working for both read and write -- and I'd like the SmartMedia card to
> be readable/writable by a Windows machine too. Am I correct that this
> interoperability constraint will prevent me from using JFFS? I'm
> assuming that a vfat fs with MTD/nftl will do the trick for me. Yes,
> no?
You need to implement the SmartMedia translation layer format. It looks like
there's enough information on the Samsung web site to do that.
> 3. I've been glancing at MTD code and didn't think I saw any logic to
> deal with the bad (unusable) blocks of a NAND flash device. Did I just
> miss it?
Done in the SmartMedia translation layer, not in the underlying device
driver.
--
dwmw2
next prev parent reply other threads:[~2001-07-11 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-09 13:42 MTD/mtdblock.c uclinux 2.0.38? Steve Kranz
2001-07-11 9:11 ` David Woodhouse [this message]
2001-07-11 19:30 ` Steve Kranz
2001-07-11 20:36 ` Herman Oosthuysen
2001-07-11 22:28 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-07-16 23:00 Mike Voytovich
2001-07-17 7:06 ` David Woodhouse
2001-07-17 23:02 Mike Voytovich
2001-07-18 6:16 ` David Woodhouse
2001-07-18 6:50 Mike Voytovich
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=18484.994842717@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=skranz@ridgerun.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.