public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: rrhsin@yahoo.co.in
Cc: linux-mtd@lists.infradead.org
Subject: Re: Cf Card vs DiskOnChip
Date: Tue, 29 Jan 2002 06:12:26 +1300	[thread overview]
Message-ID: <20020128173034.D1A5A1645@creative.actrix.co.nz> (raw)
In-Reply-To: <20020128061808.48848.qmail@web8105.in.yahoo.com>

>
> Thanks for all the help. I want to understand PCMCIA ,
> IDE , connectors , adapters,BIOS, hot-swapping, CF
> socket, wear levelling ... all these terms were used
> by you guys when u were helping me but being a newbie
> I don't understand these terms. Can anyone suggest
> some resources for me to understand these things.
>

Most of these are outside the scope of this discussion list.... you might 
want to call on uncle Google. 

IDE (loosely) is the way most hard drives are hooked up. Most drives are "IDE 
drives".
Compact Flash is a sub-set of PCMCIA. CF (and ATA-style PCMCIA cards) just 
look like a PCMCIA version of an IDE drive. Because they are PCMCIA capable 
yo can use extra pins to find out details about what the card is. This is 
used so that when you plug the card the system can tell the difference 
between a flash card and a modem - or whatever - and use the correct driver.

When you hook up a Compact Flash to the IDE bus, then you are not using those 
extra pins. It just looks like a disk drive. Hint: don't try hook up a modem 
to the IDE bus!

Flash has a limited number of times it can be erased. Somewhere between 1000 
and 1000,000 is typical depending on the technology, temperature, voltage. 
This is termed the "endurance". Because a disk drive/file system tesnds to 
erase/write some areas more often than others (eg. your program files will 
very seldom be written but data files and temporary files will get written a 
lot) some parts of the flash will wear out faster than others. Thus, maybe 
one file area might wear out long before the device wears out. To stop this 
happening, (or at least reduce it), wear levelling algorithms are used to 
move stuff around and level out the wearing.  Some devices do not apply wear 
levelling (eg. Compact Flash and SmartMedia). Some do (eg. full-size PCMCIA 
cards, DOC, JFFS).

The rest of what you ask is definitely beyond the scope of this discussion - 
try Google for a start.

Maybe an MTD FAQ/glossary could be useful?


-- Charles

  reply	other threads:[~2002-01-28 17:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1012026130.25150.0.camel@russ>
2002-01-26  6:29 ` Cf Card vs DiskOnChip Ramya Ravichandran
2002-01-26  7:31   ` Charles Manning
2002-01-26  8:05     ` Ramya Ravichandran
2002-01-26 13:50       ` kira brown
2002-01-26 20:06       ` Russ Dill
2002-01-28  1:35       ` Charles Manning
2002-01-28  6:18         ` Ramya Ravichandran
2002-01-28 17:12           ` Charles Manning [this message]
2002-01-28  9:21         ` kira brown
2002-01-28 10:03           ` Ramya Ravichandran
2002-01-28 18:46             ` Alessandro Staltari
2002-01-28 10:08           ` Ramya Ravichandran
     [not found]         ` <Pine.LNX.4.33.0201280914130.9494-100000@hex.linuxgrrls.org >
2002-01-28 15:26           ` Mark Sienkiewicz
2002-01-26  9:16   ` David Woodhouse
2002-01-26 15:03   ` Chris Fowler
2002-01-25 10:39 Ramya Ravichandran
2002-01-25 10:53 ` David Woodhouse
2002-01-25 11:16   ` Nikhil Goel
2002-01-25 11:57     ` David Woodhouse
2002-01-25 16:26   ` Richard Gooch
2002-01-25 16:50     ` David Woodhouse
2002-01-26  4:19       ` Ramya Ravichandran
2002-01-26  5:49         ` Russ Dill
2002-01-26  6:19           ` Ramya Ravichandran
2002-01-26 12:25         ` kira brown
2002-01-25 11:42 ` kira brown
2002-01-25 12:33   ` Ramya Ravichandran
2002-01-25 13:23     ` Robert Schwebel
2002-01-25 22:28       ` Chris Fowler
2002-01-25 14:14     ` Johan Adolfsson
2002-01-25 14:15       ` kira brown

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=20020128173034.D1A5A1645@creative.actrix.co.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rrhsin@yahoo.co.in \
    /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