From: Sascha Hauer <s.hauer@pengutronix.de>
To: Renaud Barbier <renaud.barbier@ge.com>
Cc: barebox@lists.infradead.org
Subject: Re: ubifs
Date: Thu, 29 Sep 2011 12:18:10 +0200 [thread overview]
Message-ID: <20110929101810.GE31404@pengutronix.de> (raw)
In-Reply-To: <4E833CE3.7070701@ge.com>
On Wed, Sep 28, 2011 at 04:27:31PM +0100, Renaud Barbier wrote:
> I see that there is no ubifs support in barebox.
>
> Is there any plan to support ubifs in the near future?
No, not that I heard of.
>
> Else how much effort do you think it will take to port it
>
> I never ported a fs so if you have any advices, I will
> be glad to read them.
Probably the U-Boot ubifs code is a useful template for
porting ubifs to barebox. It shouldn't be too hard to get
something working by looking at the current filesystems
in barebox.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-09-29 10:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 15:27 ubifs Renaud Barbier
2011-09-29 10:18 ` Sascha Hauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-03 12:42 ubifs Erwin Rol
2018-12-03 12:58 ` ubifs Sascha Hauer
2018-12-03 13:06 ` ubifs Erwin Rol
2018-12-03 13:26 ` ubifs Sascha Hauer
2018-12-03 13:35 ` ubifs Erwin Rol
2013-06-18 15:47 ubifs Aidan Totterdell
2008-12-10 13:50 Ubifs Жека
2008-12-10 11:44 Ubifs Жека
2008-12-10 11:55 ` Ubifs Artem Bityutskiy
2008-12-10 12:51 ` Ubifs Artem Bityutskiy
2008-12-10 9:02 Ubifs Жека
2008-12-10 11:04 ` Ubifs 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=20110929101810.GE31404@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=renaud.barbier@ge.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.