From: John Smith <John.Smith@arrows.demon.co.uk>
To: linux-mtd@lists.infradead.org
Subject: Re: UBI and OneNand
Date: Mon, 6 Nov 2006 20:16:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20061106T205324-87@post.gmane.org> (raw)
In-Reply-To: 1162806360.5636.19.camel@localhost.localdomain
Frank Haverkamp <haver <at> vnet.ibm.com> writes:
>
> Hi John,
>
> On Sat, 2006-11-04 at 08:22 +0000, John wrote:
> > I have a board with a MIPS core and a OneNAND flash. ...
> >
> > I have made the kernel from ubi-2.6.git run on my board. Now I would be
> > grateful for answers to some questions to help me get UBI going.
> >
> > 1. Should I expect UBI to run on OneNAND without change, or should I
> > expect to have to write or adapt some code?
>
> UBI should run on mostly any mtd device. I tried it on NAND as well as
> NOR mtds.
I have now tried it. It does run.
>
> >
> > 3. My attempt to build the ubi tools from the git
> > users/haver/mtd-utils.git failed. The tools use the argp
> > functions to parse command line args, but my root file system
> > based on uclibc doesn't support argp. I propose to collect argp
> > sources following instructions in
> > http://savannah.gnu.org/cvs/?group=gnulib and try again. Any
> > better suggestions?
>
> Mhm, I wonder if we should remove the argp parsing again and replace it
> by more portable code. I am not sure about this yet.
I did get the ubi-tools to compile with argp code from gnulib.
There is probably an elegant solution using automake and friends
and the sources from gnulib. But I just hacked a Makefile and a config.h
together, and changed the names of two functions from getopt.h
to avoid clashes with my uclibc implementation.
In the ubi-tools directory there is a script "ubi_test.sh".
This script appeared to run successfully as well.
>
> >
> > 5. What is the way to get jffs2 running on an UBI partition? Should
> > I still be aiming to use gluebi to provide an MTD partition on
> > top of a UBI partition (whatever that means)? Cook book
> > instructions would be very helpful.
>
> Yes, gluebi is used to create the MTD which can be used by JFFS2. We had
> some iterations over the code, and finally came up with the code
> available in our ubi-2.6.git. The original from Joern was reworked by
> Artem, the currently available solution has only very few changes to
> JFFS2.
>
I think the following commands just worked:
mkdir /mnt/nvm
flash_eraseall /dev/mtd6
mount -t jffs2 /dev/mtdblock6 /mnt/nvm
I wonder whether this is the first attempt to run a kernel using
jffs2 and ubi and mtd and onenand and mips? First or not, it seems to work.
Thanks,
John Smith
next prev parent reply other threads:[~2006-11-06 20:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 8:22 UBI and OneNand John
2006-11-06 9:46 ` Frank Haverkamp
2006-11-06 13:18 ` Artem Bityutskiy
2006-11-06 20:16 ` John Smith [this message]
2006-11-06 20:54 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2006-11-07 2:35 UBI and OneNAND 박경민
2006-11-07 8:50 ` Frank Haverkamp
2006-11-07 10:20 ` John Smith
2006-11-07 11:39 ` Artem Bityutskiy
2006-11-07 11:47 ` Josh Boyer
2006-11-07 14:10 ` Artem Bityutskiy
2006-11-07 14:24 ` Josh Boyer
2006-11-07 14:39 ` Artem Bityutskiy
2006-11-07 9:16 ` Artem Bityutskiy
2006-11-08 16:03 ` Artem Bityutskiy
2006-11-07 12:52 Kyungmin Park
2006-11-08 16:09 ` Artem Bityutskiy
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=loom.20061106T205324-87@post.gmane.org \
--to=john.smith@arrows.demon.co.uk \
--cc=linux-mtd@lists.infradead.org \
/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