In 1968, when I got my first job in computing, we didn't call that room full of computers with a disk drive the size of a Volkswagen an embedded system. But it was. I worked for Collins Radio and what we were working on was a message-switching system. Today, however, that same computing power could easily fit in a 1U rackmount box or be implemented on a Netwinder or Cobalt Qube.
The point is that calling a system embedded doesn't have anything to do with its size, but whether it performs some dedicated task. Besides the changes in size over the years, there have been cost changes. While my microwave doesn't have an embedded processor in it, most, do as do most traffic light controllers and virtually every printer in the world.
Doing an inventory of what is around me at home, here is my list of things that I know have embedded processors: Palm organizer, cell phone, FAX/answering machine, scanner, digital camera, video camera, dish TV receiver, VCR, stereo, laser printer, DSL modem car. At work I can add microwave, label maker, phone system, voice-mail system and conference phone.
This doesn't count other items that most likely have them as well: disk drives, tape drives, monitors, TV and clock radio. This is a big change from 1968. With $50 (US) products out there in the embedded market, there is a lot more to consider than just making a product that works.
We want to help you take the next step. Hardware costs have fallen dramatically, making it possible to put computers into relatively inexpensive products. Efficient code can reduce RAM and ROM requirements. But there are additional costs besides hardware. The OS for your product, development time, development tools and licensing all cost money. Shipping a product with bugs can cost you money and reputation.
With that I'd like to introduce a Linux Journal supplemental issue which will hit the streets October 10, 2000: Embedded Linux Journal. In this special issue you can look forward to conversations about:
industry news—emphasizing open-source software solutions
reviews of products to reduce development time and improve testing
case studies that will save you time
design solutions that show you why embedded Linux is the cost-effective answer
hardware vs. software considerations
Current Linux Journal subscribers who live within North America will receive this special supplement at no additional charge. This issue will also be heavily distributed at upcoming trade shows, other industry events, and to targeted mailing lists.
We're certain you'll enjoy this upcoming Embedded Linux Journal supplement. We look forward to your feedback!
Phil Hughes Publisher
- Android Browser Security--What You Haven't Been Told
- Epiq Solutions' Sidekiq M.2
- Readers' Choice Awards 2013
- The Many Paths to a Solution
- Nativ Disc
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Synopsys' Coverity
- Writing a Simple USB Driver
- Downloading an Entire Web Site with wget
- Securing the Programmer
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide