public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Andersen <bryan@bogonomicon.net>
To: John Bradford <john@grabjohn.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Compactflash cards dying?
Date: Mon, 03 Feb 2003 15:18:18 -0600	[thread overview]
Message-ID: <3E3EDC9A.9060102@bogonomicon.net> (raw)
In-Reply-To: 200302031425.h13EP0RX015976@darkstar.example.net

Take a look at all the embedded Linux distributions.  There are 
solutions for this out there.  I haven't looked into them as I just 
stuck a hole PC into my robot.

The issue with ROM style data storage is once written, any changes 
require replacement of the devices.  That adds up after a few revisions. 
  All motherboards once had PROMS (usually windowless EPROMS) for 
storing the BIOS.  It is just the cost of FLASH type devices has come 
down to the point where they are cheep when you look at the costs of 
going about it some other way.

- Bryan

> On a somewhat-related subject, is there currently an easy way to use a
> PROM as a read-only filesystem?
> 
> I.E. I'd like to write a raw filesystem image to an PROM using a PROM
> burner then connect that, probably to the parallel port, and use it as
> a block device.
> 
> It should be fairly simple to build the parallel port -> PROM adaptor,
> as it would essentially just be a ZIF socket, and a whole load of
> latches to multiplex the limited number of I/O lines to the 32 or so
> needed for address and data, and the driver should be straightforward
> to write as well.
> 
> Or is there a reason why this hasn't been done?  PROMs are much
> cheaper than Compact Flash...




  reply	other threads:[~2003-02-03 21:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 22:30 Compactflash cards dying? Pavel Machek
2003-02-02 23:57 ` Willy Tarreau
2003-02-03 12:53   ` Pavel Machek
2003-02-03  0:36 ` Daniel Egger
2003-02-03  2:04   ` Martin K. Petersen
2003-02-03  8:39     ` Jörn Engel
2003-02-03 13:58       ` Martin K. Petersen
2003-02-03  8:50   ` Miquel van Smoorenburg
2003-02-03  7:12 ` Bryan Andersen
2003-02-03 14:08   ` Martin K. Petersen
2003-02-03 14:10     ` Padraig
2003-02-03 14:30       ` John Bradford
2003-02-03 14:25     ` John Bradford
2003-02-03 21:18       ` Bryan Andersen [this message]
2003-02-04 20:59       ` Bill Davidsen
2003-02-04 21:07         ` John Bradford
2003-02-03  7:30 ` Andreas Jellinghaus
2003-02-03 12:54   ` Pavel Machek
2003-02-03 23:12     ` David Woodhouse
2003-02-04  3:39       ` H. Peter Anvin
2003-02-04 11:24       ` Pavel Machek
2003-02-04 11:30         ` David Woodhouse
2003-02-04 19:28           ` Pavel Machek
2003-02-03 23:56 ` Roger Larsson
2003-02-04  0:10   ` David Woodhouse
2003-02-04 23:28     ` Pavel Machek
2003-02-04  0:34   ` Andrew McGregor
2003-02-04 23:27   ` Pavel Machek

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=3E3EDC9A.9060102@bogonomicon.net \
    --to=bryan@bogonomicon.net \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.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