NetBurner Community Forum

Code: Select all

/*******************************************************************************
 * MOD54417 Network Operation Overview                                         *
 * ------------------------------------                                        *
 * The MOD54417's software drivers are designed to be fully transparent and    *
 * perform all necessary configurations using the same function calls as the   *
 * MOD54415. So, what are the relevant function calls and what do they do      *
 * differently between the MOD54415 and the MOD54417?                          *
 *                                                                             *
 * Hardware Initialization                                                     *
 * ------------------------                                                    *
 * The hardware initialization for the network stack ocurrs in                 *
 * InitializeStack(). At the bottom, this function breaks out of the main      *
 * system library when it calls AddEthernetInterface(). Inside this call, there*
 * is a check that determines if the software is running on a MOD54415 or a    *
 * MOD54417. If it is running on a MOD54417 it then checks to see if it should *
 * be running in switched mode or independent mode. By the time the function   *
 * returns, the network hardware is configured accordingly and the interface(s)*
 * are added to the stack (if the device is in switched mode, only one         *
 * interface is created, due to the nature of the switch). Add2ndEthernet()    *
 * should never be called in normal application development. If the module     *
 * should switch between switched and independent modes, the config record     *
 * must be updated and then the module be reset.                               *
 *                                                                             *
 * Network Configurations                                                      *
 * -----------------------                                                     *
 * When the ethernet interfaces are operating in independent mode, the second  *
 * ethernet interface will get its configuration from ConfigRecord number      *
 * CONFIG_IF_ID_ETHERNET2. It will appear under IPSetup. In most ways, the     *
 * second interface will behave as the first, with a few minor exceptions.     *
 *                                                                             *
 * 1. The link status functions will now operate on the driver objects.        *
 *    Example:  EtherLink() becomes enet0.EtherLink() or enet1.EtherLink()     *
 * 2. All the calls with Ethernet* (EthernetIP, EthernetIpMask, EthernetIpGate,*
 *    EthernetDNS) will need to need to be changed to work with the            *
 *    NetInterface functions for querying the different addresses, or obtaining*
 *    the InterfaceBlock for the correct interface. These can be obtained by   *
 *    the oppropriate call as follows:                                         *
 *       InterfaceBlock *pifb = GetInterFaceBlock( enet0.myInterfaceNumber );  *
 *    Once you have the block, the you can then set the individual addresses.  *
 *                                                                             *
 * GetDHCPAddressIfNecessary                                                   *
 * --------------------------                                                  *
 * GetDHCPAddressIfNecessary has been modified in the default case. The default*
 * argument is -1. When this value is passed, GetDHCPAddressIfNecessary will   *
 * start DHCP negotiations on all network interfaces that do not already have  *
 * either, a valid IP address, a DHCP object associated, or an AutoIP object   *
 * associated.                                                                 *
 *******************************************************************************/