Changes between Version 11 and Version 12 of TBR/UserManual/Using_the_RTEMS_DOS_File_System


Ignore:
Timestamp:
Oct 22, 2008, 5:17:48 AM (12 years ago)
Author:
ChrisJohns
Comment:

Updates added.

Legend:

Unmodified
Added
Removed
Modified
  • TBR/UserManual/Using_the_RTEMS_DOS_File_System

    v11 v12  
    207207 } rtems_nvdisk_device_desc;
    208208
    209 The {{{flags</code> field provides a private set of flags a specific low level device handlers for a device may need. The {{{base</base> is the base address of the device. Its definition depends on the low level device handlers for a specific device. The {{{size</code> field defines the number of bytes of storage the device provides in bytes. This is the raw number of bytes available to the driver. The {{{nv_ops</code> is a set of handlers for the specific device.
     209The fields are:
     210
     211# The {{{flags</code> field provides a private set of flags a specific low level device handlers for a device may need.
     212# The {{{base</code> is the base address of the device. Its definition depends on the low level device handlers for a specific device.
     213# The {{{size</code> field defines the number of bytes of storage the device provides in bytes. This is the raw number of bytes available to the driver.
     214# The {{{nv_ops</code> is a set of handlers for the specific device.
    210215
    211216The NV Disk device requires a set of handlers for each type of device. The handles can manage more than one device in a disk or disks. The handlers are:
    212217
    213   {{{int (*read) (uint32_t device, uint32_t flags, uint32_t base, uint32_t offset,
    214                      void* buffer, uint32_t size);</code>
     218  {{{int (*<i><b>read</b></i>) (uint32_t device, uint32_t flags, uint32_t base, uint32_t offset,
     219 ::                  void* buffer, uint32_t size);</code>
    215220 : Read a block of data from the {{{offset</code> in the {{{device</code> with the {{{base</code> address to the provided {{{buffer</code>.
    216221
    217   {{{int (*write) (uint32_t device, uint32_t flags, uint32_t base, uint32_t offset,
    218                       const void* buffer, uint32_t size);</code>
     222  {{{int (*<i><b>write</b></i>) (uint32_t device, uint32_t flags, uint32_t base, uint32_t offset,
     223 ::                   const void* buffer, uint32_t size);</code>
    219224 : Write a block of data to the {{{offset</code> in the {{{device</code> with the {{{base</code> address from the provided {{{buffer</code>.
    220225
    221   {{{int (*verify) (uint32_t device, uint32_t flags, uint32_t base, uint32_t offset,
    222                        const void* buffer, uint32_t size);</code>
     226  {{{int (*<i><b>verify</b></i>) (uint32_t device, uint32_t flags, uint32_t base, uint32_t offset,
     227 ::                    const void* buffer, uint32_t size);</code>
    223228 : Verify a block of data provided in {{{buffer</code> against to the data at the {{{offset</code> in the {{{device</code> with this {{{base</code> address.
    224229
    225230The <tt>nvdisk-sram.h</tt> provides a set of handlers suitable for static RAM.
     231
     232To configure a NV disk add this following to a source file in your application. The configuration items are:
     233
     234# Block size. This is normally 512 for the MSDOS file-system.
     235# Number of device descriptions.
     236# Pointer to the device descriptions.
     237#