Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Learning Embedded Linux using the Yocto Project

You're reading from   Learning Embedded Linux using the Yocto Project Develop powerful embedded Linux systems with the Yocto Project components

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781784397395
Length 334 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Alexandru Vaduva Alexandru Vaduva
Author Profile Icon Alexandru Vaduva
Alexandru Vaduva
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Learning Embedded Linux Using the Yocto Project
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
1. Introduction 2. Cross-compiling FREE CHAPTER 3. Bootloaders 4. Linux Kernel 5. The Linux Root Filesystem 6. Components of the Yocto Project 7. ADT Eclipse Plug-ins 8. Hob, Toaster, and Autobuilder 9. Wic and Other Tools 10. Real-time 11. Security 12. Virtualization 13. CGL and LSB Index

Understanding GPOS and RTOS


When Linux is mentioned, usually General Purpose Operating System (GPOS) is related to it, but over time, the need to have the same benefits as Real-Time Operating System (RTOS) for Linux has become more stringent. The challenge for any real-time system is to meet the given timing constrains in spite of the number and type of random asynchronous events. This is no simple task and an extensive number of papers and researches were done on theory of the real-time systems. Another challenge for a real-time system would be to have an upper limit on latency, called a scheduling deadline. Depending on how systems meet this challenge, they can be split into hard, firm, and soft:

  • Hard real-time system: This represents system for which a deadline miss will result in a complete system failure.

  • Firm real-time system: This represents systems for which a deadline miss is acceptable but the system quality can be degraded. Also, after the deadline is missed, the result that is...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at £13.99/month. Cancel anytime
Visually different images