Hello,
ah, sure. I did not connect "tests/malloc" to the path in RIOT. Thanks for the
clarification.
Raphael
> On Jan 30, 2015, at 4:07 PM, Benjamin Valentin
> wrote:
>
>
> On 24.01.2015 11:04, Hiesgen, Raphael wrote:
>> Hello Benjamin,
>>
>>> I'm not sure what that documentation is based
On 24.01.2015 11:04, Hiesgen, Raphael wrote:
Hello Benjamin,
I'm not sure what that documentation is based on though, running tests/malloc
will allocate and free all available memory just fine.
may I ask how you tested this?
I just flashed the test to my board (not stm32f4discovery, but _s
Hello Benjamin,
> I'm not sure what that documentation is based on though, running tests/malloc
> will allocate and free all available memory just fine.
may I ask how you tested this?
Raphael
___
devel mailing list
devel@riot-os.org
http://lists.riot
On 22.01.2015 15:45, Martine Lenders wrote:
Hi Raphael,
Since I am interested in the stm32f4discovery, everything should
be fine?
Was that a question? I guess it was… As far as its documentation goes
free is not possible by now on stm32f4:
https://github.com/RIOT-OS/RIOT/blob/master
Hello Martine,
> Was that a question? I guess it was… As far as its documentation goes free is
> not possible by now on stm32f4:
> https://github.com/RIOT-OS/RIOT/blob/master/cpu/stm32f4/syscalls.c#L122
that was indeed a question and a bit of an assumption. The previously mentioned
wiki entr
Hi Raphael,
Since I am interested in the stm32f4discovery, everything should be fine?
>
Was that a question? I guess it was… As far as its documentation goes free
is not possible by now on stm32f4:
https://github.com/RIOT-OS/RIOT/blob/master/cpu/stm32f4/syscalls.c#L122
Martine
__
Hi,
thanks for the answers! Since I am interested in the stm32f4discovery,
everything should be fine?
Raphael
> On Jan 22, 2015, at 11:03 AM, Ludwig Ortmann
> wrote:
>
> Hi,
>
> On Thu, Jan 22, 2015 at 10:56:22AM +0100, Martine Lenders wrote:
>> for the native-stuff you have to ask Ludwig f
Hi,
On Thu, Jan 22, 2015 at 10:56:22AM +0100, Martine Lenders wrote:
> for the native-stuff you have to ask Ludwig for the specifics as to of why,
> but most of the hosts system's implementation of standard functions are
> wrapped. I think this was because our POSIX interface would otherwise
> col
Hi Raphael,
for the native-stuff you have to ask Ludwig for the specifics as to of why,
but most of the hosts system's implementation of standard functions are
wrapped. I think this was because our POSIX interface would otherwise
colide with the system's POSIX interface. As for the other boards I'm
Hi Raphael,
On Thu, Jan 22, 2015 at 09:41:31AM +, Hiesgen, Raphael wrote:
> I am curious as to how memory management works. Searching the code for "void
> free(" returns two implementations. One implements the function in the native
> port as a wrapper of the systems implementations (?) and
Hello,
I am curious as to how memory management works. Searching the code for "void
free(" returns two implementations. One implements the function in the native
port as a wrapper of the systems implementations (?) and the other does nothing
(found in malloc.h in the folder oneway-malloc and i
11 matches
Mail list logo
