Filesystem in RTEMS

[xuelin.tian at qkmtech.com]

I followed the example (testsuites/fstests/jffs2_support/fs_support.c), and some error came up, like 
"undefined reference to rtems_jffs2_initialize",
"undefined reference to rtems_jffs2_compressor_zlib_compress", and 
"undefined reference to rtems_jffs2_compressor_zlib_decompress"
I have no clue here. Do I have to give my own implementation of these functions here? I can exploit the default functions for jffs2 entry table and compress, I think. 

And I have a little confused about the model of device driver in rtems, since I get stuck for a few days.
First, a deivce descriptor (rtems_fdisk_device_desc) should be given, including some handlers defined in rtems_fdisk_driver_handlers,  and device configuration (rtems_flashdisk_config). 
Then, I need to register (or initialize) my flash device into rtems dynamically or statically, with my own initialize, open, close functions.
Last, the JFFS2 should be set up based on the registered device driver. The block size need to be equal to the page size of flash, and the read, write, erase operations should invoke the corresponding functions defined in rtems_fdisk_driver_handlers.

Am I correct in this whoe process?





Best wishes,
xuelin.tian at qkmtech.com
 
From: Sebastian Huber
Date: 2017-10-19 19:56
To: xuelin.tian at qkmtech.com; users at rtems.org
Subject: Re: Filesystem in RTEMS
On 19/10/17 13:49, xuelin.tian at qkmtech.com wrote:
> Does RTEMS have the FTL(Flash Translation Layer) as Linux, that can 
> map flash device into block device?
 
No.
 
> How can I define the blocks used in JFFS2, according to NOR flash?
 
See testsuites/fstests/jffs2_support/fs_support.c for an example. We 
have no direct support for the flash block device driver.
 
-- 
Sebastian Huber, embedded brains GmbH
 
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.
 
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20171021/c52a02b2/attachment-0001.html>