Home ›

Embedded Linux Supplement

Aug 31, 2000  By Phil Hughes
 in
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 size changes 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 you can add microwave, phone system, voice mail system, 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 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 cost of an 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!

Sincerely,

Phil HughesPublisher

Visit Embedded Linux Journal

email: ljeditors@ssc.com

______________________

Phil Hughes

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions