public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* jffs super block
@ 2000-07-05  8:03 Rogelio M. Serrano Jr.
  2000-07-06 15:26 ` Alexander Larsson
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Rogelio M. Serrano Jr. @ 2000-07-05  8:03 UTC (permalink / raw)
  To: mtd

Does the jffs also have a super block on disk?

I have been trying to use jffs on DOC but i just cant get it to mount.
The jffs code could not find a single valid jffs inode on the DOC and
then dumps the disk data and then hang when I mount it after i dd a jffs
image to the it. The second time I boot I dont get any kind of output
anymore and my machine hangs. For starters, How should I write the jffs
file system on the DOC then? Should  I add a superblock on the chip?



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: jffs super block
  2000-07-05  8:03 jffs super block Rogelio M. Serrano Jr.
@ 2000-07-06 15:26 ` Alexander Larsson
  2000-07-06 15:26 ` David Woodhouse
  2000-07-06 18:44 ` Sébastien Côté
  2 siblings, 0 replies; 5+ messages in thread
From: Alexander Larsson @ 2000-07-06 15:26 UTC (permalink / raw)
  To: Rogelio M. Serrano Jr.; +Cc: mtd



On Wed, 5 Jul 2000, Rogelio M. Serrano Jr. wrote:

> Does the jffs also have a super block on disk?
> 
> I have been trying to use jffs on DOC but i just cant get it to mount.
> The jffs code could not find a single valid jffs inode on the DOC and
> then dumps the disk data and then hang when I mount it after i dd a jffs
> image to the it. The second time I boot I dont get any kind of output
> anymore and my machine hangs. For starters, How should I write the jffs
> file system on the DOC then? Should  I add a superblock on the chip?

No, jffs doesn't have a superblock. I usually just cat
my_filesystem_image > /dev/mtd0, but an empty mtd device should work as
well.

The hang seems strange though.

/ Alex






To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: jffs super block
  2000-07-05  8:03 jffs super block Rogelio M. Serrano Jr.
  2000-07-06 15:26 ` Alexander Larsson
@ 2000-07-06 15:26 ` David Woodhouse
  2000-07-06 18:44 ` Sébastien Côté
  2 siblings, 0 replies; 5+ messages in thread
From: David Woodhouse @ 2000-07-06 15:26 UTC (permalink / raw)
  To: Rogelio M. Serrano Jr.; +Cc: mtd


rogelio@evoserve.com said:
>  I have been trying to use jffs on DOC but i just cant get it to
> mount. 

You'll need to modify the doc2000 driver to be slightly better-behaved 
first. Currently, it refuses to do any writes which aren't 512-byte page 
aligned, and 512 bytes long, because it's only ever been used by the NFTL 
code so far. 

Once we've done that, JFFS looks like it ought to work OK, but remember that 
the DiskOnChip has NAND flash, and JFFS was designed to work on NOR flash. 

It looks to me as if it should be OK, but it's not tested on NAND flash yet.



--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: jffs super block
  2000-07-05  8:03 jffs super block Rogelio M. Serrano Jr.
  2000-07-06 15:26 ` Alexander Larsson
  2000-07-06 15:26 ` David Woodhouse
@ 2000-07-06 18:44 ` Sébastien Côté
  2000-07-06 19:50   ` David Woodhouse
  2 siblings, 1 reply; 5+ messages in thread
From: Sébastien Côté @ 2000-07-06 18:44 UTC (permalink / raw)
  To: Rogelio M. Serrano Jr.; +Cc: mtd

"Rogelio M. Serrano Jr." wrote:
> 
> Does the jffs also have a super block on disk?
> 
> I have been trying to use jffs on DOC but i just cant get it to mount.
> The jffs code could not find a single valid jffs inode on the DOC and
> then dumps the disk data and then hang when I mount it after i dd a jffs
> image to the it. The second time I boot I dont get any kind of output
> anymore and my machine hangs. For starters, How should I write the jffs
> file system on the DOC then? Should  I add a superblock on the chip?
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

I don't really know much about the DOC but doesn't it have it's own
filesystem (TrueFS or something like that) ?  If so, are linux drivers
available and open-sourced ?

Thanks,

-- 
Sébastien Côté


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: jffs super block
  2000-07-06 18:44 ` Sébastien Côté
@ 2000-07-06 19:50   ` David Woodhouse
  0 siblings, 0 replies; 5+ messages in thread
From: David Woodhouse @ 2000-07-06 19:50 UTC (permalink / raw)
  To: Sébastien Côté; +Cc: Rogelio M. Serrano Jr., mtd

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=UTF8, Size: 723 bytes --]

On Thu, 6 Jul 2000, [iso-8859-1] Sébastien Côté wrote:

> I don't really know much about the DOC but doesn't it have it's own
> filesystem (TrueFS or something like that) ?  If so, are linux drivers
> available and open-sourced ?

The DiskOnChip is just a clever way of attaching NAND flash chips to a
CPU. Generally it comes with the NAND Flash Translation Layer, which
emulates a block device, on top of which you put a 'normal' filesystem.

You end up with a journalled filesystem on top of what is essentially
already a journalled filesystem, and although we do have GPL'd NFTL
support, it's not 100% reliable yet.


-- 
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2000-07-06 19:52 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-07-05  8:03 jffs super block Rogelio M. Serrano Jr.
2000-07-06 15:26 ` Alexander Larsson
2000-07-06 15:26 ` David Woodhouse
2000-07-06 18:44 ` Sébastien Côté
2000-07-06 19:50   ` David Woodhouse

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox