From: "H. Peter Anvin" <hpa@zytor.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: Pavel Machek <pavel@ucw.cz>, Karel Zak <kzak@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux-ng@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.17 (stable)
Date: Tue, 12 Jan 2010 08:20:39 -0800 [thread overview]
Message-ID: <4B4CA157.8060906@zytor.com> (raw)
In-Reply-To: <20100112093755.GB18822@logfs.org>
On 01/12/2010 01:37 AM, Jörn Engel wrote:
> On Tue, 12 January 2010 00:19:24 -0800, H. Peter Anvin wrote:
>>
>> I believe for Smartmedia the FTL is done host side, but that there is a
>> standard-specified FTL (called CIS, Card Information System.)
>
> A CIS block/page is part of the FTL design. Not sure whether it also
> lends its name to it. I'll just take your word for it.
>
> Whether the FTL is done host side depends on the card reader and your
> definition of host side. Most old card readers implemented it in the
> driver, but some newer ones prefer to export a usb mass storage
> interface, thereby not requiring any driver CD.
>
"Host side" in this case means "not on the card". The electrical
interface to Smartmedia is, indeed, raw NAND.
-hpa
prev parent reply other threads:[~2010-01-12 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 9:33 [ANNOUNCE] util-linux-ng v2.17 (stable) Karel Zak
2010-01-08 21:43 ` H. Peter Anvin
2010-01-08 22:40 ` Andreas Dilger
2010-01-08 23:33 ` H. Peter Anvin
2010-01-11 6:36 ` Martin K. Petersen
2010-01-11 7:27 ` H. Peter Anvin
2010-01-11 14:05 ` Pavel Machek
2010-01-11 16:52 ` H. Peter Anvin
2010-01-11 20:17 ` Pavel Machek
2010-01-11 23:26 ` H. Peter Anvin
2010-01-12 13:33 ` Artem Bityutskiy
2010-01-12 13:35 ` Artem Bityutskiy
2010-01-11 19:17 ` Artem Bityutskiy
2010-01-12 7:19 ` Jörn Engel
2010-01-12 8:19 ` H. Peter Anvin
2010-01-12 9:37 ` Jörn Engel
2010-01-12 16:20 ` H. Peter Anvin [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=4B4CA157.8060906@zytor.com \
--to=hpa@zytor.com \
--cc=joern@logfs.org \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=util-linux-ng@vger.kernel.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