On 17/10/2018 07:59, Chris Johns wrote:
On 17/10/18 4:05 pm, Sebastian Huber wrote:
On 17/10/2018 02:46, Chris Johns wrote:
On 16/10/2018 19:34, Sebastian Huber wrote:
On 16/10/2018 10:28, jameszxj wrote:
CPU:zynq z7020 RTEMS version: master version
SMP define:
#define CONFIGURE_MAXIMUM_PROC
On 17/10/18 4:05 pm, Sebastian Huber wrote:
> On 17/10/2018 02:46, Chris Johns wrote:
>> On 16/10/2018 19:34, Sebastian Huber wrote:
>>> On 16/10/2018 10:28, jameszxj wrote:
CPU:zynq z7020 RTEMS version: master version
SMP define:
#define CONFIGURE_MAXIMUM_PROCESSORS 2
>
On 17/10/2018 04:17, jameszxj wrote:
thanks,
1.I read the c-use doc, but still confused about EDF SCHEDULER.
The doc said "All SMP schedulers included in RTEMS are priority based. "
Is that mean High priority task always piror low priority task just
like Priority SMP Scheduler.
But some doc fro
On 17/10/2018 02:46, Chris Johns wrote:
On 16/10/2018 19:34, Sebastian Huber wrote:
On 16/10/2018 10:28, jameszxj wrote:
CPU:zynq z7020 RTEMS version: master version
SMP define:
#define CONFIGURE_MAXIMUM_PROCESSORS 2
#if 1
#define CONFIGURE_MAXIMUM_PRIORITY 255
#define CONFIGURE_SCHED
On 17/10/2018 00:43, Chris Johns wrote:
On 16/10/2018 22:29, Sebastian Huber wrote:
Module:rtems-libbsd
Branch:master
Commit:c464b9e40478aeaf2691141952e553b31990cd8e
Changeset:http://git.rtems.org/rtems-libbsd/commit/?id=c464b9e40478aeaf2691141952e553b31990cd8e
Author:Sebastian
On 17/10/2018 13:17, jameszxj wrote:
> 2.I create a patch about top usage to make the display messages look
> reasonable,
> if someone have time to review it?
Could you please create a ticket on the 5.1 milestone and attach the patch?
The first page of the wiki at https://devel.rtems.org/ has a
thanks,
1.I read the c-use doc, but still confused about EDF SCHEDULER.
The doc said "All SMP schedulers included in RTEMS are priority based. "
Is that mean High priority task always piror low priority task just like
Priority SMP Scheduler.
But some doc from internet said EDF scheduler has a dyn
On 16/10/2018 19:34, Sebastian Huber wrote:
> On 16/10/2018 10:28, jameszxj wrote:
>> CPU:zynq z7020 RTEMS version: master version
>> SMP define:
>> #define CONFIGURE_MAXIMUM_PROCESSORS 2
>>
>> #if 1
>> #define CONFIGURE_MAXIMUM_PRIORITY 255
>>
>> #define CONFIGURE_SCHEDULER_PRIORITY_SMP
>
On 16/10/2018 22:29, Sebastian Huber wrote:
> Module:rtems-libbsd
> Branch:master
> Commit:c464b9e40478aeaf2691141952e553b31990cd8e
> Changeset:
> http://git.rtems.org/rtems-libbsd/commit/?id=c464b9e40478aeaf2691141952e553b31990cd8e
>
> Author:Sebastian Huber
> Date: Tue Oct
On 15/10/2018 14:52, Joel Sherrill wrote:
Does doing this mean that autoconf probes now need to pass an extra
library to link against?
I think Autoconf is not an issue. By default, the feature probes will
use the dummy crt0.o provided by Newlib.
The detault config primarily exists to allow
On 16/10/2018 10:28, jameszxj wrote:
Hi,
ask questions again,(◡‿◡)
Board infomation:
CPU:zynq z7020 RTEMS version: master version
SMP define:
#define CONFIGURE_MAXIMUM_PROCESSORS 2
#if 1
#define
Hi,
ask questions again,(◡‿◡)
Board infomation:
CPU:zynq z7020 RTEMS version: master version
SMP define:
#define CONFIGURE_MAXIMUM_PROCESSORS2
#if 1
#define CONFIGURE_MAXIMUM_PRIORITY
Hi Joel,
it took some time, but today I will send you a set of agreements from
our embedded brains team via PM.
Kind regards,
Thomas.
Am 07.08.18 um 23:21 schrieb Joel Sherrill:
> Hi
>
> I have attached a letter (PDF) to ticket 3053
> (http://devel.rtems.org/ticket/3053) from On-Line Applicati
13 matches
Mail list logo