Changeset 271d981 in rtems


Ignore:
Timestamp:
May 21, 2003, 11:29:58 PM (17 years ago)
Author:
Ralf Corsepius <ralf.corsepius@…>
Children:
3116c5a
Parents:
f902e822
Message:

2003-05-21 Ralf corsepius <corsepiu@…>

  • adaintr.t, ata.t, ide-ctrl.t, target.t: Various typo-fixes, Update to reflect introduction of the cpukit.
Location:
doc/bsp_howto
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • doc/bsp_howto/ChangeLog

    rf902e822 r271d981  
     12003-05-21      Ralf corsepius <corsepiu@faw.uni-ulm.de>
     2
     3        * adaintr.t, ata.t, ide-ctrl.t, target.t: Various typo-fixes, Update
     4        to reflect introduction of the cpukit.
     5
    162003-01-28      Joel Sherrill <joel@OARcorp.com>
    27
  • doc/bsp_howto/adaintr.t

    rf902e822 r271d981  
    3333
    3434To enable gnat interrupt and error exception support for a particular
    35 bsp, the following has to be done:
     35BSP, the following has to be done:
    3636
    3737@enumerate
     
    4343handled by gnat (including spurious).
    4444
    45 @item At startup, gnat calls @code{__gnat_install_handler()}. The bsp
     45@item At startup, gnat calls @code{__gnat_install_handler()}. The BSP
    4646must provide this function which installs the interrupt/trap handlers.
    4747
    4848@end enumerate
    4949
    50 Which cpu-interrupt will generate which signal is implementation
     50Which CPU-interrupt will generate which signal is implementation
    5151defined. There are 32 POSIX signals (1 - 32), and all except the
    5252three error signals (SIGILL, SIGFPE and SIGSEGV) can be used. I
     
    6464Ada examples package to show how interrupts can be handled
    6565in Ada95. Note that generation of the test interrupt
    66 (@code{irqforce.c}) is bsp specific and must be edited.
     66(@code{irqforce.c}) is BSP specific and must be edited.
    6767
    6868NOTE: The @code{irq_test} example was written for the SPARC/ERC32
  • doc/bsp_howto/ata.t

    rf902e822 r271d981  
    1616
    1717ATA driver provides generic interface to an ATA device. ATA driver is
    18 hardware independant implementation of ATA standart defined in working draft
    19 "AT Attachment Interface with Extentions (ATA-2)" X3T10/0948D revision 4c,
     18hardware independent implementation of ATA standard defined in working draft
     19"AT Attachment Interface with Extensions (ATA-2)" X3T10/0948D revision 4c,
    2020March 18, 1996. ATA Driver based on IDE Controller Driver and may be used for
    2121computer systems with single IDE controller and with multiple as well. Although
     
    3030
    3131The reference implementation for ATA driver can be found in
    32 @code{c/src/exec/libblock/src/ata.c}. 
     32@code{cpukit/libblock/src/ata.c}. 
    3333
    3434@section Initialization
     
    5353   for each IDE controller successfully initialized by the IDE Controller
    5454       driver
    55      if the controller is interuupt driven
     55     if the controller is interrupt driven
    5656       set up interrupt handler
    5757
     
    6868
    6969Special processing of ATA commands is required because of absence of
    70 multitasking enviroment during the driver initialization.
     70multitasking environment during the driver initialization.
    7171
    7272Detected ATA devices are registered in the system as physical block devices
     
    119119ATA driver supports separate ATA requests queues for each IDE
    120120controller (one queue per controller). The following structure contains
    121 inforamtion about controller's queue and devices attached to the controller:
     121information about controller's queue and devices attached to the controller:
    122122
    123123@example
     
    129129typedef struct ata_ide_ctrl_s @{
    130130    rtems_boolean present;   /* controller state */
    131     ata_dev_t     device[2]; /* ata diveces description */
     131    ata_dev_t     device[2]; /* ata devices description */
    132132    Chain_Control reqs;      /* requests chain */
    133133@} ata_ide_ctrl_t;
     
    138138number.
    139139
    140 The following struture allows to map an ATA device to the pair (IDE
     140The following structure allows to map an ATA device to the pair (IDE
    141141controller minor number device is attached to, device number
    142142on the controller):
     
    177177implementation supports only two ioctls: BLKIO_REQUEST and
    178178ATAIO_SET_MULTIPLE_MODE. Each ATA driver ioctl() call generates an
    179 ATA request which is appended to the apropriate controller queue depending
     179ATA request which is appended to the appropriate controller queue depending
    180180on ATA device the request belongs to. If appended request is single request in
    181181the controller's queue then ATA driver event is generated.
     
    184184driver. In current driver version queue of ATA driver events implemented
    185185as RTEMS message queue. Each message contains event type, IDE controller
    186 minor number on which event happaned and error if an error occured. Events
     186minor number on which event happened and error if an error occurred. Events
    187187may be generated either by ATA driver ioctl call or by ATA driver task itself.
    188188Each time ATA driver task receives an event it gets controller minor number
  • doc/bsp_howto/ide-ctrl.t

    rf902e822 r271d981  
    2626is based on the libchip concept and allows to work with any of the IDE
    2727Controller chips simply by appropriate configuration of BSP. Drivers for a
    28 paticular IDE Controller chips locate in the following directories: drivers
     28particular IDE Controller chips locate in the following directories: drivers
    2929for well-known IDE Controller chips locate into
    3030@code{$RTEMS_SRC_ROOT/c/src/libchip/ide}, drivers for IDE Controller chips
     
    3939@section Initialization
    4040
    41 IDE Controller chips used by a BSP are statically confiured into
     41IDE Controller chips used by a BSP are statically configured into
    4242@code{IDE_Controller_Table}. The @code{ide_controller_initialize} routine is
    4343responsible for initialization of all configured IDE controller chips.
     
    5757@{
    5858   for each IDE Controller chip configured in IDE_Controller_Table
    59      if (BSP dependant probe(if exists) AND device probe for this IDE chip
     59     if (BSP dependent probe(if exists) AND device probe for this IDE chip
    6060        indicates it is present)
    6161       perform initialization of the particular chip
     
    7474@group
    7575void ide_controller_read_register(rtems_device_minor_number minor,
    76                                   unsigned32 reg, unsiged32 *value)
     76                                  unsigned32 reg, unsigned32 *value)
    7777@{
    7878  get IDE Controller chip configuration information from
     
    9393@group
    9494void ide_controller_write_register(rtems_device_minor_number minor,
    95                                    unsigned32 reg, unsiged32 value)
     95                                   unsigned32 reg, unsigned32 value)
    9696@{
    9797  get IDE Controller chip configuration information from
  • doc/bsp_howto/target.t

    rf902e822 r271d981  
    2727routines for the executive proper such as the context switch and
    2828the interrupt subroutine implementations.  Sources for the supported
    29 processor families can be found in @code{c/src/exec/score/cpu}.
     29processor families can be found in @code{cpukit/score/cpu}.
    3030A good starting point for a new family of processors is the
    3131@code{no_cpu} directory, which holds both prototypes and
     
    3535dependent on a particular CPU model.  For example, the MC68000 and MC68020
    3636processors are both members of the m68k CPU family but there are significant
    37 differents between these CPU models which RTEMS must take into account.
     37differences between these CPU models which RTEMS must take into account.
    3838
    3939@section Board Dependent
     
    116116
    117117@example
    118 c/src/exec/score/cpu/@i{CPU}
     118cpukit/score/cpu/@i{CPU}
    119119@end example
    120120
Note: See TracChangeset for help on using the changeset viewer.