From: Charles Manning <manningc2@actrix.gen.nz>
To: Ramya Ravichandran <rrhsin@yahoo.co.in>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Cf Card vs DiskOnChip
Date: Mon, 28 Jan 2002 14:35:20 +1300 [thread overview]
Message-ID: <20020128013905.81A0611FD@creative.actrix.co.nz> (raw)
In-Reply-To: <20020126080500.34286.qmail@web8101.in.yahoo.com>
On Sat, 26 Jan 2002 21:05, Ramya Ravichandran wrote:
> > If the CF is "embedded" and you are not going to
> > remove it while it is
> > powered up (ie. use it like you would a DOC) then
> > you quite likely do not
> > need any PCMCIA adapter chips I've seen a few
> > designs using CF this way.
>
> You have a desktop system and in this desktop system I
> just want to remove the HD and replace it with the CF
> card or DOC .Do you need adapters for this. IF DOC
> then can it be directly embedded in the motherboard.
>
> Please help.
OK so if I understand you correctly, you want to take a normal x86 system,
throw away the hand disk and put int a CF instead.
If that is what you want to do then the sandisk link shows how. All you need
is a very simple cable that goes from a standard IDE connector to a CF socket.
My understanding, which might be off, is that if you look inside a Sandisk
Flashdrive then that is what you'll find.
For all you nay-sayers, there are some good reasons to do this. One good
reason to do this over a DOC-based solution is that you don't have to load
special DOC access software or have a specail DOC-friendly BIOS. The system
can't tell the difference between a CF and a rotating disk. It's a nice easy
way to get from A toZ, especially for an exploratory product or an "embedded
PC" that's going into a vehicle or other high vibration scenario that will
shake a disk to death.
kira I reckon you're being a bit rude! An honest question deserves a useful
answer - not abuse. Help or shut up. IMHO.
-- Charles
next prev parent reply other threads:[~2002-01-28 1:29 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 [this message]
2002-01-28 6:18 ` Ramya Ravichandran
2002-01-28 17:12 ` Charles Manning
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=20020128013905.81A0611FD@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