public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Simpkins, Andy" <Andy.Simpkins@Transcomm.uk.com>
To: "Simpkins, Andy" <Andy.Simpkins@Transcomm.uk.com>
Cc: "eCos-Discuss (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] FLASH file system
Date: Mon, 03 Sep 2001 07:38:00 -0000	[thread overview]
Message-ID: <919A3A7F776FD311AFD600508B44A7F301795B8F@ramhqlon.transcomm.uk.com> (raw)

On the surface it looks like JFFS2 is just what I am looking for...

Can someone point me in the direction for JFFS2 documentation and source?
All I can find is the red hat announcement on the device and the a build for
use with the 'familiar platform' ipaq.

that should enable me to determine if this is the right thing for me to
pursue.

Has anyone (or is anyone in the process of) ported JFFS2 to eCos.
again the red hat announcement indicated that a port was soon to follow the
Linux release...


Andy

> -----Original Message-----
> From: Simpkins, Andy 
> Sent: 03 September 2001 10:18
> To: 'Andrew Lunn'; Simpkins, Andy
> Cc: eCos-Discuss (E-mail)
> Subject: RE: [ECOS] FLASH file system
> 
> 
> Andrew,
> 
> What I am looking for is something like the following...
> 
> - Ability to read and write files to FLASH
> - Because BLOCK size in flash is typically quite large (>64K) 
> then it is desirable to split blocks into sub-blocks of a 
> more reasonable size.  
> - This now leaves the problem of erasing (as the smallest 
> erase size is 1 block).
> - By leaving 1 Block free space in the file system at all 
> times it is possible to 'juggle' data around (i.e. 
> defragmenter) such that sub-blocks no-longer in use may be 
> freed up for re-use.
> - Obviously this will require 1 (or 2) blocks (possibly of a 
> smaller size) to maintain the FAT.
> 
> 
> Do you or anyone else know of such a module available in open source?
> 
> If not then I shall have to write one.  Cue Red Hat to tell 
> me about what they would like to see me provide :-)
> 
> Andy
> 
> 
> > -----Original Message-----
> > From: Andrew Lunn [ mailto:andrew.lunn@ascom.ch ]
> > Sent: 03 September 2001 09:34
> > To: Simpkins, Andy
> > Cc: eCos-Discuss (E-mail)
> > Subject: Re: [ECOS] FLASH file system
> > 
> > 
> > On Mon, Sep 03, 2001 at 09:25:45AM +0100, Simpkins, Andy wrote:
> > > Hi there,
> > > 
> > > Does anyone know if there is an eCos FLASH file handling 
> > module (i.e. treats
> > > FLASH as a disk)
> > 
> > The ROM FS can run this the FS in FLASH. Its read only. Is 
> > that what you mean?
> > 
> > Or do you mean using the flash as a block device? You open 
> /dev/flash
> > and read blocks and write blocks? Im not sure that would be very
> > efficient. The flash on my device has 256k blocks.
> > 
> >         Andrew
> > 
> 

             reply	other threads:[~2001-09-03  7:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03  7:38 Simpkins, Andy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-14 22:32 Gustav Kälvesten
2001-09-05  1:21 Dominic Ostrowski
2001-09-03  2:17 Simpkins, Andy
2001-09-03  1:26 Simpkins, Andy
2001-09-03  1:34 ` Andrew Lunn
2001-05-18  0:34 [ECOS] Flash " james chen
2001-05-18 12:24 ` Jonathan Larmour
2001-06-03 19:43   ` james chen

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=919A3A7F776FD311AFD600508B44A7F301795B8F@ramhqlon.transcomm.uk.com \
    --to=andy.simpkins@transcomm.uk.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).