From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] UBIFS confusion
Date: Sat, 4 Apr 2009 23:53:47 +1100 [thread overview]
Message-ID: <20090404125347.GA11896@cloud.net.au> (raw)
In-Reply-To: <AC4CD65049C54EDC9F34A00769C5A81F@apexjs>
On Sat, Apr 04, 2009 at 11:03:26AM +0200, Sagaert Johan wrote:
> When i need UBIFS do i just enable UBI and UBIFS with the default kernel
> (currently using 2.6.28.8.)?
>
> On http://git.infradead.org/ i saw <http://git.infradead.org/ubifs-2.6.git>
> ubifs-2.6.git , <http://git.infradead.org/ubi-2.6.git> ubi-2.6.git , these
> seem to be kernel trees with modifications in the ubisfs fs.
>
> i am currently using MTD userspace tools from the git repository.(mkfs.ubifs
> ,ubinize) to create ubifs images.
>
> Do i need the to use the kernel tree from
> <http://git.infradead.org/ubifs-2.6.git> ubifs-2.6.git or
> <http://git.infradead.org/ubi-2.6.git> ubi-2.6.git or can i just use the
> default buildroot stuff ?
Default buildroot kernel is fine (>= 2.6.25 at least, maybe later).
However the current checked-in ubifs root uses an old version of
mkfs.ubifs which generates an old format. I don't think it will work
with any released kernel. You need the patches submitted by Michael Roth
this week. We should get them committed to buildroot very soon.
The ubi-2.6.git and ubifs-2.6.git trees are either old work or future
development work, but the stuff in the released kernel is stable.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-04-04 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 9:03 [Buildroot] UBIFS confusion Sagaert Johan
2009-04-04 12:53 ` Hamish Moffatt [this message]
2009-04-06 7:40 ` [Buildroot] arm platform halt during boot. Help! Daniel.Li
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=20090404125347.GA11896@cloud.net.au \
--to=hamish@cloud.net.au \
--cc=buildroot@busybox.net \
/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