linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: LEROY Christophe <christophe.leroy@c-s.fr>
Cc: linuxppc-embedded@lists.linuxppc.org, herve.poli@c-s.fr
Subject: Re: What does Montavista Linux gives you in addition to standard Linux ?
Date: Tue, 23 Apr 2002 13:23:09 -0600	[thread overview]
Message-ID: <20020423132309.J3939@host110.fsmlabs.com> (raw)
In-Reply-To: <7754BDCF5E4.AAA217C@hermes17.si.c-s.fr>; from christophe.leroy@c-s.fr on Tue, Apr 23, 2002 at 09:15:08PM +0200


There are a number of advantages to using Linux in embedded applications -
regardless of what MontaVista has or has not done.  They are not embedded
Linux, they just use it.  Don't judge all of embedded Linux by one company.

Do you mean Linux for realtime applications?  There are many low-latency
style projects to improve standard linux real-time performance along with
FSMLabs RTLinux hard-realtime work.  There's a lot to choose from no matter
what your needs are.

} I thought that Montavista had really improved the realtime of Linux,
} but i've been told that Montavista has only improved realtime for threads
} and for SMP.
} It means it is only interesting if you have only one process per CPU, with
} a lot of threads inside it.
}
} Is that right ?
}
} If it is right, I can't see any interest of using Linux for embedded
} systems.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-04-23 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 19:15 What does Montavista Linux gives you in addition to standard Linux ? LEROY Christophe
2002-04-23 19:23 ` Cort Dougan [this message]
2002-04-23 20:22 ` Kurt Wall
2002-04-23 21:28 ` Todd Poynor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020423132309.J3939@host110.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=herve.poli@c-s.fr \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).