On 4/12/2014 6:31 pm, Sebastian Huber wrote:
Ah of course. Why not move the bspinit.c one into the cpukit and use
that rather than add another copy ?
Should we really initialize the network by default?
No and I feel that should do from bspinit.c.
If you look at the README file in the
du
On 04/12/14 08:25, Chris Johns wrote:
On 4/12/2014 5:30 pm, Sebastian Huber wrote:
On 04/12/14 00:00, Joel Sherrill wrote:
On December 3, 2014 4:53:23 PM EST, Chris Johns
wrote:
>On 3/12/2014 7:46 pm, Sebastian Huber wrote:
>>The dummy.c is a de-facto default configuration so use unlimited
On 4/12/2014 5:30 pm, Sebastian Huber wrote:
On 04/12/14 00:00, Joel Sherrill wrote:
On December 3, 2014 4:53:23 PM EST, Chris Johns wrote:
>On 3/12/2014 7:46 pm, Sebastian Huber wrote:
>>The dummy.c is a de-facto default configuration so use unlimited
>objects
>>and the stack checker. Th
On 04/12/14 00:00, Joel Sherrill wrote:
On December 3, 2014 4:53:23 PM EST, Chris Johns wrote:
>On 3/12/2014 7:46 pm, Sebastian Huber wrote:
>>The dummy.c is a de-facto default configuration so use unlimited
>objects
>>and the stack checker. This makes it easier for new RTEMS users
>which
On December 3, 2014 4:53:23 PM EST, Chris Johns wrote:
>On 3/12/2014 7:46 pm, Sebastian Huber wrote:
>> The dummy.c is a de-facto default configuration so use unlimited
>objects
>> and the stack checker. This makes it easier for new RTEMS users
>which
>> will likely use this file if they just w
On 3/12/2014 7:46 pm, Sebastian Huber wrote:
The dummy.c is a de-facto default configuration so use unlimited objects
and the stack checker. This makes it easier for new RTEMS users which
will likely use this file if they just work with the usual main()
function as the application entry point.
The dummy.c is a de-facto default configuration so use unlimited objects
and the stack checker. This makes it easier for new RTEMS users which
will likely use this file if they just work with the usual main()
function as the application entry point. Provide proper arguments for
main() using the B