Structure and physical hardware initialization. Processing is application specific, it usually consists of data Therefore, all driver functions need to beĪlthough the actual driver initialization Typically the device driver also handles interrupts. Therefore the device driver internal function shall not Note that the device driver function executes with the IP Not need to handle multiple threads asynchronously calling the entryįunction. NetX serializes all access to the driver. NX_SUCCESS, the driver request was completed successfully. Status information is reported back to the caller
Member of the driver request data structure ( NX_IP_DRIVER)ĭefines the request. Because each networkĭriver has a single entry function, NetX makes all requests through The driver entry function to execute the command. NetX creates the driver request with a specific command and invokes The following format: VOID my_driver_entry(NX_IP_DRIVER *request) Nx_ip_driver_command field in the NX_IP_DRIVER request structure. NetX issues commands to the network driver by setting the Status operations, including initializing and enabling the networkĭevice. Initialization and for sending packets and for various control and NetX invokes the network driver entry function for driver Therefore released after the driver and calling function return. Structure is most often defined locally on the caller's stack and is Additional devices may be added to the IP instance via theĬommunication between NetX and the application's network driver isĪccomplished through the NX_IP_DRIVER request structure. Theĭriver's entry routine is defined during the nx_ip_create
The application-specific physical network driver's entry routine. This includes general TCP/IP protocol information as well as The NX_IP structure contains everything to manage a single IP
#Get command packet sender drivers
Information presented is designed to help developers writeĪpplication-specific network drivers for Azure RTOS NetX. This chapter contains a description of network drivers for NetX.
0 kommentar(er)
