On 20/03/15 01:54, Chris Johns wrote:
On 20/03/2015 11:27 am, Joel Sherrill wrote:
20 Hz is a 50 millisecond period.
Ah, thanks. I read it on a phone as 20KHz and was confused and did not
reread.
I have assumed that he meant this was the largest clock tick time
quantum which is reasona
On 20/03/2015 11:27 am, Joel Sherrill wrote:
20 Hz is a 50 millisecond period.
Ah, thanks. I read it on a phone as 20KHz and was confused and did not
reread.
I have assumed that he meant this was the largest clock tick time quantum which
is reasonable to configure.
50msec is fine with
ps://devel.rtems.org/ticket/2271).
>
>This is really cool stuff and I think the graphs so far are excellent.
>
>> In the progress, I found out that the minimum RTEMS system clock
>> frequency should at least be 20Hz to guarantee a correct
>functionality.
>> Are there users that
llent.
In the progress, I found out that the minimum RTEMS system clock
frequency should at least be 20Hz to guarantee a correct functionality.
Are there users that are troubled by this minimum system clock frequency?
I am a little confused with the wording here.
To me a 'system clock fre
s, I found out that the minimum RTEMS system clock
>frequency should at least be 20Hz to guarantee a correct functionality.
>Are there users that are troubled by this minimum system clock
>frequency?
I have been recommending 1 ms as a good starting spot for a clock tick quantum
for years.
Hello,
currently I am working on the implementation of FreeBSD timecounters
into RTEMS as illustrated in Ticket #2271 of the developer's board
(https://devel.rtems.org/ticket/2271).
In the progress, I found out that the minimum RTEMS system clock
frequency should at least be 20Hz to guar
