From: Michael Brian Willis <willis@arlut.utexas.edu>
To: Mirek23 <miroslaw.dach@psi.ch>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Flash paritioning and JFFS2
Date: Thu, 23 Aug 2007 11:08:57 -0500 [thread overview]
Message-ID: <1187885337.5160.55.camel@louie> (raw)
In-Reply-To: <12293748.post@talk.nabble.com>
On Thu, 2007-08-23 at 06:36 -0700, Mirek23 wrote:
> Could someone advice me how to configure Linux kernel to make use of the
> Flash (with above mentioned partitions and JFFS2.
The Denx U-boot and Linux Guide (DULG) will tell you how to configure
the kernel for MTD devices and will give some good general information:
http://www.denx.de/wiki/view/DULG/FlashFilesystemsMTD
> I do not know however which specific options to enable for MTD/JFFS2 since
> it has many sub options.
The following post has some relevant information for your setup:
http://osdir.com/ml/linux.uclinux.devel/2005-12/msg00130.html
> I do not know also where to place:
> -the partition information (which I have mentioned above)
The partition information probably should go in a file that you create
for your board located at "drivers/mtd/maps/<your_file>.c"
> -the start (0xFF800000) and end (0xFFBFFFFF) physical location of my Flash
> memory.
I think this information just needs to be defined in your board's .h
file in u-boot. I don't think you need to specify this in any linux
config files.
I hope this info helps.
Regards,
Michael Willis
Applied Research Labs - University of Texas
willis@arlut.utexas.edu
next prev parent reply other threads:[~2007-08-23 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 13:36 Flash paritioning and JFFS2 Mirek23
2007-08-23 16:08 ` Michael Brian Willis [this message]
2007-09-07 15:23 ` Mirek23
2007-09-07 15:55 ` Michael Brian Willis
2007-09-28 9:51 ` Mirek23
2007-09-28 21:09 ` Mirek23
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=1187885337.5160.55.camel@louie \
--to=willis@arlut.utexas.edu \
--cc=linuxppc-embedded@ozlabs.org \
--cc=miroslaw.dach@psi.ch \
/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).