Linux - Embedded & Single-board computerThis forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My question is general about real time embedded coding .
When response time is critical and should be short like in case of
an industrial machine that needs to respond fast .
In such case is it better to control that machine with a bare board
programmed with C code or is it better to use a LINUX based board ?
Depends on the exact application. In many industrial settings, running bare-bones may be better. Additionally, if it's a life-critical safety application, Linux is pretty much out of the question. However, Linux does provide a lot in terms of drivers and software libraries that may be useful for an embedded application.
The term HARD REAl TIME means fast response time
vs SOFT REAL TILE means long response tle LIKE an ATM machine .
The definitions I've heard are a bit different:
Hard real-time: The system has defined deadlines; missing a single deadline is considered complete system failure.
Soft real-time: Missing the occasional deadline is acceptable.
I think the OP is trying to distinguish between Linux as a realtime OS and bare-metal C programming. Neither of these are 'hard realtime', although you may achieve hard realtime performance with bare-metal C coding.
Strictly speaking, hard realtime is about guaranteed response time, and does not mean fast/high-speed. Normally, when guaranteed response times are required (not 'should be short'), it also implies some elevated performance level, and that is probably what causes people to misunderstand the meaning. Determinism is the name of the game for real-time performance. Only if you can guarantee response times can you call a system a realtime system. Bare Linux can not do this. Very often, it is true that 'real fast is as good as real time', but there is still a distinction.
You seem to be generally splattering the forum with related content. I suggest that you try to stay with one thread instead of open a new thread that is related to the same topic you have been posting queries about.
That way we can address the topic in it's entirety. Questions are fine but when you segment, it can not be addressed fully as to the related content.
Please look at the following;
FYI: I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem or query.
FYI: Netiquette is a set of social conventions that facilitate interaction over networks, ranging from Usenet and mailing lists to blogs and forums.