In message [off-list ref] you wrote:
Actually, the range of my flash is from 0xFF000000 to 0xFFFFFFFF. My
starting address of Kernel is 0xFF000000, and the starting address of
ramdisk image is FF200000, so the partitions is as following:
0xFF000000 - 0xFF1FFFFF Kernel
0xFF200000 - 0xFF9FFFFF RamDisk Image ( also my Root File System )
And I found my RootFS image is so big that waste many time while write it to
flash.
Then avoid writing it that often. Use a more efficient setup for
developoment and test, like root file system mounted over NFS.
I hope I can use MTD to distribute it into two parts, Simple RootFS and
libraries, but I don't know how to implement it?
You can use MTD to provide an additional file system which can then
be mounted by one of your startup scripts. MTD configuration and file
system building is documented in the DULG, please see
http://www.denx.de/twiki/bin/view/DULG/Manual
It is not possible to give good advice how to split data into
separate file systems, or how exactly you can mount it without
precise knowledge of your system and it's requirements. For example,
do you use a SysV init with several run levels, or a simple setup for
example based on busybox? In the end this is something which you have
to design yourself.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Let the programmers be many and the managers few -- then all will be
productive. -- Geoffrey James, "The Tao of Programming"
I have browsed the website, http://www.denx.de/twiki/bin/view/DULG/Manual.
For this example:
0x00000000-0x00060000 : "U-Boot"
0x00060000-0x00080000 : "Environment 1"
0x00080000-0x000A0000 : "Environment 2"
0x000A0000-0x000C0000 : "ASIC Images"
0x000C0000-0x001C0000 : "Linux Kernel"
0x001C0000-0x005C0000 : "Ramdisk Image"
0x005C0000-0x01000000 : "User Data"
How can I put the Environment variables or configurations in
0x00060000-0x00080000, or put User Data in 0x005C0000-0x1000000?
Use U-boot command? Or....
Best Regards,
Johnson Cheng
-----Original Message-----
From: linuxppc-embedded-bounces@ozlabs.org
[mailto:linuxppc-embedded-bounces@ozlabs.org] On Behalf Of Wolfgang Denk
Sent: Monday, August 22, 2005 4:17 PM
To: JohnsonCheng
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux Kernel MTD question
In message [off-list ref] you wrote:
Actually, the range of my flash is from 0xFF000000 to 0xFFFFFFFF. My
starting address of Kernel is 0xFF000000, and the starting address of
ramdisk image is FF200000, so the partitions is as following:
0xFF000000 - 0xFF1FFFFF Kernel
0xFF200000 - 0xFF9FFFFF RamDisk Image ( also my Root File
System )
And I found my RootFS image is so big that waste many time while write it
to
flash.
Then avoid writing it that often. Use a more efficient setup for
developoment and test, like root file system mounted over NFS.
I hope I can use MTD to distribute it into two parts, Simple RootFS and
libraries, but I don't know how to implement it?
You can use MTD to provide an additional file system which can then
be mounted by one of your startup scripts. MTD configuration and file
system building is documented in the DULG, please see
http://www.denx.de/twiki/bin/view/DULG/Manual
It is not possible to give good advice how to split data into
separate file systems, or how exactly you can mount it without
precise knowledge of your system and it's requirements. For example,
do you use a SysV init with several run levels, or a simple setup for
example based on busybox? In the end this is something which you have
to design yourself.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Let the programmers be many and the managers few -- then all will be
productive. -- Geoffrey James, "The Tao of Programming"
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded