From: Juraj Vijtiuk <juraj.vijtiuk@sartura.hr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Adding F2FS support
Date: Mon, 25 Mar 2019 13:57:43 +0100 [thread overview]
Message-ID: <20190325125743.kqoj557nxpbp3fea@debian> (raw)
Hello,
I've started to work on adding F2FS support to U-boot.
After a quick search of the U-Boot mailing archives, I see that support for
multiple file systems, like ZFS was already added by reusing existing GRUB code.
F2FS was added to GRUB last year, in this commit:
http://git.savannah.gnu.org/cgit/grub.git/commit/?id=71f9e4ac44142af52c3fc1860436cf9e432bf764
so I'd port that to U-Boot.
F2FS has also been added to the Linux kernel in version 3.8 and is licensed under GNU GPLv2,
so there shouldn't be any issues with that as far as I know.
I plan to use the ZFS patch as a starting point, and reference other fs patches
and recent ZFS updates when needed.
Are there any potential issues or anything else I should know before I start
working on the patch?
Regards,
Juraj Vijtiuk
next reply other threads:[~2019-03-25 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:57 Juraj Vijtiuk [this message]
2019-03-25 14:13 ` [U-Boot] Adding F2FS support Lukasz Majewski
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=20190325125743.kqoj557nxpbp3fea@debian \
--to=juraj.vijtiuk@sartura.hr \
--cc=u-boot@lists.denx.de \
/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