Fadi Nasser
2004-12-22 21:17:45 UTC
Where can I get the sourcecode from? Better yet, as someone out there
must have already compiled this for 82xx PPC, does anyone know where
I can get an executable for 82xxPPC? Many thanks.
-----Original Message-----
From: owner-jffs-***@axis.com [mailto:owner-jffs-***@axis.com] On Behalf
Of Fadi Nasser
Sent: Tuesday, December 21, 2004 9:52 AM
To: David Woodhouse; Pedro Aguilar
Cc: jffs-***@axis.com; linux-***@lists.infradead.org
Subject: JFFS2 for multi-partition Flash
Hello all,
I apologize I advance for my long email but I'll try to state
The few questions that I have in a detailed fashion. My flash
(sect_size=0x20000, ***@0xFE000000) looks like this:
physmap_partitions
0x00000->0x20000 PPC hardware reset word
0x20000->0x1F00000 Filesystem section
0x1F00000->0x1F40000 U-boot
0x1F40000->0x1F80000 U-boot env
Basically, I only need a portion of Flash to use JFFS2. So I built my
Jffs2.img (padded to 0x1F00000-0x20000=0x1ee0000), burned it in flash.
/proc/mtd shows the proper partitions created (in proc at least).
Question#1
I get my jffs2.img filessize = 0x100000 (1MB) even though I'm padding to
0x1ee0000. Is this because of internal compression?
Problem#1
When linux comes up, I "mknod /dev/mtdblock1 b 31 0". If I try to "mount
-t jffs2 /dev/mtdblock1 /mnt", I see the jffs2_do_mount_fs call scanning
For the magic keys (0x1985) at offset 0x0 (where I don't have a JFFS
Image burned). How can I get the scan_medium and mount_fs files to start
at the proper offset!?
Problem#2
Even after hardcoding the offsets in the jffs2_do_fill_super call,
after the scan_medium is happy for the first 0x100000 bytes, I
start to see the msgs (0x1985 not found at 0x00100a18: xyz instead).
Jffs2_scan_eraseblock() scans every 4bytes & keeps complaining about n
ot finding the magic key (0x1985). I figured this is because my
img size is 0x100000 even though I padded it to 0x1ee0000. What am I
missing here?
Thank you so much for any pointers that you may offer.
-----Original Message-----
From: owner-jffs-***@axis.com [mailto:owner-jffs-***@axis.com] On Behalf
Of David Woodhouse
Sent: Tuesday, December 21, 2004 3:39 AM
To: Pedro Aguilar
Cc: jffs-***@axis.com; linux-***@lists.infradead.org
Subject: Re: Kernel freezing when booting with jffs2
normal -- add 'rw' on the command line if you don't want it read-only.
--
dwmw2
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to ***@axis.com
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to ***@axis.com
must have already compiled this for 82xx PPC, does anyone know where
I can get an executable for 82xxPPC? Many thanks.
-----Original Message-----
From: owner-jffs-***@axis.com [mailto:owner-jffs-***@axis.com] On Behalf
Of Fadi Nasser
Sent: Tuesday, December 21, 2004 9:52 AM
To: David Woodhouse; Pedro Aguilar
Cc: jffs-***@axis.com; linux-***@lists.infradead.org
Subject: JFFS2 for multi-partition Flash
Hello all,
I apologize I advance for my long email but I'll try to state
The few questions that I have in a detailed fashion. My flash
(sect_size=0x20000, ***@0xFE000000) looks like this:
physmap_partitions
0x00000->0x20000 PPC hardware reset word
0x20000->0x1F00000 Filesystem section
0x1F00000->0x1F40000 U-boot
0x1F40000->0x1F80000 U-boot env
Basically, I only need a portion of Flash to use JFFS2. So I built my
Jffs2.img (padded to 0x1F00000-0x20000=0x1ee0000), burned it in flash.
/proc/mtd shows the proper partitions created (in proc at least).
Question#1
I get my jffs2.img filessize = 0x100000 (1MB) even though I'm padding to
0x1ee0000. Is this because of internal compression?
Problem#1
When linux comes up, I "mknod /dev/mtdblock1 b 31 0". If I try to "mount
-t jffs2 /dev/mtdblock1 /mnt", I see the jffs2_do_mount_fs call scanning
For the magic keys (0x1985) at offset 0x0 (where I don't have a JFFS
Image burned). How can I get the scan_medium and mount_fs files to start
at the proper offset!?
Problem#2
Even after hardcoding the offsets in the jffs2_do_fill_super call,
after the scan_medium is happy for the first 0x100000 bytes, I
start to see the msgs (0x1985 not found at 0x00100a18: xyz instead).
Jffs2_scan_eraseblock() scans every 4bytes & keeps complaining about n
ot finding the magic key (0x1985). I figured this is because my
img size is 0x100000 even though I padded it to 0x1ee0000. What am I
missing here?
Thank you so much for any pointers that you may offer.
-----Original Message-----
From: owner-jffs-***@axis.com [mailto:owner-jffs-***@axis.com] On Behalf
Of David Woodhouse
Sent: Tuesday, December 21, 2004 3:39 AM
To: Pedro Aguilar
Cc: jffs-***@axis.com; linux-***@lists.infradead.org
Subject: Re: Kernel freezing when booting with jffs2
The problem is that when mounting the jffs2 filesystem it says
read-only(I'm not giving it any read-only flag in the MTD partition) and then
showsthe msg 'Warning: unable to open an initial console'
Is there a /dev/console node in your file system? Mounting read-only isnormal -- add 'rw' on the command line if you don't want it read-only.
--
dwmw2
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to ***@axis.com
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to ***@axis.com