On Sun, Jun 17, 2007 at 10:38:54PM -0700, Ted Mittelstaedt wrote:
There's another issue and that is POST on standard PC hardware. POST
takes too long. For example the auto industry has agreed on a standard
time that a car engine computer must be fully operational, it is very
short, no more
On Mon, Jun 18, 2007 at 01:32:21PM +1000, Murray Taylor wrote:
I can only think of one other point for this...
Interrupt latency. Depending on what you are attempting to do,
the variable nature of interrupt responses could be an issue.
I.e. if the system becomes io bound during a data capture
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Chad Perrin
Sent: Monday, June 18, 2007 3:32 AM
To: [EMAIL PROTECTED]
Subject: Re: FreeBSD and Robotics
and within a second has come fully ready, and operating. You could not
wait the 30-60 seconds
It's only as good as the drivers you write to control the robot. It
also depends on just how critical your critical situations refers
to.
In situations where human life is directly dependent upon the
integrity of the system, a modular kernel design has traditionally
been preferred over the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Modulok
Sent: Monday, 18 June 2007 12:40 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: FreeBSD and Robotics
It's only as good as the drivers you write to control the robot. It
also
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Modulok
Sent: Sunday, June 17, 2007 7:40 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: FreeBSD and Robotics
It's only as good as the drivers you write to control the robot. It
also
