Lines Matching defs:and
3 The layout of the FAT16 and FAT32 filesystems can be seen in Figures
4 \ref{fig:fat16_layout} and \ref{fig:fat32_layout} respectively. The \ac{fat}
6 of the next cell, and special values indicate unused, bad and list-terminating
10 $fat\_start + i \cdot entry\_size$ and the cluster entry is $clusters\_start +
27 FAT16 (and FAT12) have the particularity that the root directory is not like
30 the root directory is fixed when formatting. FAT32 removes this limitation, and
34 \section{Implementation and Limitations}
36 We have implemented read-only support for FAT16 and FAT32. However, because the
37 example \lstinline+ata_rw28+ interface only has the 28-bit {\tt READ DMA} and
46 and does not support opening files with non-\acs{ascii} filenames.
63 The FAT code uses a cache layer as a global block and cluster store,
64 simplifying the code and improving performance. The cache is implemented as a
66 uses doubly linked lists to handle collisions, the free list, and a list of
73 seen as an \acs{lru} queue. Thus when \lstinline+fs_cache_put+ is called and
75 unused list, free its data, and use the entry for the new cache item.
79 \item \lstinline+fs_cache_init+ and \lstinline+fs_cache_free+, for cache
80 setup and teardown. The initialization method takes the maximum capacity
81 of the backing array and the hashmap size. Both values must be powers of
96 device, and the optional {\tt startblock} specifies the offset the first sector
102 filesystem and the whole disk. An alternative that would avoid code duplication