From: "Jörn Engel" <joern@logfs.org>
To: Markus Schiltknecht <markus@bluegap.ch>
Cc: linux-mtd@lists.infradead.org, Russell Fleitman <fleitman68@yahoo.com>
Subject: Re: Intel Turbo Memory
Date: Mon, 9 Jun 2008 09:30:27 +0200 [thread overview]
Message-ID: <20080609073026.GG13200@logfs.org> (raw)
In-Reply-To: <484CD9C0.8060105@bluegap.ch>
On Mon, 9 June 2008 09:20:32 +0200, Markus Schiltknecht wrote:
> Jörn Engel wrote:
> >It appears as if those devices are raw flash and could be accessed
> >through mtd - provided someone either has documentation or creates some
> >by reverse engineering.
>
> Isn't that the first - and so far only - device which adheres to their
> NVMHCI specification [1]?
Interesting. If that is the case then we're dealing with a weird device
indeed. "Erases ... are abstracted", OOB is 12 bytes per 512. So they
do some sort of FTL stuff, but still leave 12 out of 16 bytes of OOB
available for the user. Quite odd.
Anyway, thanks for the spec!
Jörn
--
You can take my soul, but not my lack of enthusiasm.
-- Wally
prev parent reply other threads:[~2008-06-09 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 22:58 Intel Turbo Memory Russell Fleitman
2008-06-05 6:48 ` Jörn Engel
2008-06-09 7:20 ` Markus Schiltknecht
2008-06-09 7:30 ` 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=20080609073026.GG13200@logfs.org \
--to=joern@logfs.org \
--cc=fleitman68@yahoo.com \
--cc=linux-mtd@lists.infradead.org \
--cc=markus@bluegap.ch \
/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