mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: michael <trimarchi@gandalf.sssup.it>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org,
	Michael Trimarchi <trimarchimichael@yahoo.it>,
	linux-kernel@vger.kernel.org
Subject: [Fwd: Re: JFFS2 as rootfs on DataFlash]
Date: Thu, 21 Feb 2008 14:50:30 +0100	[thread overview]
Message-ID: <47BD81A6.7080009@gandalf.sssup.it> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Re: JFFS2 as rootfs on DataFlash --]
[-- Type: message/rfc822, Size: 2780 bytes --]

From: michael <trimarchi@gandalf.sssup.it>
To: Ulf Samuelsson <ulf.samuelsson@atmel.com>
Subject: Re: JFFS2 as rootfs on DataFlash
Date: Wed, 20 Feb 2008 09:36:11 +0100
Message-ID: <47BBE67B.6030804@gandalf.sssup.it>

hi,
> I have build JFFS2 for dataflash using buildroot.
> It was some time ago though.
>
> You do need to have the -s 0x210 and -e 0x2100.
> Note that using old mtd S/W will break the JFFS2,
> since old MTD assumes that pages are 2^n.
>
> You need to fix the mtd S/W in the linux kernel/root fs
> AND you need to change the mtd used to generate the file system.
>
>   
I'm using the 2.6.24 tree. Take a look:

 Inode      node at 0x00002724, totlen 0x00000115, #ino     21, 
version    16, isize   461972, csize      209, dsize     1056, offset    
14784
         Inode      node at 0x0000283c, totlen 0x00000117, #ino     21, 
version    17, isize   461972, csize      211, dsize     1056, offset    
15840
         Inode      node at 0x00002954, totlen 0x00000334, #ino     21, 
version    18, isize   461972, csize      752, dsize     1056, offset    
16896

This a short dump of an image create with mkfs.jffs2 using your setting.

Inode      node at 0x002a8ae8, totlen 0x000007a6, #ino    700, 
version     4, isize     8192, csize     1890, dsize     4096, 
offset     4096
         Inode      node at 0x002a9290, totlen 0x00000607, #ino    700, 
version     5, isize    12288, csize     1475, dsize     4096, 
offset     8192
         Inode      node at 0x002a9898, totlen 0x00000549, #ino    700, 
version     6, isize    16384, csize     1285, dsize     4096, offset    
12288
         Inode      node at 0x002a9de4, totlen 0x000006b7, #ino    700, 
version     7, isize    20480, csize     1651, dsize     4096, offset    
16384

This is created by linux, filling it just copy file.

    Inode      node at 0x00042000, totlen 0x00000a40, #ino     21, 
version    75, isize   461972, csize     2556, dsize     4096, offset   
229376
         Inode      node at 0x00042a40, totlen 0x00000abe, #ino     21, 
version    76, isize   461972, csize     2682, dsize     4096, offset   
233472
         Inode      node at 0x00043500, totlen 0x00000363, #ino     21, 
version    77, isize   461972, csize      799, dsize      986, offset   
237568
This is created by me using only the erase blocksize.

As you can see the inode data can be 4096 and it is wrong to have 1056.

Regards Michael



                 reply	other threads:[~2008-02-21 13:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47BD81A6.7080009@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=trimarchimichael@yahoo.it \
    /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

all inboxes | Powered by JetHome®