Collaboration diagram for PHAT File System:
![]() |
Modules | |
* Volume Support | |
Dealing with volumes. | |
Directory Support | |
Routines for reading and writing directories. | |
PHAT12 Support | |
PHAT12 specific routines. | |
PHAT16 Support | |
PHAT16 specific routines. | |
PHAT32 Support | |
PHAT32 specific routines. | |
PHAT Block I/O | |
Reading and writing data blocks. | |
PHAT Utilities | |
General utility routines used by the PHAT file system. | |
PHAT Debugging Support | |
Listing various PHAT structures. | |
Data Structures | |
struct | _PHATFILE |
PHAT file descriptor structure. More... | |
File attributes. | |
#define | PHAT_FATTR_RDONLY |
#define | PHAT_FATTR_HIDDEN |
#define | PHAT_FATTR_SYSTEM |
#define | PHAT_FATTR_VOLID |
#define | PHAT_FATTR_DIR |
#define | PHAT_FATTR_ARCHIV |
#define | PHAT_FATTR_LFN |
#define | PHAT_FATTR_FILEMASK |
Defines | |
#define | PHAT_MAX_PATHLEN |
Maximum length of a full path name. | |
#define | PHAT_MAX_NAMELEN |
Maximum length of a base file name. | |
#define | PHATEOC |
Marks end of cluster chain. | |
Typedefs | |
typedef _PHATFILE | PHATFILE |
PHAT file descriptor structure. | |
Functions | |
u_long | AllocFirstCluster (NUTFILE *nfp) |
Allocate the first cluster of a file. | |
Variables | |
NUTDEVICE | devPhat0 |
PHAT file system driver information structure. | |
NUTDEVICE | devPhat1 |
NUTDEVICE | devPhat0 |
PHAT file system driver information structure. | |
NUTDEVICE | devPhat1 |
|
File is not archived. This flag will be set when the file is created or modified. |
|
File contains a subdirectory. |
|
Only these flags are allowed for files and directories. |
|
Hidden file. |
|
Long filename entry. |
|
Read only file. |
|
System file. |
|
No file, but a volume label. |
|
Allocate the first cluster of a file.
|
|
PHAT file system driver information structure. A pointer to this structure must be passed to NutRegisterDevice() to bind this file system driver to the Nut/OS kernel. An application may then call /verbatim _open("MMC0:1/PHAT0", _O_RDWR | _O_BINARY); /endverbatim to mount partition 1 on the previously registered block device (devMmc0 in this example). |
|
PHAT file system driver information structure. A pointer to this structure must be passed to NutRegisterDevice() to bind this file system driver to the Nut/OS kernel. An application may then call /verbatim _open("MMC0:1/PHAT0", _O_RDWR | _O_BINARY); /endverbatim to mount partition 1 on the previously registered block device (devMmc0 in this example). |