| Summary: | Support F2FS | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | jonathan.yong |
| Component: | core | Assignee: | Naveen Saini <naveen.kumar.saini> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | bluelightning, meta.mr.watcher, meta.watcher, naveen.kumar.saini, robin.l.jordan, ross.burton, sgw |
| Version: | 2.5 | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
jonathan.yong
2017-10-11 02:18:37 UTC
This has both a Kernel component and User-space, F2FS is already in meta-filesystems, the question is does it need to move to oe-core? Currently, when IMAGE_FSTYPES has f2fs, bitbake fails with: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'f2fs'. It looks to me like this did get added at least to IMAGE_FSTYPES: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=c44980abaf4ef3756597c0c5b51678253a56a5f5 (Note that you still need the meta-filesystems layer in your configuration in order to provide the required f2fs-tools recipe.) F2FS support in IMAGE_FSTYPES is available and build is successful and produces *.rootfs.f2fs image. As per comments, closing. |