linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "JohnsonCheng" <johnsoncheng@qnap.com.tw>
To: "'Wolfgang Denk'" <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Linux Kernel MTD question
Date: Mon, 22 Aug 2005 10:46:03 -0000	[thread overview]
Message-ID: <20050822104552.E2F9567FED@ozlabs.org> (raw)
In-Reply-To: <20050822081708.74890352B0C@atlas.denx.de>

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 <20050822030032.4917442C7E@denx.de> 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

  reply	other threads:[~2005-08-22 10:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050822030032.4917442C7E@denx.de>
2005-08-22  8:17 ` Linux Kernel MTD question Wolfgang Denk
2005-08-22 10:46   ` JohnsonCheng [this message]
     [not found] <20050823053053.67D1A42AFE@denx.de>
2005-08-23  8:59 ` Wolfgang Denk
     [not found] <20050822104924.214ED429CB@denx.de>
2005-08-22 13:07 ` Wolfgang Denk
2005-08-23  3:12   ` JohnsonCheng
2005-08-23  3:24     ` Robert P. J. Day
2005-08-23  5:31       ` JohnsonCheng
2005-08-23 19:16         ` Ricardo Scop
2005-08-24  5:02           ` JohnsonCheng
2005-08-24  8:49             ` Alex Zeffertt
2005-08-25  2:59               ` JohnsonCheng
2005-08-23  5:26   ` JohnsonCheng
2005-08-21  8:02 JohnsonCheng
2005-08-21 20:58 ` Wolfgang Denk
2005-08-22  2:56   ` JohnsonCheng

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=20050822104552.E2F9567FED@ozlabs.org \
    --to=johnsoncheng@qnap.com.tw \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=wd@denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).