a techfocus media publication :: January 24, 2006 :: volume II, no. 02
| a techfocus media publication :: January 24, 2006 :: volume II, no. 02 |
ANNOUNCEMENTS
 |
This Engineer Walks Into a Bar… Just out of college and needing some extra cash during the holidays, I worked briefly for a high-end haberdashery in Virginia. During orientation, we learned the tricks of the trade, including how to tie the perfect tie (I can still perform this impressive parlor trick…) and how to fold and stack dress shirts. But tucked neatly among all the expensive men’s clothing presentation skills was an actual life lesson. We were coached that we must not judge any customer by his appearance, and that some of the most important clients to visit the store would look quite the opposite. On further scrutiny, this amounts to no more than selfish altruism. The company’s policies were driven less by a social conscience than by an astute understanding of the habits of their target customer. Still, I managed to walk away from the experience with a keen sense that what you see is often not what you get. We’ve all had our moments. If you hear that your blind date has a great sense of humor, perhaps you develop a preconceived notion about said date’s outward appearance. What if you were told that your date was an engineer? The stereotype that brands engineers as nerds is clearly defined. It’s reached a level of stability and adoption that could qualify it for ratification by the IEEE. It could be known as the “Nerd Classification Code,” or NCC-1701. Over the years, creative jokesters have found ever more amusing ways to pin on the Nerd Badge. “Have you heard the one about the engineering superhero? He’s known as The Pocket Protector, and he keeps us safe from all things algorithmic, as long as it doesn’t involve fighting, athletics, or speaking to a girl.”
Getting Performance with Memory Protection in Real-time Windows Systems When designing Windows real-time embedded systems, maintaining deterministic performance is as critical as ensuring that the system itself runs error-free. Applications can be developed and deployed in Ring 3 or Ring 0. In fact, they can be developed in one mode yet deployed in the other. Development in the application mode (Ring 3) provides memory protection and application stability. However, to deploy with high system predictability and hard real-time determinism, the application must reside in the kernel mode (Ring 0). The following note outlines the proper technique for integrating the benefits of Ring 3 and Ring 0. Development using Ring 3 provides the benefit of memory protection from the application, which aids in debugging the application by letting the hardware catch common programming errors. This enables rapid development, because in many cases, only the application will crash upon hitting a bug. With the operating system running, the application can be restarted and the debugging can be continued – resulting in a quick test, debug and fix cycle. [more] |
||||||||
| LATEST NEWS | |||||||||
January 24, 2006 Cascada Mobile Announces Peer-to-Peer Distribution Solution for J2ME Applications January 23, 2006 CoWare Launches New Modeling Solution for Platform-Driven ESL Design |
January 23, 2006 (continuted) Atmel Expands LIN Portfolio With New LIN2.0 System Basis Chip Featuring Silent Mode Operation January 19, 2006 PolarPro -- One of EDN's Hot 100 Products for 2005 January 18, 2006 MIPS Technologies Customers and Licensees Spearhead Innovation at CES 2006 Juniper Networks Selects Denali Verification IP for Design and Verification of Its Products ARM Powered(R) TTPCom Modem Delivers Market-Leading Size and Performance Advantages |
||||||||
All material copyright © 2003-2006 techfocus media, inc. All rights reserved. |
