From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] YAFFS2 support for buildroot
Date: Wed, 8 Dec 2010 20:34:29 +0100 [thread overview]
Message-ID: <20101208203429.5ae2cadc@surf> (raw)
In-Reply-To: <201012081744.10248.robert.szentmihalyi@helvetica-it.com>
Hi Robert,
On Wed, 8 Dec 2010 17:44:10 +0100
Robert Szentmihalyi <robert.szentmihalyi@helvetica-it.com> wrote:
> I am planning to add YAFFS2 support to buildroot.
> Is anybody else interested in that or working on it already?
I am not personaly, and I haven't heard of any effort in this direction.
> Would anybody care to give me a hint about what is the preferred way to add
> support for a new root filesystem to buildroot, so that a patch could
> eventually be accepted for inclusion?
It depends on what you want to be able to do:
1) Have Buildroot generate a YAFFS2 image for the filesystem
2) Have Buildroot patch the kernel built to support YAFFS2
1) is fairly easy, 2) is much more complicated because we don't have
(yet ?) a proper infrastructure to handle third-party kernel patches in
a generic way (even though it'd be nice to support things like Xenomai).
For 1), what you have to do is :
*) Create a package for the userspace yaffs tools. You can look in
package/cramfs/cramfs.mk for an example. You need to do this so
that Buildroot builds a host version of mkyaffs and installs it in
$(HOST_DIR)/usr/bin.
*) Create a new filesystem format in fs/yaffs/ by taking example on
other filesystems.
If you need any other detail or clarification about this, do not
hesitate to ask.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-08 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 16:44 [Buildroot] YAFFS2 support for buildroot Robert Szentmihalyi
2010-12-08 19:34 ` Thomas Petazzoni [this message]
2010-12-08 22:47 ` Robert Szentmihalyi
2010-12-09 19:33 ` Thomas Petazzoni
2010-12-10 23:28 ` Robert Szentmihalyi
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=20101208203429.5ae2cadc@surf \
--to=thomas.petazzoni@free-electrons.com \
--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