Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Configure each of the device’s interrupts on either an external or CPU’s integrated interrupt controller. However, vectored interrupt controllers may not require the explicit configuration and enabling of higher-level interrupt controller sources. In this case, the application developer may need to configure the system’s interrupt vector table with the name of the ISR handler functions declared in net_bsp.c.

    NetDev_WiFi_CfgIntCtrl() should only enable each devices’ interrupt sources but not the local device-level interrupts themselves, which are enabled by the device driver only after the device has been fully configured and started.

    Since each network device requires a unique NetDev_WiFi_CfgIntCtrl(), it is recommended that each device’s NetDev_WiFi_CfgIntCtrl() function be named using the following convention:

    NetDev_WiFi_[Device]CfgIntCtrl[Number]()

    [Device]Network device name or type, e.g. RS9110 (optional if the development board does not support multiple devices)
    [Number]Network device number for each specific instance of device (optional if the development board does not support multiple instances of the specific device)

    For example, the NetDev_CfgIntCtrl() function for the #2 RS9110 wireless device on an Atmel AT91SAM9263-EK should be named NetDev_WiFi_RS9110_CfgIntCtrl2(), or NetDev_WiFi_RS9110_CfgIntCtrl_2() with additional underscore optional.

See also section Network Board Support Package.

...