On 6/06/2014 12:24 am, Marcos Díaz wrote:
From tmtests folder the following tests used more than 3 tasks: tm02,
tm03, tm04, tm05, tm06, tm07, tm10, tm11, tm12, tm13, tm14, tm15, tm
16, tm17, tm18, tm19, tm21, tm22, tm23, tm24, tm 25, tm26, tm29.
Although we reduced the count of tasks for those
From tmtests folder the following tests used more than 3 tasks: tm02,
tm03, tm04, tm05, tm06, tm07, tm10, tm11, tm12, tm13, tm14, tm15, tm
16, tm17, tm18, tm19, tm21, tm22, tm23, tm24, tm 25, tm26, tm29.
Although we reduced the count of tasks for those tests (with the
OPERATION_COUNT macro) with s
Not all the tests run but we achieved many more tests working with this change.
On Thu, Jun 5, 2014 at 10:54 AM, Sebastian Huber
wrote:
> On 2014-06-05 15:04, Marcos Díaz wrote:
>>
>> Yes, we made this patch in order to the testsuites work correctly. So
>> you think we should change the macro val
On 2014-06-05 15:04, Marcos Díaz wrote:
Yes, we made this patch in order to the testsuites work correctly. So
you think we should change the macro value in cpu.h and arm.h as i
proposed before?
So you can run the complete test suite with a default stack size of 1024?
I wouldn't change the defa
Yes, we made this patch in order to the testsuites work correctly. So
you think we should change the macro value in cpu.h and arm.h as i
proposed before?
On Thu, Jun 5, 2014 at 8:37 AM, Sebastian Huber
wrote:
> On 2014-06-04 23:05, Joel Sherrill wrote:
>>
>> FWIW I wrote the confdefs.h part and M
On 2014-06-04 23:05, Joel Sherrill wrote:
FWIW I wrote the confdefs.h part and Marcos wrote the documentation.
He spotted a typo and missed that also.
I am not sure if the BSP should be responsible for a default task stack size.
The BSP has nothing to do with the code generation and the genera
FWIW I wrote the confdefs.h part and Marcos wrote the documentation.
He spotted a typo and missed that also.
I am ok with this patch.
On 6/4/2014 3:58 PM, Marcos Díaz wrote:
> Here is a patch in order to configure the minimum stack size for a
> task for a bsp. We tested it with our bsp to be subm
Here is a patch in order to configure the minimum stack size for a
task for a bsp. We tested it with our bsp to be submitted.
On Wed, Jun 4, 2014 at 12:50 PM, Joel Sherrill
wrote:
> The patch I sent you needs be reflected I user docs. Conf.t in doc/user. But
> it is a prerequisite and independent
On 6/4/2014 8:52 AM, Marcos Díaz wrote:
> Hi, we were running the check_submission script and we were fixing
> some issues. but now we are having two problems:
The script is far from perfect and the structure of a BSP is a moving
target.
> One is that a missing file, for example bsp_interrupt_vect
Hi, we were running the check_submission script and we were fixing
some issues. but now we are having two problems:
One is that a missing file, for example bsp_interrupt_vector_enable,
which is defined in the shared folder outside our bsp's folder, gives
a warning (only with verbose set), but also
It doesn't run in any simulator..
I have another question:
We are developing a bsp for a board with very little memory (32k) when
we tried to run tmtest (and others) we encounter that couldnt allocate
more RAM, and one of the things that we saw we could improve is the
stack size passed for each ta
On 5/30/2014 9:51 AM, Marcos Díaz wrote:
> thanks to all! We will try to submit it soon!
Does the BSP run on any simulator? If so, there are a
couple of other things we like to have to aid automated
testing.
Also there is a new file .tcfg which can list the files
which do not link or run with a k
thanks to all! We will try to submit it soon!
On Thu, May 29, 2014 at 5:16 PM, Joel Sherrill
wrote:
>
> On 5/29/2014 2:34 PM, Gedare Bloom wrote:
>> On Thu, May 29, 2014 at 3:02 PM, Marcos Díaz
>> wrote:
>>> Hi! We are about to submit a BSP but we have some doubts:
>>> In http://www.rtems.org/w
On 5/29/2014 2:34 PM, Gedare Bloom wrote:
> On Thu, May 29, 2014 at 3:02 PM, Marcos Díaz
> wrote:
>> Hi! We are about to submit a BSP but we have some doubts:
>> In http://www.rtems.org/wiki/index.php/Submitting_a_BSP
>> there is a point that refers to:
>>
>> Do all files have a CVS $Id$ in them?
On Thu, May 29, 2014 at 3:02 PM, Marcos Díaz
wrote:
> Hi! We are about to submit a BSP but we have some doubts:
> In http://www.rtems.org/wiki/index.php/Submitting_a_BSP
> there is a point that refers to:
>
> Do all files have a CVS $Id$ in them?
>
> What does this mean?
>
That is outdated and sho
On 5/29/2014 2:02 PM, Marcos Díaz wrote:
> Hi! We are about to submit a BSP but we have some doubts:
What BSP? We are looking forward to it. :)
> In http://www.rtems.org/wiki/index.php/Submitting_a_BSP
> there is a point that refers to:
>
> Do all files have a CVS $Id$ in them?
>
> What does this
Hi! We are about to submit a BSP but we have some doubts:
In http://www.rtems.org/wiki/index.php/Submitting_a_BSP
there is a point that refers to:
Do all files have a CVS $Id$ in them?
What does this mean?
There is other:
Did you provide a TIMES files with the results of the tmtests?
is there a
17 matches
Mail list logo
