Hello,
I am not sure which problem you want to address. For the watchdogs we
use currently a 64-bit integer key for relative and absolute timeouts.
For the watchdog it is important that
* the key comparison operations are fast,
* the conversion from common time formats to the key are fast, an
On 27/07/2016 18:56, Sebastian Huber wrote:
-RTEMS_INLINE_ROUTINE Thread_Control
*_Thread_Lock_acquire_default_for_executing(
+RTEMS_INLINE_ROUTINE Thread_Control
*_Thread_Wait_acquire_default_for_executing(
This and others have broken libbsd:
./libbsd.a(subr_sleepqueue.c.16.o): In function
On 28/07/2016 07:29, Pavel Pisa wrote:
But discussion and counter examples are welcome.
How do these time formats interact with time management protocol like
NTP and PTP?
We should consider NTP and PTP interfaces if we are reviewing how we
manage time. I am not asking these be implemented
On 27/07/2016 19:28, Pavel Pisa wrote:
On Wednesday 27 of July 2016 02:57:06 Chris Johns wrote:
Pavel, thanks for the excellent detail provided. I will try and expand
on a couple of parts being discussed.
You need to link list of symbols to the base executable image
to inform runtime linker whi
Hello Gedare,
thanks much for the great summary of the discussion.
On Wednesday 27 of July 2016 18:30:02 Gedare Bloom wrote:
> After an IRC chat this morning with Pavel, we've decided to query
> everyone about thoughts on unifying the internal score representations
> for time into a single format
After an IRC chat this morning with Pavel, we've decided to query
everyone about thoughts on unifying the internal score representations
for time into a single format. This discussion comes from the work
I've done with nanosleep, which now uses both the relative and
absolute watchdogs that have two
>
> The rtems_waf support (https://git.rtems.org/chrisj/rtems_waf.git/) now
>> provides a simple way to add files via an embedded tar file to an
>> executable. You can:
>
> How can I start using WAF build system? I found
> https://devel.rtems.org/wiki/waf on the wiki but it wasn't helping much.
>
F
Interestingly, when I compiled and ran dl01 and dl02 manually, using the
source files that were generated during making rtems (like dl-tar.c/h
etc.), BUT with application development Makefile (from examples-v2
hello_world_c), AND CFLAGS from the generated Makefile for dl01 test, I got
the following
Hello,
Thanks for the answers Pavel, Chris.
You need to link list of symbols to the base executable image
> to inform runtime linker which symbols are available.
I followed your instructions carefully and after building my app, I get an
"untar failed: 1" error. How should I debug this error? My
Hello Chris,
thanks for clarification.
On Wednesday 27 of July 2016 02:57:06 Chris Johns wrote:
> Pavel, thanks for the excellent detail provided. I will try and expand
> on a couple of parts being discussed.
> > You need to link list of symbols to the base executable image
> > to inform runtime
10 matches
Mail list logo
