psxtests: add POSIX API signature compliance tests for mqueue.h file (GCI 2018)
Hi guys,
Here is the patch file for mqueue.h file.
Thanks
Himanshu
From 2cfa9910237a0c6c3859a8067de7d4e9683cc106 Mon Sep 17 00:00:00 2001
From: Himanshu40
Date: Wed, 28 Nov 2018 13:34:34 +0530
Subject: [PATCH] psxtests: add POSIX API signature compliance tests for
mqueue.h file (GCI 2018)
---
testsuites/psxtests/Makefile.am | 12 +++-
testsuites/psxtests/psxhdrs/mqueue/mq_close.c | 49
.../psxtests/psxhdrs/mqueue/mq_getattr.c | 49
.../psxtests/psxhdrs/mqueue/mq_notify.c | 52 +
testsuites/psxtests/psxhdrs/mqueue/mq_open.c | 51
.../psxtests/psxhdrs/mqueue/mq_receive.c | 52 +
testsuites/psxtests/psxhdrs/mqueue/mq_send.c | 53 +
.../psxtests/psxhdrs/mqueue/mq_setattr.c | 50
.../psxtests/psxhdrs/mqueue/mq_timedreceive.c | 57 ++
.../psxtests/psxhdrs/mqueue/mq_timedsend.c| 58 +++
.../psxtests/psxhdrs/mqueue/mq_unlink.c | 39 +
11 files changed, 521 insertions(+), 1 deletion(-)
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_close.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_getattr.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_notify.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_open.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_receive.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_send.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_setattr.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_timedreceive.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_timedsend.c
create mode 100644 testsuites/psxtests/psxhdrs/mqueue/mq_unlink.c
diff --git a/testsuites/psxtests/Makefile.am b/testsuites/psxtests/Makefile.am
index 39fceb02fe..812dc303b6 100644
--- a/testsuites/psxtests/Makefile.am
+++ b/testsuites/psxtests/Makefile.am
@@ -1093,7 +1093,17 @@ lib_a_SOURCES = psxhdrs/devctl/posix_devctl.c \
psxhdrs/dirent/rewinddir.c \
psxhdrs/dirent/scandir.c \
psxhdrs/dirent/seekdir.c \
- psxhdrs/dirent/telldir.c
+ psxhdrs/dirent/telldir.c \
+ psxhdrs/mqueue/mq_open.c \
+ psxhdrs/mqueue/mq_close.c \
+ psxhdrs/mqueue/mq_getattr.c \
+ psxhdrs/mqueue/mq_setattr.c \
+ psxhdrs/mqueue/mq_notify.c \
+ psxhdrs/mqueue/mq_receive.c \
+ psxhdrs/mqueue/mq_send.c \
+ psxhdrs/mqueue/mq_timedreceive.c \
+ psxhdrs/mqueue/mq_timedsend.c \
+ psxhdrs/mqueue/mq_unlink.c
endif
rtems_tests_PROGRAMS = $(psx_tests)
diff --git a/testsuites/psxtests/psxhdrs/mqueue/mq_close.c b/testsuites/psxtests/psxhdrs/mqueue/mq_close.c
new file mode 100644
index 00..02afecff88
--- /dev/null
+++ b/testsuites/psxtests/psxhdrs/mqueue/mq_close.c
@@ -0,0 +1,49 @@
+/**
+ * @file
+ * @brief mq_close() API Conformance Test
+ */
+
+ /*
+ * COPYRIGHT (c) 2018.
+ * Himanshu Sekhar Nayak
+ *
+ * Permission to use, copy, modify, and/or distribute this software
+ * for any purpose with or without fee is hereby granted.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
+ * WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
+ * WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR
+ * BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES
+ * OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
+ * WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
+ * ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ */
+
+ #ifdef HAVE_CONFIG_H
+ #include "config.h"
+ #endif
+
+ #include
+ #include
+
+ int test( void );
+
+ #define MQ_MAXMSG 1
+ #define MQ_MSGSIZEsizeof(int)
+
+ int test( void )
+ {
+mqd_t mqdes;
+struct mq_attr mqstat;
+const char *q_name;
+int result;
+
+mqstat.mq_maxmsg = MQ_MAXMSG;
+mqstat.mq_msgsize = MQ_MSGSIZE;
+q_name = "queue";
+
+mqdes = mq_open( q_name, O_CREAT | O_RDWR, 0x777, &mqstat );
+result = mq_close( mqdes );
+
+return result;
+ }
diff --git a/testsuites/psxtests/psxhdrs/mqueue/mq_getattr.c b/testsuites/psxtests/psxhdrs/mqueue/mq_getattr.c
new file mode 100644
index 00..092c6bf8cc
--- /dev/null
+++ b/testsuites/psxtests/psxhdrs/mqueue/mq_getattr.c
@@ -0,0 +1,49 @@
+/**
+ * @file
+ * @brief mq_getattr() API Conformance Test
+ */
+
+ /*
+ * COPYRIGHT (c) 2018.
+ * Himanshu Sekhar Nayak
+ *
+ * Permission to use, copy, modify, and/or distribute this software
+ * for any purpose with or without fee is hereby granted.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
+ * WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
+ * WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR
+ * BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES
+ * OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
+ * WH
Re: The T Test Framework
Hello, I changed the test runner API a bit. Now it is also possible to test the system initialization for example. The test output of the attached example test (derived from sptests/spsysinit01): A:sysinit S:Platform:RTEMS S:Compiler:7.3.0 20180125 (RTEMS 5, RSB 30da0c720b78eba16a3f5272206c07415368617b, Newlib 2ab57ad59bc35dafffa69cd4da5e228971de069f) S:Version:5.0.0.9c792752178ce9bfaffec0ae3d2f150d8f01821f S:BSP:erc32 S:RTEMS_DEBUG:1 S:RTEMS_MULTIPROCESSING:0 S:RTEMS_POSIX_API:0 S:RTEMS_PROFILING:0 S:RTEMS_SMP:1 B:sysinit P:0:0:?:test-sysinit.c:243 P:1:0:?:test-sysinit.c:252 P:2:0:?:test-sysinit.c:257 P:3:0:?:test-sysinit.c:262 P:4:0:?:test-sysinit.c:263 P:5:0:?:test-sysinit.c:268 P:6:0:?:test-sysinit.c:269 P:7:0:?:test-sysinit.c:274 P:8:0:?:test-sysinit.c:275 P:9:0:?:test-sysinit.c:280 P:10:0:?:test-sysinit.c:281 P:11:0:?:test-sysinit.c:286 P:12:0:?:test-sysinit.c:287 P:13:0:?:test-sysinit.c:292 P:14:0:?:test-sysinit.c:293 P:15:0:?:test-sysinit.c:298 P:16:0:?:test-sysinit.c:299 P:17:0:?:test-sysinit.c:304 P:18:0:?:test-sysinit.c:305 P:19:0:?:test-sysinit.c:310 P:20:0:?:test-sysinit.c:311 P:21:0:?:test-sysinit.c:316 P:22:0:?:test-sysinit.c:317 P:23:0:?:test-sysinit.c:323 P:24:0:?:test-sysinit.c:328 P:25:0:?:test-sysinit.c:334 P:26:0:?:test-sysinit.c:339 P:27:0:?:test-sysinit.c:344 P:28:0:?:test-sysinit.c:345 P:29:0:?:test-sysinit.c:350 P:30:0:?:test-sysinit.c:351 P:31:0:?:test-sysinit.c:356 P:32:0:?:test-sysinit.c:357 P:33:0:?:test-sysinit.c:362 P:34:0:?:test-sysinit.c:363 P:35:0:?:test-sysinit.c:368 P:36:0:?:test-sysinit.c:369 P:37:0:?:test-sysinit.c:374 P:38:0:?:test-sysinit.c:375 P:39:0:?:test-sysinit.c:380 P:40:0:?:test-sysinit.c:381 P:41:0:?:test-sysinit.c:386 P:42:0:?:test-sysinit.c:387 P:43:0:?:test-sysinit.c:392 P:44:0:?:test-sysinit.c:393 P:45:0:?:test-sysinit.c:398 P:46:0:?:test-sysinit.c:399 P:47:0:?:test-sysinit.c:404 P:48:0:?:test-sysinit.c:405 P:49:0:?:test-sysinit.c:410 P:50:0:?:test-sysinit.c:411 P:51:0:?:test-sysinit.c:416 P:52:0:?:test-sysinit.c:417 P:53:0:?:test-sysinit.c:422 P:54:0:?:test-sysinit.c:423 P:55:0:?:test-sysinit.c:450 P:56:0:?:test-sysinit.c:451 P:57:0:?:test-sysinit.c:456 P:58:0:?:test-sysinit.c:457 P:59:0:?:test-sysinit.c:462 P:60:0:?:test-sysinit.c:463 P:61:0:?:test-sysinit.c:468 P:62:0:?:test-sysinit.c:469 P:63:0:?:test-sysinit.c:474 P:64:0:?:test-sysinit.c:475 P:65:0:?:test-sysinit.c:480 P:66:0:?:test-sysinit.c:481 P:67:0:?:test-sysinit.c:500 P:68:0:?:test-sysinit.c:501 P:69:0:?:test-sysinit.c:506 P:70:0:?:test-sysinit.c:507 P:71:0:?:test-sysinit.c:530 P:72:0:?:test-sysinit.c:531 P:73:0:?:test-sysinit.c:536 P:74:0:?:test-sysinit.c:537 P:75:0:?:test-sysinit.c:516 P:76:0:?:test-sysinit.c:524 P:77:0:?:test-sysinit.c:525 P:78:0:?:test-sysinit.c:542 P:79:0:?:test-sysinit.c:543 P:80:0:IDLE:test-sysinit.c:548 P:81:0:IDLE:test-sysinit.c:549 P:82:0:IDLE:test-sysinit.c:554 P:83:0:IDLE:test-sysinit.c:555 P:84:0:IDLE:test-sysinit.c:560 P:85:0:IDLE:test-sysinit.c:561 P:86:0:IDLE:test-sysinit.c:571 P:87:0:IDLE:test-sysinit.c:572 P:88:0:IDLE:test-sysinit.c:581 P:89:0:IDLE:test-sysinit.c:582 P:90:0:IDLE:test-sysinit.c:591 P:91:0:IDLE:test-sysinit.c:596 P:92:0:IDLE:test-sysinit.c:601 P:93:0:IDLE:test-sysinit.c:602 P:94:0:IDLE:test-sysinit.c:607 P:95:0:IDLE:test-sysinit.c:608 P:96:0:IDLE:test-sysinit.c:614 P:97:0:IDLE:test-sysinit.c:616 P:98:0:IDLE:test-sysinit.c:622 P:99:0:IDLE:test-sysinit.c:624 P:100:0:IDLE:test-sysinit.c:630 P:101:0:IDLE:test-sysinit.c:632 P:102:0:IDLE:test-sysinit.c:638 P:103:0:IDLE:test-sysinit.c:640 P:104:0:IDLE:test-sysinit.c:650 P:105:0:IDLE:test-sysinit.c:651 P:106:0:IDLE:test-sysinit.c:660 P:107:0:IDLE:test-sysinit.c:661 P:108:0:IDLE:test-sysinit.c:664 P:109:0:IDLE:test-sysinit.c:665 P:110:0:IDLE:test-sysinit.c:666 P:111:0:IDLE:test-sysinit.c:667 P:112:0:IDLE:test-sysinit.c:668 P:113:0:IDLE:test-sysinit.c:669 P:114:0:IDLE:test-sysinit.c:670 P:115:0:IDLE:test-sysinit.c:671 P:116:0:IDLE:test-sysinit.c:672 P:117:0:IDLE:test-sysinit.c:673 P:118:0:IDLE:test-sysinit.c:674 P:119:0:IDLE:test-sysinit.c:675 P:120:0:UI1:test-sysinit.c:682 Y:sysinit:N:121:F:0 Z:sysinit:C:1:N:121:F:0 *** FATAL *** fatal source: 5 (RTEMS_FATAL_SOURCE_EXIT) fatal code: 0 (0x) RTEMS version: 5.0.0.9c792752178ce9bfaffec0ae3d2f150d8f01821f RTEMS tools: 7.3.0 20180125 (RTEMS 5, RSB 30da0c720b78eba16a3f5272206c07415368617b, Newlib 2ab57ad59bc35dafffa69cd4da5e228971de069f) executing thread ID: 0x08a010001 executing thread name: UI1 -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG. /* * SPDX-License-Identifier: BSD-2-Clause * * Copyright (C) 2015, 2018 embedded brains GmbH * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions
m68k/mcf5235:Add per-section compilation and linking support (GCI 2018)
Hello , The per-function section linking has been enabled under this patch , I faced permission denied for loopback test which i had fixed by giving "x" attribute to loopback-init.o file . if it happens with you , please enable the permission for this test. and generate a patch which improves this . Thank you Regards --Shashvat 0001-m68k-mcf5235-Add-per-section-compilation-and-linking.patch Description: Binary data ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: psxtests: add POSIX API signature compliance tests for mqueue.h file (GCI 2018)
On Wed, 28 Nov 2018 at 13:38, Himanshu Sekhar Nayak < himanshuwindows...@gmail.com> wrote: > Hi guys, > > Here is the patch file for mqueue.h file. > > I have approved this task in GCI site. > Thanks > Himanshu > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: psxtests: add POSIX API signature compliance tests for mqueue.h file (GCI 2018)
Thanks for approving it Vijay! For the purposes of reviewing psxhdrs tasks, here are the guidelines. This should help everyone. + good commit message including indication work is from GCI 2018 + Build without warnings. Be warned, some POSIX methods require defining a symbol to make the method visible. This is noted in the POSIX standard and Linux man pages. + All methods from the .h file are tested. See http://pubs.opengroup.org/onlinepubs/9699919799/ and click on "headers" on the lower left hand side. All the POSIX header requirements are a click away from there. If the new test uncovers an issue with a header or RTEMS method prototype, discuss it with your mentor and on deve@. This will likely require filing a ticket and developer follow up. It may be an option to commit the tests but comment out the offending test (if it does not compile) in the Makefile.am until it is resolved. Issues uncovered will just have to be dealt with on a case by case basis. Thanks. --joel On Wed, Nov 28, 2018 at 8:11 AM Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > > > > > On Wed, 28 Nov 2018 at 13:38, Himanshu Sekhar Nayak < > himanshuwindows...@gmail.com> wrote: > >> Hi guys, >> >> Here is the patch file for mqueue.h file. >> >> I have approved this task in GCI site. > >> Thanks >> Himanshu >> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: m68k/mcf5235:Add per-section compilation and linking support (GCI 2018)
On Wed, Nov 28, 2018 at 7:29 AM Shashvat Jain wrote: > Hello , > The per-function section linking has been enabled under this patch > , I faced permission denied for loopback test which i had fixed by giving > "x" attribute to loopback-init.o file . > if it happens with you , please enable the permission for this test. > and generate a patch which improves this . > Committed. I don't know why you are seeing the x attribute on the init.o. Is this still on MSYS2 or Linux? --joel > > Thank you > Regards > > --Shashvat > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
m68k/mcf5329:Add per-section compilation and linking support (GCI 2018)
Hello , The per-function section linking has been enabled under this patch. Thank you Regards --Shashvat 0001-m68k-mcf5329-Add-per-section-compilation-and-linking.patch Description: Binary data ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: m68k/mcf5329:Add per-section compilation and linking support (GCI 2018)
This one is pushed. Thank you. I am not sure why but I am seeing much larger drops in size. Perhaps msys2 doesn't support something need for the function section linking to do its magic. before]$ m68k-rtems5-size `find . -name ticker.exe` textdata bss dec hex filename 904061184 12000 103590 194a6 ./m68k-rtems5/c/mcf5329/testsuites/samples/ticker.exe ]$ m68k-rtems5-size `find . -name ticker.exe` textdata bss dec hex filename 6397411369984 75094 12556 ./m68k-rtems5/c/mcf5329/testsuites/samples/ticker.exe That's quite different from what your commit message indicates you saw. On Wed, Nov 28, 2018 at 12:36 PM Shashvat Jain wrote: > Hello , > The per-function section linking has been enabled under this patch. > > Thank you > Regards > > --Shashvat > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
m68k/mcf52235:Add per-section compilation and linking support (GCI 2018)
Hello , The per-function section linking has been enabled under this patch. Thank you Regards 0001-m68k-mcf52235-Add-per-section-compilation-and-linkin.patch Description: Binary data ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
m68k/mcf5225x:Add per-section compilation and linking support (GCI 2018)
Hello , The per-function section linking has been enabled under this patch. Drops have been recorded , keeping in mind the host is MSYS2 linux will tend to give a different story , concerning with higher drops. Thank you Regards 0001-m68k-mcf5225x-Add-per-section-compilation-and-linkin.patch Description: Binary data ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS Software Engineering Handbook
Hi Scott Zemerick of NASA IV&V did a review of NASA's quality standard and DO-178B and tried to find a way for open source projects to provide documents meeting the spirit and intent of those standards in a way that is palatable and not soul crushing for an open source project. He presented about this at the Flight Software Workshop last year. The title was "Open-Source RTOS Space Qualification: an RTEMS Case Study" Presentation: http://flightsoftware.jhuapl.edu/files/2017/Day-3/06-Zemerick-RTOS-Qualification.pptx Video of presentation: https://youtu.be/UYJqABg2Mzk Scott suggested an outline which takes existing content and puts it into a structure that an IV&V person would recognize. It also moves content from the Wiki into Rest which is much better for long-term controlled maintenance and organization. Plus prettier. Scott's outline and info is at https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/. For example, the Coding Style, Licensing Requirements, git instructions, project policies, etc. should be in here. Other topics are up for discussion. I took his outline with URLs and converted it to Rest. I left TBDs for the wiki pages to convert and insert. I also left TBDs for things to write. I am going to write Google Code-In tasks for the conversion. The current Rest code is in my rtems-docs git repo git:// git.rtems.org/joel/rtems-docs.git on the sw_eng_hb branch. The current formatted version (as is) is at https://ftp.rtems.org/pub/rtems/people/joel/docs-eng/ This is a solid starting point to having some of the documentation required by high integrity processes. We can grow it. Obviously this is a starting point and I am hoping that in the remaining two weeks of GCI we can get the wiki pages converted. At some point in the near future, I hope to submit it for inclusion in the main rtems documentation set. Please pitch in and let's make this happen. Improving our processes and supporting documentation is important. Thanks --joel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: m68k/mcf5225x:Add per-section compilation and linking support (GCI 2018)
patch merged and GCI task closed. Thank you! --joel On Wed, Nov 28, 2018 at 6:48 PM Shashvat Jain wrote: > Hello , > The per-function section linking has been enabled under this patch. > Drops have been recorded , keeping in mind the host is MSYS2 > linux will tend to give a different story , concerning with higher drops. > Thank you > Regards > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Software Engineering Handbook
Scott has done a awesome job , would love to do the task : ) On Thu, Nov 29, 2018 at 6:22 AM Joel Sherrill wrote: > Hi > > Scott Zemerick of NASA IV&V did a review of NASA's quality standard and > DO-178B and tried to find a way for open source projects to provide > documents meeting the spirit and intent of those standards in a way that is > palatable and not soul crushing for an open source project. He presented > about this at the Flight Software Workshop last year. The title was > "Open-Source RTOS Space Qualification: an RTEMS Case Study" > > Presentation: > http://flightsoftware.jhuapl.edu/files/2017/Day-3/06-Zemerick-RTOS-Qualification.pptx > Video of presentation: https://youtu.be/UYJqABg2Mzk > > Scott suggested an outline which takes existing content and puts it into a > structure that an IV&V person would recognize. It also moves content from > the Wiki into Rest which is much better for long-term controlled > maintenance and organization. Plus prettier. Scott's outline and info is at > https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/. > > For example, the Coding Style, Licensing Requirements, git instructions, > project policies, etc. should be in here. Other topics are up for > discussion. > > I took his outline with URLs and converted it to Rest. I left TBDs for the > wiki pages to convert and insert. I also left TBDs for things to write. I > am going to write Google Code-In tasks for the conversion. The current > Rest code is in my rtems-docs git repo git:// > git.rtems.org/joel/rtems-docs.git on the sw_eng_hb branch. The current > formatted version (as is) is at > https://ftp.rtems.org/pub/rtems/people/joel/docs-eng/ > > This is a solid starting point to having some of the documentation > required by high integrity processes. We can grow it. > > Obviously this is a starting point and I am hoping that in the remaining > two weeks of GCI we can get the wiki pages converted. At some point in the > near future, I hope to submit it for inclusion in the main rtems > documentation set. > > Please pitch in and let's make this happen. Improving our processes and > supporting documentation is important. > > Thanks > > --joel > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Software Engineering Handbook
:) Look through what I got converted. The potential tasks should be pretty obvious. If not, I didn't do what I think I did. I will review the doc for GCI tasks tomorrow and Gedare and I will try to get them published. On Wed, Nov 28, 2018 at 7:00 PM Shashvat Jain wrote: > Scott has done a awesome job , would love to do the task : ) > > > > On Thu, Nov 29, 2018 at 6:22 AM Joel Sherrill wrote: > >> Hi >> >> Scott Zemerick of NASA IV&V did a review of NASA's quality standard and >> DO-178B and tried to find a way for open source projects to provide >> documents meeting the spirit and intent of those standards in a way that is >> palatable and not soul crushing for an open source project. He presented >> about this at the Flight Software Workshop last year. The title was >> "Open-Source RTOS Space Qualification: an RTEMS Case Study" >> >> Presentation: >> http://flightsoftware.jhuapl.edu/files/2017/Day-3/06-Zemerick-RTOS-Qualification.pptx >> Video of presentation: https://youtu.be/UYJqABg2Mzk >> >> Scott suggested an outline which takes existing content and puts it into >> a structure that an IV&V person would recognize. It also moves content from >> the Wiki into Rest which is much better for long-term controlled >> maintenance and organization. Plus prettier. Scott's outline and info is at >> https://ftp.rtems.org/pub/rtems/people/joel/sw_eng_hb/. >> >> For example, the Coding Style, Licensing Requirements, git instructions, >> project policies, etc. should be in here. Other topics are up for >> discussion. >> >> I took his outline with URLs and converted it to Rest. I left TBDs for >> the wiki pages to convert and insert. I also left TBDs for things to >> write. I am going to write Google Code-In tasks for the conversion. The >> current Rest code is in my rtems-docs git repo git:// >> git.rtems.org/joel/rtems-docs.git on the sw_eng_hb branch. The current >> formatted version (as is) is at >> https://ftp.rtems.org/pub/rtems/people/joel/docs-eng/ >> >> This is a solid starting point to having some of the documentation >> required by high integrity processes. We can grow it. >> >> Obviously this is a starting point and I am hoping that in the remaining >> two weeks of GCI we can get the wiki pages converted. At some point in the >> near future, I hope to submit it for inclusion in the main rtems >> documentation set. >> >> Please pitch in and let's make this happen. Improving our processes and >> supporting documentation is important. >> >> Thanks >> >> --joel >> >> ___ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: m68k/mcf52235:Add per-section compilation and linking support (GCI 2018)
ping On Thu, Nov 29, 2018 at 6:13 AM Shashvat Jain wrote: > Hello , > The per-function section linking has been enabled under this patch. > > Thank you > Regards > ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
