Do I need to do anything?
On Mon, 18 Mar 2024 at 16:38, Kinsey Moore wrote:
> Sorry, I didn't realize I had tests turned off in my local build when I
> checked this. The test is now gated behind NEEDS_CLOCK_DRIVER as well.
>
> Kinsey
>
> On Mon, Mar 18, 2024 at 4:15 AM Sebastian Huber <
> seba
Did you check in the code?
Il mar 12 mar 2024, 21:55 Kinsey Moore ha
scritto:
> Sorry, I missed this in the deluge of emails. Looks good to me.
>
> Kinsey
>
> On Tue, Mar 12, 2024 at 8:17 PM zack leung
> wrote:
>
>> ping
>>
>> On Fri, 8 Mar 2024 at
ping
On Fri, 8 Mar 2024 at 22:03, wrote:
> From: Zack leung
>
> ---
> cpukit/doxygen/appl-config.h | 3 +--
> cpukit/include/rtems/confdefs/clock.h | 4
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/cpukit/doxygen/appl-config
Hey i've replied with another patch :)
On Tue, 5 Mar 2024 at 10:42, Kinsey Moore wrote:
> Zack,
> It looks like there's been a little confusion here. Sebastian was
> requesting that you condense the pair of #ifs into a single #if with && and
> the defined check st
ping
On Tue, 27 Feb 2024 at 21:33, zack leung wrote:
>
> joel said:
>+#if CONFIGURE_TICKS_PER_TIMESLICE <= 0 &&
> > defined(CONFIGURE_TICKS_PER_TIMESLICE)
> > + #error "CONFIGURE_TICKS_PER_TIMESLICE shall be greater than zero"
>
it is safer to check that
> it is defined
> before checking its value.
Yes, the defined() check should be first. - sebestian
You said this in relation to joel's comment in my previous thread. You can
check in either one. The previous one used the "and" statement.
Zack
On Tue, 2
ping
On Tue, 20 Feb 2024 at 20:25, zack leung wrote:
> ping
>
> On Sun, 18 Feb 2024 at 21:15, wrote:
>
>> ---
>> cpukit/doxygen/appl-config.h | 2 +-
>> cpukit/include/rtems/confdefs/clock.h | 6 ++
>> 2 files changed, 7 insertions(+), 1 d
ping
On Sun, 18 Feb 2024 at 21:15, wrote:
> ---
> cpukit/doxygen/appl-config.h | 2 +-
> cpukit/include/rtems/confdefs/clock.h | 6 ++
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h
> index bd7cde628f..
; > I'm cc'ing Sebastian because you edited the text in a generated file. He
> > should be able to point us to the right place to fix it.
> >
> > On Mon, Feb 12, 2024 at 8:26 PM > <mailto:zakthertems...@gmail.com>> wrote:
> >
> > Fro
ping
On Tue, 31 Oct 2023 at 22:07, zack leung wrote:
> Sorry either I lack knowledge in C or lack knowledge in working with
> rtems. Do you mean if rtems smp is defined then we make sure that scheduler
> context base type is defined? I don't quite understand why it would be
>
ler.h
file which is where the struct is defined.
On Mon, 30 Oct 2023 at 03:04, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 29.10.23 02:44, zack leung wrote:
> > ./../../cpukit/include/rtems/score/schedulerpriority.h:87:21: error:
> > field '
:40, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 27.10.23 03:43, zack leung wrote:
> > ping
> >
> > On Tue, 24 Oct 2023 at 22:17, zack leung > <mailto:zakthertems...@gmail.com>> wrote:
> >
> > that didn't work
ping
On Tue, 24 Oct 2023 at 22:17, zack leung wrote:
> that didn't work but i'm thinking of defining a char array that is equal
> to the size of the processor lock and the isr lock? i figured that the
> processor lock is 64 bits and isr lock is a one bit?
> I'm con
ue, 24 Oct 2023 at 08:31, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 24.10.23 14:02, zack leung wrote:
> > hi! sabestian did you mean the size of the structure?
>
> Yes, one option to get rid of the empty structures is to just provide
> typedefs,
hi! sabestian did you mean the size of the structure?
On Mon, 23 Oct 2023 at 10:20, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Zack,
>
> there is a bit more work to do to fix this warning. The warning fix
> should not result in a size increase of the
---
cpukit/include/rtems/score/isrlock.h | 1 +
cpukit/include/rtems/score/scheduler.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/cpukit/include/rtems/score/isrlock.h
b/cpukit/include/rtems/score/isrlock.h
index 7586624f9d..612f17a34d 100644
--- a/cpukit/include/rtems/score/isrlock.h
diff --git a/cpukit/libmisc/regulator/regulator.c
b/cpukit/libmisc/regulator/regulator.c
index 2071c468fd..97a48be4f5 100644
--- a/cpukit/libmisc/regulator/regulator.c
+++ b/cpukit/libmisc/regulator/regulator.c
@@ -35,6 +35,7 @@
#include
#include
+#include
#include
--
2.34.1
___
a patch, just a code change snippet and explanation. Zack
> turned it into
> > a patch. You will need to post that on the ticket to get the submitter's
> feedback.
> >
> > I hope you don't mind copying that to the ticket and seeing what you
> think is
> >
fixes #4903 adressing an error in the TMS570 console driver
---
bsps/arm/tms570/console/tms570-sci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fixes #4903
diff --git a/bsps/arm/tms570/console/tms570-sci.c
b/bsps/arm/tms570/console/tms570-sci.c
index 768770a4c8..59a0b7e6f1 100644
---
Fixes #4903
diff --git a/bsps/arm/tms570/console/tms570-sci.c
b/bsps/arm/tms570/console/tms570-sci.c
index 768770a4c8..59a0b7e6f1 100644
--- a/bsps/arm/tms570/console/tms570-sci.c
+++ b/bsps/arm/tms570/console/tms570-sci.c
@@ -311,7 +311,7 @@ bool tms570_sci_set_attributes(
/* Apply baudrate to
Fixes #4903
diff --git a/bsps/arm/tms570/console/tms570-sci.c
b/bsps/arm/tms570/console/tms570-sci.c
index 768770a4c8..59a0b7e6f1 100644
--- a/bsps/arm/tms570/console/tms570-sci.c
+++ b/bsps/arm/tms570/console/tms570-sci.c
@@ -311,7 +311,7 @@ bool tms570_sci_set_attributes(
/* Apply baudrate to
---
bsps/arm/tms570/console/tms570-sci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Fixes #4903
diff --git a/bsps/arm/tms570/console/tms570-sci.c
b/bsps/arm/tms570/console/tms570-sci.c
index 768770a4c8..59a0b7e6f1 100644
--- a/bsps/arm/tms570/console/tms570-sci.c
+++ b/bsps/arm/tms570
- hi guys i am working on #4674
- currently i'm not able to get it to produce the error
- my code looks like this
-
#ifdef HAVE_CONFIG_H
#include "config.h"
#endif
#include
#include
#include
#include
#include
#include
#include
#include
#include
const char rtems_test_name[] = "FSREADDIR
From: zack
Closes #4557
---
cpukit/libmisc/shell/main_edit.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/cpukit/libmisc/shell/main_edit.c b/cpukit/libmisc/shell/main_edit.c
index 6e954639e2..8317452b7b 100644
--- a/cpukit/libmisc/shell/main_edit.c
+++ b/cpukit/libmisc
libmisc/shell: User can't cut using ctrl e and x in medit
Closes #4557
---
cpukit/libmisc/shell/main_edit.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/cpukit/libmisc/shell/main_edit.c
b/cpukit/libmisc/shell/main_edit.c
index 6e954639e2..8317452b7b 100644
--- a/cpukit/li
fixes 4557 user can't cut using ctrl e and x in medit
---
cpukit/libmisc/shell/main_edit.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/cpukit/libmisc/shell/main_edit.c
b/cpukit/libmisc/shell/main_edit.c
index 6e954639e2..8317452b7b 100644
--- a/cpukit/libmisc/shell/main_e
fixes #4557
---
cpukit/libmisc/shell/main_edit.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/cpukit/libmisc/shell/main_edit.c
b/cpukit/libmisc/shell/main_edit.c
index 191eefa19d..71bb1d931b 100644
--- a/cpukit/libmisc/shell/main_edit.c
+++ b/cpukit/libmisc/shell/main_ed
Hello,
I'm currently looking at ticket 4364. It says that there is a difference
between the test results printed by the console and what is emailed to
@devel. I don't see a difference and i'm just wondering if it has been
fixed
Zack
__
Closes #4751
---
cpukit/libmisc/shell/main_chmod.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/libmisc/shell/main_chmod.c
b/cpukit/libmisc/shell/main_chmod.c
index 1f646d92d4..9a42cbd940 100644
--- a/cpukit/libmisc/shell/main_chmod.c
+++ b/cpukit/libmisc/shell/main_c
Closes #4751
---
cpukit/libmisc/shell/main_chmod.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/libmisc/shell/main_chmod.c
b/cpukit/libmisc/shell/main_chmod.c
index 1f646d92d4..9a42cbd940 100644
--- a/cpukit/libmisc/shell/main_chmod.c
+++ b/cpukit/libmisc/shell/main_c
Closes #4751
---
cpukit/libmisc/shell/main_chmod.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/libmisc/shell/main_chmod.c
b/cpukit/libmisc/shell/main_chmod.c
index 1f646d92d4..9a42cbd940 100644
--- a/cpukit/libmisc/shell/main_chmod.c
+++ b/cpukit/libmisc/shell/main_c
Bump
On Wed, 14 Dec 2022 at 20:12, zack leung wrote:
> Closes #4556
> ---
> cpukit/libmisc/shell/main_mmove.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/cpukit/libmisc/shell/main_mmove.c
> b/cpukit/libmisc/shell/main_mmove.c
> index 38731
Closes #4556
---
cpukit/libmisc/shell/main_mmove.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/libmisc/shell/main_mmove.c
b/cpukit/libmisc/shell/main_mmove.c
index 38731b10a2..0029882d62 100644
--- a/cpukit/libmisc/shell/main_mmove.c
+++ b/cpukit/libmisc/shell/main_m
Ping
Il ven 4 mar 2022, 21:58 zack leung ha scritto:
> closes #4503
> ---
> cpukit/include/rtems/libcsupport.h| 5 +++
> cpukit/libcsupport/src/mallocusablesize.c | 48 +++
> spec/build/cpukit/librtemscpu.yml | 1 +
> testsuites/libtests
closes #4503
---
cpukit/include/rtems/libcsupport.h| 5 +++
cpukit/libcsupport/src/mallocusablesize.c | 48 +++
spec/build/cpukit/librtemscpu.yml | 1 +
testsuites/libtests/malloctest/init.c | 15 ++-
4 files changed, 68 insertions(+), 1 deletion(-)
c
---
cpukit/include/rtems/libcsupport.h| 5 +++
cpukit/libcsupport/src/mallocusablesize.c | 48 +++
spec/build/cpukit/librtemscpu.yml | 1 +
testsuites/libtests/malloctest/init.c | 15 ++-
4 files changed, 68 insertions(+), 1 deletion(-)
create mode 10
ping
On Sat, 26 Feb 2022 at 02:42, zack leung wrote:
> ping
> *
>
> On Sun, 20 Feb 2022 at 02:55, zack leung wrote:
>
>> diff --git a/cpukit/include/rtems/libcsupport.h
>> b/cpukit/include/rtems/libcsupport.h
>> index f4be4cfc9a..ec385bb71a 100644
>> -
ping
*
On Sun, 20 Feb 2022 at 02:55, zack leung wrote:
> diff --git a/cpukit/include/rtems/libcsupport.h
> b/cpukit/include/rtems/libcsupport.h
> index f4be4cfc9a..ec385bb71a 100644
> --- a/cpukit/include/rtems/libcsupport.h
> +++ b/cpukit/include/rtems/libcsupport.h
> @@ -73,
diff --git a/cpukit/include/rtems/libcsupport.h
b/cpukit/include/rtems/libcsupport.h
index f4be4cfc9a..ec385bb71a 100644
--- a/cpukit/include/rtems/libcsupport.h
+++ b/cpukit/include/rtems/libcsupport.h
@@ -73,7 +73,10 @@ extern size_t malloc_free_space(void);
* Find amount of free heap remainin
---
cpukit/include/rtems/libcsupport.h| 5 ++-
cpukit/libcsupport/src/mallocusablesize.c | 47 +++
spec/build/cpukit/librtemscpu.yml | 1 +
testsuites/libtests/malloctest/init.c | 13 +++
4 files changed, 65 insertions(+), 1 deletion(-)
create mode 10
---
cpukit/include/rtems/libcsupport.h| 8 ++-
cpukit/libcsupport/src/mallocusablesize.c | 28 +++
spec/build/cpukit/librtemscpu.yml | 1 +
testsuites/libtests/malloctest/init.c | 15 +++-
4 files changed, 50 insertions(+), 2 deletions(-)
crea
There a way to get the same values used to make the calculation in malloc
get usable size?
Bump
Il ven 7 gen 2022, 21:25 zack leung ha scritto:
> I think that the malloc tests is calculated differently than alloc_size+
> allocsize mod it looks like this
> *alloc_size = (uintptr_t) n
the current block?
On Thu, 6 Jan 2022 at 21:28, Joel Sherrill wrote:
> On Thu, Jan 6, 2022 at 2:55 PM Gedare Bloom wrote:
> >
> > On Tue, Jan 4, 2022 at 6:10 PM zack leung
> wrote:
> > >
> > > Helllo ,
> > > I'm working on a patch fo
Helllo ,
I'm working on a patch for malloc_get_usable size right now so far i have
this test case for malloc, I just make sure that the value is null and i
just malloc an int and then i make a call to the function malloc_usable
size and then i compare it like this.
static void test_malloc_usable
What tasks can I do that can help with ECSS compliance?
Zack
On Mon, 13 Dec 2021 at 21:40, Chris Johns wrote:
> On 14/12/21 1:53 am, Sebastian Huber wrote:
> > Hello,
> >
> > the ESA activity to pre-qualify parts of RTEMS according to ECSS
> requirements is
> &g
bump
On Mon, 18 Oct 2021 at 23:47, zack leung wrote:
> bump
>
>
> On Wed, 6 Oct 2021 at 00:30, zack leung wrote:
>
>> For relative times, the clock identifier is not used to select the clock
>> and instead always the CLOCK_MONOTONIC is used. A side-effect is that
>
bump
On Mon, 18 Oct 2021 at 23:58, zack leung wrote:
> bump
>
>
> On Sat, 25 Sept 2021 at 00:26, zack leung
> wrote:
>
>> bump
>>
>> On Thu, 9 Sept 2021 at 02:17, zack leung
>> wrote:
>>
>>> >Thanks! I guess i'm really unsure a
bump
On Mon, 18 Oct 2021 at 23:46, zack leung wrote:
> fix came from github code inspector, flagged by one of the analysis that
> was done
> ---
> testsuites/libtests/POSIX/calloc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/testsuites/li
bump
On Sat, 25 Sept 2021 at 00:26, zack leung wrote:
> bump
>
> On Thu, 9 Sept 2021 at 02:17, zack leung wrote:
>
>> >Thanks! I guess i'm really unsure about how the pointer relates to the
>> amount of memory that you can use. I assume the Malloc keeps track
bump
On Wed, 6 Oct 2021 at 00:30, zack leung wrote:
> For relative times, the clock identifier is not used to select the clock
> and instead always the CLOCK_MONOTONIC is used. A side-effect is that
> sleep() and nanosleep() use the wrong clock (CLOCK_MONOTONIC instead of
> CL
fix came from github code inspector, flagged by one of the analysis that
was done
---
testsuites/libtests/POSIX/calloc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/testsuites/libtests/POSIX/calloc.c
b/testsuites/libtests/POSIX/calloc.c
index bd04faa800..a7537c8cc4 10064
flagged as uninitialized.
But personally, I feel it's easier to read if we don't change where
variables are defined. An example of this is found in
testsuites/mptests/mp09/task1.c. An array called recieve_Buffer could be
defined later. I'm not sure if this matters much. I want t
ed. I know that
if it's not a realtime clock then
Thread_queue_Context_set_enqueue_timeout_monotonic_timespec is called and i
believe that all the appropriate branches are there to make the monotonic
clock work.
Zack
___
devel mailing list
devel@rtem
bump
On Thu, 9 Sept 2021 at 02:17, zack leung wrote:
> >Thanks! I guess i'm really unsure about how the pointer relates to the
> amount of memory that you can use. I assume the Malloc keeps track of the
> sections being used in the heap. Does this function Allocate 2 blocks si
bump
On Thu, 23 Sept 2021 at 00:21, zack leung wrote:
> I can send an example of the exception if you want.
>
> zack
>
> On Wed, 22 Sept 2021 at 18:01, Gedare Bloom wrote:
>
>> Joel,
>>
>> This looks good to me. I don't know if you can easily test it
I can send an example of the exception if you want.
zack
On Wed, 22 Sept 2021 at 18:01, Gedare Bloom wrote:
> Joel,
>
> This looks good to me. I don't know if you can easily test it?
>
> Gedare
>
> On Wed, Sep 22, 2021 at 11:26 AM zack leung
> wrote:
> >
>
ll hex values now have 8 character width
thread id is now hex
updates #4203
---
cpukit/score/cpu/i386/cpu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/cpukit/score/cpu/i386/cpu.c b/cpukit/score/cpu/i386/cpu.c
index 77b7a7161c..786cf8b0b6 100644
--- a/cpukit/score/cpu
all hex values now have 8 character width
thread id is now hex
---
cpukit/score/cpu/i386/cpu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/cpukit/score/cpu/i386/cpu.c b/cpukit/score/cpu/i386/cpu.c
index 77b7a7161c..786cf8b0b6 100644
--- a/cpukit/score/cpu/i386/cpu.c
+
printk(" EAX = 0%08" PRIx32 "EBX = 0%08" PRIx32 "ECX = 0%08"
PRIx32 "EDX = 0%08" PRIx32 "\n",
should it look like this gedare? will send once you give the ok
On Sun, 19 Sept 2021 at 17:42, zack leung wrote:
> Bumo
&
Bumo
Il ven 17 set 2021, 19:57 zack leung ha scritto:
> Where am i missing it?
>
> Zack
>
> On Fri, 17 Sept 2021 at 23:15, Gedare Bloom wrote:
>
>> Hi Zack,
>>
>> I think you have also missed Joel's request to add an 8-character
>> width specif
Where am i missing it?
Zack
On Fri, 17 Sept 2021 at 23:15, Gedare Bloom wrote:
> Hi Zack,
>
> I think you have also missed Joel's request to add an 8-character
> width specifier.
>
> On Thu, Sep 16, 2021 at 6:19 PM zack leung
> wrote:
> >
> > Thread id i
Thread id is now a Hex value. formatting improved for hex values
Updates #4203
---
cpukit/score/cpu/i386/cpu.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/cpukit/score/cpu/i386/cpu.c b/cpukit/score/cpu/i386/cpu.c
index 77b7a7161c..0f17cf0148 100644
--- a/cpukit/score/
p0);
Before I send my patch here is what i'll change . So i can do this for
example format the hex values with 0x and
have the thread id as a hex value.
On Wed, 15 Sept 2021 at 15:18, Gedare Bloom wrote:
> On Mon, Sep 13, 2021 at 6:10 PM zack leung
> wrote:
> >
> > Gedar
Gedare told me just to change the ID when I submitted the other I sent you
in discord. Sorry for things bouncing back and forth.
On Mon, 13 Sept 2021 at 23:44, Joel Sherrill wrote:
> On Sun, Sep 12, 2021 at 7:02 PM zack leung
> wrote:
> >
> > Thread id is now a Hex value.
Thread id is now a Hex value.
Updates #4203
---
cpukit/score/cpu/i386/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/score/cpu/i386/cpu.c b/cpukit/score/cpu/i386/cpu.c
index 77b7a7161c..06af57418d 100644
--- a/cpukit/score/cpu/i386/cpu.c
+++ b/cpukit/score/cpu/i386/
Where are the duplicates been trying to fix the commit messages?
Thanks zack
Il gio 9 set 2021, 22:30 Gedare Bloom ha scritto:
> Hi Zack,
>
> It looks like something got a little messed up with your commit
> message. Please see if you can fix it to remove the duplication(s).
>
score/i386: improve the format of exception reporting
Updates #4203."Updates #4203."
---
cpukit/score/cpu/i386/cpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/score/cpu/i386/cpu.c b/cpukit/score/cpu/i386/cpu.c
index 77b7a7161c..06af57418d 100644
--- a/cpukit/score/c
implement a wrapper and what safety measures need to be
implemented. So far it's checking if : the block is not in the heap and if
it's been previously used. Is the usable memory in the heap calculated by:
the size of the block * # of blocks?
Thanks, Zack
-- Forwarded message -
Thread ID is now a hex value part of ticket #4203
On Wed, 8 Sept 2021 at 23:58, Zacchaeus Leung
wrote:
> diff --git a/cpukit/score/cpu/i386/cpu.c b/cpukit/score/cpu/i386/cpu.c
> index 77b7a7161c..06af57418d 100644
> --- a/cpukit/score/cpu/i386/cpu.c
> +++ b/cpukit/score/cpu/i386/cpu.c
> @@ -21
ket/4271>?
Thanks
Zack
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
- thread id is printed as a hex value
- EBP ESP is now printed as a address pointer %p
- Program counter is printed as a pinter
Part of ticket #4203
On Wed, 8 Sept 2021 at 00:17, Zacchaeus Leung
wrote:
> ---
> cpukit/score/cpu/i386/cpu.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletion
Say i find an exception (ex format string printing a decimal.) How do I
test that my improvement works?
Thanks
Zack
On Fri, 3 Sept 2021 at 01:36, Joel Sherrill wrote:
> On Thu, Sep 2, 2021 at 8:01 PM zack leung
> wrote:
> >
> > Hello!
> >
> > I'd like to
exception
number/names is in the manual for the architecture. For an i386 or later,
that should be in many places. Where do i find the documentation of the
bsps?
Thanks
Zack
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
How do i report the findings of the psx and tests?
Thanks
Zack
On Thu, 5 Aug 2021 at 19:23, Gedare Bloom wrote:
> On Thu, Aug 5, 2021 at 12:36 PM Zacchaeus Leung
> wrote:
> >
> > the timer_create() method can use CLOCK_MONOTONIC but there was no test
> for this
>
create
if ( ptimer->clock_type != CLOCK_REALTIME && ptimer->clock_type !=
CLOCK_MONOTONIC )
rtems_set_errno_and_return_minus_one( EINVAL );
Zack
On Wed, 4 Aug 2021 at 16:02, Gedare Bloom wrote:
> On Wed, Jul 28, 2021 at 6:28 PM Zacchaeus Leung
> wrote:
> >
>
bump
On Thu, 29 Jul 2021 at 00:28, Zacchaeus Leung
wrote:
> the timer_create() method can use CLOCK_MONOTONIC but there was no test
> for this
>
> Closes #3888
> ---
> cpukit/include/rtems/posix/timer.h| 1 +
> cpukit/posix/src/psxtimercreate.c | 3 +-
> cpukit/posix/src/time
> - remaining = 0;
> + result->tv_nsec=0;
> + result->tv_sec=0;
This isn't correct. result is an uninitialized pointer.
So then how do I set the timespec's value to 0? I have changed the
timespec variables i have declared from pointers to regular variables.
in the original code the
, I have made changes to reduce code duplication. The structure of the
code has changed so I had to format things.
Thanks
Zack
On Thu, 15 Jul 2021 at 15:29, Gedare Bloom wrote:
> The first line of the commit should be shorter. Use a blank line, and
> then close the ticket with the Closes
&value->it_value);
Why convert back and forth between timespec and ticks? why not just
update this function to use timespec values?
Do you want me to change remaining to be a timespec? change the field
it_value to a timespec?
Zack
Ps: thanks for being so patient with my patch. I'm sti
---
cpukit/include/rtems/posix/timer.h| 1 +
cpukit/posix/src/psxtimercreate.c | 5 +-
cpukit/posix/src/timergettime.c | 79 ---
testsuites/psxtests/psxtimer02/psxtimer.c | 38 ++-
4 files changed, 98 insertions(+), 25 deletions(-)
diff --gi
From: zack
---
cpukit/include/rtems/posix/timer.h| 6 ++-
cpukit/posix/src/psxtimercreate.c | 5 +-
cpukit/posix/src/timergettime.c | 61 ---
testsuites/psxtests/psxtimer02/psxtimer.c | 26 +++---
4 files changed, 81 insertions(+), 17
81 matches
Mail list logo
