From: Scott Anderson <sanders@mvista.com>
To: Alex J Lennon <ajlennon@arcom.co.uk>
Cc: David Woodhouse <dwmw2@infradead.org>, mtd@infradead.org
Subject: Re: sbc-mediagx
Date: Fri, 15 Sep 2000 20:23:53 +0000 [thread overview]
Message-ID: <39C28559.CDA25297@mvista.com> (raw)
In-Reply-To: NEBBLLDBMLGONJHPHHEKIEMNCHAA.ajlennon@arcom.co.uk
Alex J Lennon wrote:
> Also , there is a discussion of a possible pre-cursor to FlashFx in DDJ, May
> '93
> - although I haven't managed to source this .
You can get all the articles/source from 1988 up to now on the
Dr. Dobb's CD/Release 9:
http://www.ddj.com/cdrom/
It's $100US though. Here's a list of the FLASH articles that I
found on my Release 8 CD:
May 93
FLASH FILE SYSTEMS by Drew Gislason
Flash memory packaged in solid-state, credit card-size PCMCIA cards is
starting to change the face of embedded and portable systems. Drew
examines Flash file systems and presents one that's FAT-like.
Feb 95
THE MICROSOFT FLASH FILE SYSTEM
by Peter Torelli
Peter examines flash file systems for DOS, focusing on the mechanics
behind a flash file system based on the Microsoft data structures.
Oct 95
INSIDE FLASH MEMORY
by Brian L. Dipert
Direct-execute flash memory systems don't require the gigabyte hard
disks and 64-Mbit DRAM arrays common in desktop systems.
The May 93 article has source that simply allocates a FLASH sector
for every sector of a FAT file system. It doesn't do erases. He
discusses that there is a better way, which he called "Byte-oriented
Flash File System", but there isn't much detail there. What he
does say is that at Datalight (his employer) they use a linked
list of records with each header containing "approximately 12 bytes
(describing the data's owner) and a variable-length data field".
I do not see any mention of an FTL. This last point interested
me because the article is from May 93 and the imfamous M-systems
patent was filed Mar 93.
Scott Anderson
scott_anderson@mvista.com MontaVista Software Inc.
(408)328-9214 490 Potrero Ave.
http://www.mvista.com Sunnyvale, CA 94086
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-09-15 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NEBBLLDBMLGONJHPHHEKGEMLCHAA.ajlennon@arcom.co.uk>
2000-09-14 12:54 ` sbc-mediagx David Woodhouse
2000-09-14 13:12 ` sbc-mediagx Alex J Lennon
2000-09-14 13:20 ` sbc-mediagx David Woodhouse
2000-09-15 20:23 ` Scott Anderson [this message]
2000-09-29 17:47 re[2]: SBC-MediaGX Tony Questad
2000-09-30 11:19 ` SBC-MediaGX Alex J Lennon
-- strict thread matches above, loose matches on Subject: below --
2000-09-29 12:55 SBC-MediaGX Michiel Ronsse
2000-09-29 15:15 ` SBC-MediaGX David Given
2000-09-29 17:20 ` SBC-MediaGX Michiel Ronsse
[not found] <39C08AB9.1DF0409B@arcom.co.uk>
2000-09-14 10:59 ` sbc-mediagx David Given
2000-09-14 11:45 ` sbc-mediagx Kira Brown
2000-09-13 16:27 sbc-mediagx David Given
2000-09-13 16:43 ` sbc-mediagx David Woodhouse
2000-09-13 17:08 ` sbc-mediagx David Given
2000-09-13 17:37 ` sbc-mediagx David Given
2000-09-13 18:10 ` sbc-mediagx David Given
2000-09-14 9:04 ` sbc-mediagx David Woodhouse
2000-09-14 10:03 ` sbc-mediagx David Given
2000-09-14 11:15 ` sbc-mediagx David Given
2000-09-14 9:35 ` sbc-mediagx David Vrabel
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=39C28559.CDA25297@mvista.com \
--to=sanders@mvista.com \
--cc=ajlennon@arcom.co.uk \
--cc=dwmw2@infradead.org \
--cc=mtd@infradead.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