DSRs are not preemptable, and currently all pending DSRs must run to
completion before any thread gets to execute. So as far as worst case
thread response time is concerned, prioritizing DSRs amongst
themselves will have no effect. So the only alternative approach would
be to prioritize DSRs in th
"Fabian Scheler" <[EMAIL PROTECTED]> writes:
> > I was hesitant to raise this subject, but I am delighted to see the
> > discussion that has grown out of my initial query. Discussions such as
> > this can only serve to make eCos a more reliable and relevant real-time
> > operating system in embed
Thanks for your insightful response.
I'll pass the responses along to my bosses and see which way they want
to process from here.
Have a great day,
Don Walton
On Thu, 2006-12-14 at 16:14 +, Nick Garnett wrote:
> Donald Walton <[EMAIL PROTECTED]> writes:
>
> > I would be interested to know t
Donald Walton <[EMAIL PROTECTED]> writes:
> I would be interested to know the type of testing eCos has been through.
> If it has been successfully tested as part of an embedded aviation
> system, I would agree with you. If it has been tested as part of the
> embedded system for a printer or digit
I was hesitant to raise this subject, but I am delighted to see the
discussion that has grown out of my initial query. Discussions such as
this can only serve to make eCos a more reliable and relevant real-time
operating system in embedded system development.
Another issue that would have to be
I apologize for the retrasmission of this message. It was originally
sent to the wrong eCos group.
I would be interested to know the type of testing eCos has been through.
If it has been successfully tested as part of an embedded aviation
system, I would agree with you. If it has been tested as
> From: Don Walton [mailto:[EMAIL PROTECTED]
>
> I would be interested to know the type of testing eCos has been
> through. If it has been successfully tested as part of an
> embedded aviation system, I would agree with you. If it has been
> tested as part of the embedded system for a printer or
> From: Donald Walton
>
> This is in no way intended to be an edict.
>
> However, there are environments where object oriented software using
> multiple inheritance is discouraged. Using multiple inheritance in such
> environments can lead to costly testing to prove that the multiple
> inheritance
This is in no way intended to be an edict.
However, there are environments where object oriented software using
multiple inheritance is discouraged. Using multiple inheritance in such
environments can lead to costly testing to prove that the multiple
inheritance scenario is functioning exactly as
Donald Walton wrote:
I have started looking more closely at the core of eCos. I noticed that
multiple inheritance appears to be used in connection with the
Cyg_Thread class. The arena I am working in does not permit multiple
inheritance.
What does this mean? A design edict? "Thall shalt not
I have started looking more closely at the core of eCos. I noticed that
multiple inheritance appears to be used in connection with the
Cyg_Thread class. The arena I am working in does not permit multiple
inheritance.
This raises the following questions:
Would it be difficult task to remove the
11 matches
Mail list logo
