September 2011
Intermediate to advanced
744 pages
19h 4m
English
Content preview from Professional Windows® Embedded Compact 7Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
STREAM DRIVERS
A majority of Windows Embedded Compact 7 drivers are implemented as Stream Drivers. Any device that can be modeled as producing and consuming data in a stream can have a device driver implemented as a Stream Driver. Drivers as diverse as serial, battery, backlight, NLED, accelerometer, and I2C are all implemented as Stream Drivers. For layered Stream Drivers, the MDD, the part that interfaces to the OS, implements the stream interface. Even the RELFSD driver, which enables the mounting of the Release Directory File System on a development system, has a pseudo Stream Driver interface so that Device Manager can load it.
Why Stream Drivers?
Stream Drivers, unlike native drivers, all interlock with the operating system in a standard manner but have the flexibility via IOCTLs to implement specific functionality. This standardization results in a generic functional interface between the drivers and their operating system manager, Device Manager. Driver source code consists of a set of functions that all Stream Drivers implement in part or in full. The same API is used to load, unload, and perform data streaming with the driver. Yet IOCLs provide a “backdoor” interface for implementing driver-specific functionality and for low-level operating system functions such as power management.
Stream Driver Architecture
Figure 32-1 shows the Stream Driver architecture. An application makes calls to the Device Manager to load a Stream Driver. The system or an application can similarly ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.