On Wed, Jun 01, 2005 at 04:02:44PM -0700, Bill Huey wrote:
> > people will just assume it to be hard-RT and they could build hardware
> > with random drivers thinking that they will get the gurantee. I
> > understand it's ok with you since you're able to evaluate the RT-safety
> > of every driver you use, but I sure prefer "ruby hard" solutions that
> > don't require looking into drivers to see if they're RT-safe.
>
> Again, this has been covered previously by this thread. It's ultimately
> about writing RT apps that have a more sophisticated use that RTAI or
> RT Linux.
Also, I'm telling you as a person that works for a well known RTOS company
that this patch is very very close to achieving the hard determinism goals
outlined. It has good latency and good overall kernel performancei and it's
much closer to your notion of "ruby" hard RT that you might realize. What's
needed to be done is largely driver mop up and nothing more that I can tell.
There hasn't been any major driver changes submitted recently with this
patch so the code base is pretty stable at the moment.
bill
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
