Hello,
On 10/09/15 20:01, Joel Sherrill wrote:
Hi
Fails like this. Patches appreciated.
or1k-rtems4.11-gcc --pipe -DHAVE_CONFIG_H -I../../..
-I../../../../cpukit/../../../generic_or1k/lib/include -O2 -O0 -g
-Wall -Wmissing-prototypes -Wimplicit-function-declaration
-Wstrict-prototypes
On 11/09/15 02:25, Cyrille Artho wrote:
Dear all,
Please let me try to clarify:
1. Our understanding so far was that upon lock release, the priority
instantly gets reverted back to the previous priority. This also
applies for nested locks, i.e., a higher priority gets reverted
(stepwise) when
On 11/09/15 10:10, Inderjit Singh wrote:
Can I presume that using errno with RTEMS does not work? To me I'm
baffled that a RTEMS_SUCCESSFULL value must be returned in order to
retain the errno value.
The standard drivers are quite primitive. You may have a look at IMFS
generic nodes, if you
Hello Saurabh,
On 11/09/15 02:14, Saurabh Gadia wrote:
Hi Sebastian,
Sorry for late reply. I was out of town and could not reply. I am bit
confused with above description which I need to get clarified:
1. replaced LIFO with sorted list: I don't change the mutex order to
make the list
Hi,
Can I presume that using errno with RTEMS does not work? To me I'm baffled that
a RTEMS_SUCCESSFULL value must be returned in order to retain the errno value.
regards,
Indy
From: Inderjit Singh
Sent: 24 August 2015 15:07
To: Chris Johns; devel@rtems.org
On 11/09/15 13:28, Inderjit Singh wrote:
So basically you're saying is that i cannot use errno when using the primitve
driver standard driver but use IMFS instead if I want to retain an errno value
set in driver and that is recieved by the app.
Yes, if you are unlucky with what
Thanks Sebastian for you response.
So basically you're saying is that i cannot use errno when using the primitve
driver standard driver but use IMFS instead if I want to retain an errno value
set in driver and that is recieved by the app.
Regards,
Indy
> The test runners are in "sim-scripts" make sure a "realview_pbx_a9_qemu
> -i ticker.exe" produces the expected output.
Hi, silly question here, running ticker gave me the elapsed times
but not in 'real time'. It prints 09:00:00, 09:00:04,..., 09:00:34 immediately.
Is this a normal behaviour
