From: Mark Sienkiewicz <ms@wavix.com>
To: kira brown <kira@hex.linuxgrrls.org>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Cf Card vs DiskOnChip
Date: Mon, 28 Jan 2002 10:26:59 -0500 [thread overview]
Message-ID: <5.1.0.14.1.20020128092633.00a75640@mail.wavix.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0201280914130.9494-100000@hex.linuxgrrls.org >
>I'm sorry, I just don't have much respect for people who say things like
>'cost is more important than reliability'. Probably becasue I've cleaned
>up their messes so often.
This guy is just asking about how to use flash. He isn't going to include
the entire cost/benefit analysis of his project in the posting, so he just
summarizes it by saying "cost is more important". There is no reason to
assume that he hasn't thought of the implications of the decision, or even
that he has any other choice. If you make your product so expensive that
nobody buys it, it is a failure no matter how reliable it is. Cost is
always an important factor.
>When designing an embedded system it's important to start by looking at
>your application rather than by looking at what technologies you
>understand and kludging the design to make it all fit.
But don't forget labor costs. If I use a system that I already know
everything about, I don't have to spend time learning about it.
Lots of embedded industrial systems are just desktop PCs or ruggedized
desktop PCs for exactly that reason. They work just fine, and for
a lower cost than some of the alternatives.
>I think someone needs to tell us what they actually need from a storage
>device, and then we can help them, rather than saying 'I need 128M of
>somethign exactly like a hard disc' which is clearly a specification
>derived from trying to make a desktop system embedded.
I don't think that is clear at all. You can't tell the architecture of a
system solely by looking at storage requirements. Maybe he just has a lot
of data.
Mark S.
next prev parent reply other threads:[~2002-01-28 15:16 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
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 [this message]
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=5.1.0.14.1.20020128092633.00a75640@mail.wavix.com \
--to=ms@wavix.com \
--cc=kira@hex.linuxgrrls.org \
--cc=linux-mtd@lists.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