Hello.
I am operating linux-2.4.21 on Dbau1100.
ApplicationXIP patched linux-2.4.21.
(It is a reference as for http://tree.celinuxforum.org/)
And, I want to make mount cramfs on flash.
The data of cramfs is stored in physical address 0xbf000000 of flash with
0x1000.
It stored it by using tftp with u-boot.
=============
# md bf000000
bf000000: 28cd3d45 00010000 00000000 00000000 E=.(............
bf000010: 706d6f43 73736572 52206465 53464d4f Compressed ROMFS
bf000020: f6fedb08 e452945a 94403278 43bdbefa ....Z.R.x2@....C
bf000030: 706d6f43 73736572 00006465 00000000 Compressed......
bf000040: 000041ed 00000014 000004c0 000081a4 .A..............
bf000050: 00000457 00000602 61746164 7478742e W.......data.txt
bf000060: 00000081 34339c78 35313632 34b0b733 ....x.3426153..4
bf000070: 651c32e0 9947328e 302a4ca3 d37cd101 .2.e.2G..L*0..|.
bf000080:
=============
Storage in Flash is sure to have succeeded.
And, the patch of applicationXIP is appropriated with Linux-2.4.21, and
when the mount is done from physaddr, magic number cannot acquire cramfs.
BF000000 has been passed to ioremap though linux-2.4.21/fs/cramfs/inode.c
was confirmed.
The data is 0 though the virtual address has come back to the return value
from ioremap.
The MTD flash driver is not operating it.
Is it wrong something?
=================
# mount -t cramfs -o physaddr=0xbf000000 none /mnt/cramfs
===dmesg==========
cramfs: checking physical address 0xbf000000 for linear cramfs image
__ioremap call phys_addr1=bf000000
__ioremap size=1000
cramfs: virtual address = c1038000
cramfs: readb virt_addr = 0
cramfs: first magic = 0
cramfs: size = 0
cramfs: flags = 0
cramfs: future = 0
cramfs: signature =
at offset 0, no cramfs magic: trying 512...
cramfs: second magic = 0
cramfs: wrong magic
=============
Tefs
_________________________________________________________________
迷惑メールやウイルスへの対策も万全「MSN Hotmail」
http://promotion.msn.co.jp/hotmail/
