Home ›

Resources for Mobile Phones: the Embedded Linux Challenge

Issue 148

From Issue #148
August 2006

Jul 01, 2006  By Bill Weinberg
 in

Open Source Real-Time Linux Project: source.mvista.com/linux_2_6_RT

Preemption Patches Maintained by Ingo Molnar: people.redhad.com/~mingo

LinuxTiny: www.selenic.com/linux-tiny

ARM Thumb: www.arm.com/products/CPUs/archi-thumb.html

MIPS16: www.linux-mips.org/wiki/MIPS16

User Space XIP with CramFS: tree.celinuxforum.org/CelfPubWiki/ApplicationXIP

Raw NOR Flash Kernel XIP: tree.celinuxforum.org/CelfPubWiki/KernelXIP

uClibc: www.uclinux.org

BusyBox: www.busybox.net

TinyLogin: tinylogin.busybox.net

CramFS and YAFFS: www.aleph1.co.uk/yaffs

Harald Welte's Open-E2X: www.open-ezx.org

Open Phone Stack for Motorola Mobile Phones Wiki: wiki.openezx.org

MLI: www.lsdl.org/lab_activities/mobile_linux/mli

______________________

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