China
Africa
Explore chapters and articles related to this topic
Packet Forwarding in the Switch/Router
Published in James Aweya, Designing Switch/Routers, 2023
A device driver provides a software interface to a hardware device in a host system, enabling the host OS and other computer programs running on the system to access the device’s hardware functions without having to know precise details of that hardware device. Simply, a device driver allows the host’s OS to communicate with the hardware device. Device drivers are hardware-dependent and OS-specific. A device driver provides hardware abstraction as well as serves as a translating interface between the hardware device and the OS and programs that use it.
Computers
Published in John G. Webster, Halit Eren, Measurement, Instrumentation, and Sensors Handbook, 2017
A.M. MacLeod, P.F. Martin, W.A. Gillespie
Figure 89.7 shows a layer model of the software for a generalized instrumentation system. The application layer handles the data acquisition, analysis, and presentation. The instrument drivers provide a mechanism for communicating with the instruments in a standard way without requiring the user to know about the often cryptic data strings which need to be sent. For example, all digital multimeters will need the facility to choose a specific input voltage range. The range coding, resolution, etc. that have to be sent to the multimeter to achieve this will vary from instrument to instrument; however, the instrument driver allows the software writer programming in the application layer to call a procedure such as SetVoltageRange (Voltage Value) and this procedure call is the same for all multimeters. Although some manufacturers use the term slightly differently, the instrument driver is in effect the virtual instrument. Writing instrument drivers is a time-consuming but not too difficult task. Instrument drivers for proprietary instrumentation software design packages are readily available from instrument manufacturers. Device drivers integrate the controlling interface (e.g., IEEE-488, RS-232, or internal card) into the operating system of the computer. Writing a device driver requires a detailed knowledge of the device hardware and of the computer operating system. This is a difficult task and new interfaces should be purchased with a device driver appropriate for the operating system wherever possible.
The Contiki Operating System: A Tool for Design and Development of IoT—Case Study Analysis
Published in Ricardo Armentano, Robin Singh Bhadoria, Parag Chatterjee, Ganesh Chandra Deka, The Internet of Things, 2017
B. Venkatalakshmi, A. Pravin Renold, S. Vijayakumar
The device drivers act as an interface between the application and the hardware. Moreover, they are responsible for reading the packet and forwarding them to the higher layers. The communication stack processes the packets and forward them to the application for which the packet is intended for. In the case of any response to be done, the application program responds via the communication stack.
qLPV modeling and mixed-sensitivity
Published in International Journal of General Systems, 2023
Luiz Benício Degli Esposte Rosa, Matheus Senna de Oliveira, Renan Lima Pereira
The following equipment was used in order to test our proposals: a Maglev plant, an amplification module VoltPAQ-X1, a data acquisition module Q8-USB and a PC with Intel(R)i5 2.90GHz. Except for the latter, all of these devices were manufactured by Quanser. It can be seen that the experimental platform consists of four parts: the magnetic levitation device, driver circuit, acquisition module and a computer, as depicted in Figure 6. Herein, the effectiveness of the proposed design procedure is evaluated. As pointed out in Section 2, by setting the varying parameters to be , a reference LTI model at the operating point is recovered. Then, the control synthesis used in this work should give a comparable result to the discrete-time loop-shaping synthesis in Pereira, Kienitz, and Guaracy (2017). This synthesis was also applied to the Maglev system to provide a benchmark to assess the LPV results. Table 3 shows that the LPV approach was able to comply with the design requirements.
Thermodynamic-RAM technology stack
Published in International Journal of Parallel, Emergent and Distributed Systems, 2018
M. Alexander Nugent, Timothy W. Molter
Thermodynamic-RAM is designed to plug into existing computing architectures easily. The envisioned hardware format is congruent with standard RAM chips and RAM modules and would plug into a motherboard in a variety of different ways. In general there are two main categories of integration. First, kT-RAM can be tightly coupled with the CPU, on the CPU die itself or connected via the north bridge. In this case, the instruction set of the CPU would have to be modified to accommodate the new capabilities of kT-RAM. Secondly, kT-RAM is loosely coupled as a peripheral device either via the PCI bus, the LPC bus, or via cables or ports to the south bridge. In these cases, no modification to the CPU’s instruction set would be necessary, as the interfacing would be implemented over the generic plug-in points over the south bus. As in the case with other peripheral devices, a device driver would need to be developed. Additional integration configurations are also possible.
Design of a speech-enabled 3D marine compass simulation system
Published in Ships and Offshore Structures, 2018
Bin Fu, Hongxiang Ren, Jingjing Liu, Xiaoxi Zhang
Based on the principles described above, the Microsoft Speech SDK 5.1 was used to develop the speech interactive functions for the 3D marine compass simulation system. This SDK application layer includes both speech recognition and speech synthesis programs. Speech recognition is managed by the speech recognition engine, while the speech synthesis engine is responsible for text-to-speech synthesis. The SDK also provides a speech application program interface and a device driver interface to achieve its speech function. The system's structure is shown in Figure 12.