Re: [PATCH] c-user: Use new template for feature config opts

[Sebastian Huber]

On 18/03/2020 16:52, Sebastian Huber wrote:


Try to bring all descriptions up to date.  Add cross-references to
several options.

Update #3900.


I checked in a slightly updated patch. I added a new option type 
"feature-enable" to produce a standard text for the default configuration:


https://git.rtems.org/sebh/rtems-qual.git/commit/?id=f85bb0bbaece4c3be58d3b023fd4d118e2c59030

A good example for the new template is here:

https://docs.rtems.org/branches/master/c-user/config/event-record.html

I will work now on an update of the integer type configuration options:

https://devel.rtems.org/ticket/3901

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

GSOC 2020 Project Proposal - POSIX Compliance

[Eshan Dhawan]

Hello Everyone,
I have completed the first draft for my GSOC 2020 proposal on POSIX
Compliance. I have tried to implement every suggestion given to the draft
by the community.
I would like everyone to provide feedback on the project proposal. Also,
tell if the project has enough work to be a gsoc project or there is a need
to add more tasks.

proposal link: POSIX Compliance proposal

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 16/16] This patch provides usage of RTEMS cross-compiler over GCC cross-compiler

[utkarsh.ra...@gmail.com]

---
 user/start/tools.rst | 35 +--
 1 file changed, 25 insertions(+), 10 deletions(-)

diff --git a/user/start/tools.rst b/user/start/tools.rst
index 92e99c8..3a6da3a 100644
--- a/user/start/tools.rst
+++ b/user/start/tools.rst
@@ -79,17 +79,32 @@ Add ``--verbose`` to the GCC command for the the verbose 
version details.
 
 Need for RTEMS-Specific Cross-Compiler
 
-  New users are often confused as to why they can't use their distribution's 
cross-compiler for their target on rtems, e.g.,the riscv64-linux-gnu or the 
arm-none-eabi-gcc. Below mentioned are some of the reasons for using the RTEMS 
cross-compiler.
 
- ``Correct configuration of newlib`` -
-Newlib is a C standard library implementation intended for use on embedded 
systems. Most of the POSIX and libc support for RTEMS is derived from newlib. 
The RTEMS cross-compiler configures newlib correctly for RTEMS.
+New users are often confused as to why they can't use their distribution's
+cross-compiler for their target on rtems, e.g.,the riscv64-linux-gnu or the
+arm-none-eabi-gcc. Below mentioned are some of the reasons for using the RTEMS
+cross-compiler.
 
- ``Threading in GCC support libraries`` -
-GCC support threading libraries such as ``pthread.h`` provide threading 
support to an application; these libraries are tailored according to RTEMS 
using the RTEMS cross-compiler.
-   
- ``Provide preprocessor define __rtems__`` -
-The ``__rtems__`` preprocessor define is used to provide conditional code 
compilation in source files that are shared with other projects e.g. in newlib 
or imported code from freebsd.
+ ``Correct configuration of newlib`` - 
+ Newlib is a C standard library implementation intended for use on embedded
+ systems. Most of the POSIX and libc support for RTEMS is derived from newlib.
+ The RTEMS cross-compiler configures newlib correctly for RTEMS.
 
- ``Multilib variants to match the BSP``-
-RTEMS configures GCC to create separate runtime libraries for each 
supported instruction set, floating point unit, vector unit, word size (e.g. 
32-bit and 64-bit), endianness, ABI, processor errata workarounds,and so on in 
the architecture. These libraries are termed multilib variants. Multilibs 
variants to match the BSP are set by selecting a specific set of machine 
options using the RTEMS cross-compiler.
+ ``Threading in GCC support libraries`` - 
+ GCC support threading libraries such as ``pthread.h`` provide threading 
support
+ to an application; these libraries are tailored according to RTEMS using the
+ RTEMS cross-compiler.
+   
+ ``Provide preprocessor define __rtems__`` - 
+ The ``__rtems__`` preprocessor define is used to provide conditional code
+ compilation in source files that are shared with other projects e.g. in newlib
+ or imported code from freebsd.
+
+ ``Multilib variants to match the BSP``- 
+ RTEMS configures GCC to create separate runtime libraries for each supported
+ instruction set, floating point unit, vector unit, word size (e.g. 32-bit and
+ 64-bit), endianness, ABI, processor errata workarounds,and so on in the
+ architecture. These libraries are termed multilib variants. Multilibs variants
+ to match the BSP are set by selecting a specific set of machine options using
+ the RTEMS cross-compiler.
 
-- 
2.17.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-littlevgl PATCH] Add README

[Vijay Kumar Banerjee]

On Tue, Mar 24, 2020, 1:55 AM Gedare Bloom  wrote:

> Please add the maintainer info for the package, and/or devel@rtems.org
> for questions (just in case someone picks this up somehow without
> RTEMS!)
>
Thanks for the review.
I'll add that in v2 once I get the @rtems address ;)

Will it be possible to also host it on GitHub?

>
> On Mon, Mar 23, 2020 at 12:44 PM Vijay Kumar Banerjee
>  wrote:
> >
> > ---
> >  README.md | 34 ++
> >  1 file changed, 34 insertions(+)
> >  create mode 100644 README.md
> >
> > diff --git a/README.md b/README.md
> > new file mode 100644
> > index 000..161e4d9
> > --- /dev/null
> > +++ b/README.md
> > @@ -0,0 +1,34 @@
> > +RTEMS LittlevGL
> > +===
> > +
> > +Welcome to RTEMS LittlevGL (lvgl). This package builds the lvgl library
> using
> > +waf with the required settings for running it with rtems. The lvgl
> drivers are
> > +adapted to the BSD framebuffer and hence requires the latest
> rtems-libbsd build.
> > +
> > +About LittlevGL
> > +---
> > +
> > +LittlevGL is a lightweight graphics library for embedded GUI
> applications. It
> > +can be configured using the `lv_conf.h` and the `lv_drv_conf.h` files
> that are
> > +in the top of the rtems-littlevgl directory.
> > +
> > +The documentation is available at:
> > +https://docs.littlevgl.com/en/html/index.html
> > +
> > +Building and installing rtems-littlevgl
> > +---
> > +
> > +```
> > +git clone git://git.rtems.org/packages/rtems-littlevgl.git
> > +git submodule update
> > +./waf configure --prefix=/path/to/rtems/5
> > +./waf build install
> > +```
> > +
> > +Writing embedded GUI app using rtems-littlevgl
> > +--
> > +
> > +The rtems-examples repository has a sample lvgl hello world application
> that can
> > +be followed for reference on how to write and build an application with
> lvgl.
> > +The sample app can be found here:
> > +https://git.rtems.org/rtems-examples/tree/lvgl/hello/test.c
> > --
> > 2.21.1
> >
> > ___
> > 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: [PATCH 16/16] This patch provides usage of RTEMS cross-compiler over GCC cross-compiler

[Gedare Bloom]

Hi Utkarsh,

Please squash/fixup your patches to send a patch (set) that modifies
the existing repository.

For more, read about "git rebase interactive" mode.

Thanks,
Gedare

On Tue, Mar 24, 2020 at 4:21 AM utkarsh.ra...@gmail.com
 wrote:
>
> ---
>  user/start/tools.rst | 35 +--
>  1 file changed, 25 insertions(+), 10 deletions(-)
>
> diff --git a/user/start/tools.rst b/user/start/tools.rst
> index 92e99c8..3a6da3a 100644
> --- a/user/start/tools.rst
> +++ b/user/start/tools.rst
> @@ -79,17 +79,32 @@ Add ``--verbose`` to the GCC command for the the verbose 
> version details.
>
>  Need for RTEMS-Specific Cross-Compiler
>  
> -  New users are often confused as to why they can't use their distribution's 
> cross-compiler for their target on rtems, e.g.,the riscv64-linux-gnu or the 
> arm-none-eabi-gcc. Below mentioned are some of the reasons for using the 
> RTEMS cross-compiler.
>
> - ``Correct configuration of newlib`` -
> -Newlib is a C standard library implementation intended for use on 
> embedded systems. Most of the POSIX and libc support for RTEMS is derived 
> from newlib. The RTEMS cross-compiler configures newlib correctly for RTEMS.
> +New users are often confused as to why they can't use their distribution's
> +cross-compiler for their target on rtems, e.g.,the riscv64-linux-gnu or the
> +arm-none-eabi-gcc. Below mentioned are some of the reasons for using the 
> RTEMS
> +cross-compiler.
>
> - ``Threading in GCC support libraries`` -
> -GCC support threading libraries such as ``pthread.h`` provide threading 
> support to an application; these libraries are tailored according to RTEMS 
> using the RTEMS cross-compiler.
> -
> - ``Provide preprocessor define __rtems__`` -
> -The ``__rtems__`` preprocessor define is used to provide conditional 
> code compilation in source files that are shared with other projects e.g. in 
> newlib or imported code from freebsd.
> + ``Correct configuration of newlib`` -
> + Newlib is a C standard library implementation intended for use on embedded
> + systems. Most of the POSIX and libc support for RTEMS is derived from 
> newlib.
> + The RTEMS cross-compiler configures newlib correctly for RTEMS.
>
> - ``Multilib variants to match the BSP``-
> -RTEMS configures GCC to create separate runtime libraries for each 
> supported instruction set, floating point unit, vector unit, word size (e.g. 
> 32-bit and 64-bit), endianness, ABI, processor errata workarounds,and so on 
> in the architecture. These libraries are termed multilib variants. Multilibs 
> variants to match the BSP are set by selecting a specific set of machine 
> options using the RTEMS cross-compiler.
> + ``Threading in GCC support libraries`` -
> + GCC support threading libraries such as ``pthread.h`` provide threading 
> support
> + to an application; these libraries are tailored according to RTEMS using the
> + RTEMS cross-compiler.
> +
> + ``Provide preprocessor define __rtems__`` -
> + The ``__rtems__`` preprocessor define is used to provide conditional code
> + compilation in source files that are shared with other projects e.g. in 
> newlib
> + or imported code from freebsd.
> +
> + ``Multilib variants to match the BSP``-
> + RTEMS configures GCC to create separate runtime libraries for each supported
> + instruction set, floating point unit, vector unit, word size (e.g. 32-bit 
> and
> + 64-bit), endianness, ABI, processor errata workarounds,and so on in the
> + architecture. These libraries are termed multilib variants. Multilibs 
> variants
> + to match the BSP are set by selecting a specific set of machine options 
> using
> + the RTEMS cross-compiler.
>
> --
> 2.17.1
>
> ___
> 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-littlevgl PATCH] Add README

[Gedare Bloom]

On Tue, Mar 24, 2020 at 6:22 AM Vijay Kumar Banerjee
 wrote:
>
>
>
> On Tue, Mar 24, 2020, 1:55 AM Gedare Bloom  wrote:
>>
>> Please add the maintainer info for the package, and/or devel@rtems.org
>> for questions (just in case someone picks this up somehow without
>> RTEMS!)
>
> Thanks for the review.
> I'll add that in v2 once I get the @rtems address ;)
>
> Will it be possible to also host it on GitHub?

Yes, talk to Amar about getting that set up, too.

>>
>>
>> On Mon, Mar 23, 2020 at 12:44 PM Vijay Kumar Banerjee
>>  wrote:
>> >
>> > ---
>> >  README.md | 34 ++
>> >  1 file changed, 34 insertions(+)
>> >  create mode 100644 README.md
>> >
>> > diff --git a/README.md b/README.md
>> > new file mode 100644
>> > index 000..161e4d9
>> > --- /dev/null
>> > +++ b/README.md
>> > @@ -0,0 +1,34 @@
>> > +RTEMS LittlevGL
>> > +===
>> > +
>> > +Welcome to RTEMS LittlevGL (lvgl). This package builds the lvgl library 
>> > using
>> > +waf with the required settings for running it with rtems. The lvgl 
>> > drivers are
>> > +adapted to the BSD framebuffer and hence requires the latest rtems-libbsd 
>> > build.
>> > +
>> > +About LittlevGL
>> > +---
>> > +
>> > +LittlevGL is a lightweight graphics library for embedded GUI 
>> > applications. It
>> > +can be configured using the `lv_conf.h` and the `lv_drv_conf.h` files 
>> > that are
>> > +in the top of the rtems-littlevgl directory.
>> > +
>> > +The documentation is available at:
>> > +https://docs.littlevgl.com/en/html/index.html
>> > +
>> > +Building and installing rtems-littlevgl
>> > +---
>> > +
>> > +```
>> > +git clone git://git.rtems.org/packages/rtems-littlevgl.git
>> > +git submodule update
>> > +./waf configure --prefix=/path/to/rtems/5
>> > +./waf build install
>> > +```
>> > +
>> > +Writing embedded GUI app using rtems-littlevgl
>> > +--
>> > +
>> > +The rtems-examples repository has a sample lvgl hello world application 
>> > that can
>> > +be followed for reference on how to write and build an application with 
>> > lvgl.
>> > +The sample app can be found here:
>> > +https://git.rtems.org/rtems-examples/tree/lvgl/hello/test.c
>> > --
>> > 2.21.1
>> >
>> > ___
>> > 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

[rtems-littlevgl PATCH v2 1/2] Add README

[Vijay Kumar Banerjee]

---
 README.md | 47 +++
 1 file changed, 47 insertions(+)
 create mode 100644 README.md

diff --git a/README.md b/README.md
new file mode 100644
index 000..d0e7b02
--- /dev/null
+++ b/README.md
@@ -0,0 +1,47 @@
+RTEMS LittlevGL
+===
+
+Welcome to RTEMS LittlevGL (lvgl). This package builds the lvgl library using
+waf with the required settings for running it with rtems. The lvgl drivers are
+adapted to the BSD framebuffer and hence requires the latest rtems-libbsd 
build.
+
+About LittlevGL
+---
+
+LittlevGL is a lightweight graphics library for embedded GUI applications. It
+can be configured using the `lv_conf.h` and the `lv_drv_conf.h` files that are
+in the top of the rtems-littlevgl directory.
+
+The documentation is available at:
+https://docs.littlevgl.com/en/html/index.html
+
+Building and installing rtems-littlevgl
+---
+
+```
+git clone git://git.rtems.org/packages/rtems-littlevgl.git
+git submodule update
+./waf configure --prefix=/path/to/rtems/5
+./waf build install
+```
+
+Writing embedded GUI app using rtems-littlevgl
+--
+
+The rtems-examples repository has a sample lvgl hello world application that 
can +be followed for reference on how to write and build an application with 
lvgl.
+The sample app can be found here:
+https://git.rtems.org/rtems-examples/tree/lvgl/hello/test.c
+
+Where to discuss questions and ideas?
+-
+
+The preferred way of carrying out any discussions or questions is to reach out
+to the users mailing list us...@rtems.org or the devel mailing list
+devel@rtems.org for more detailed discussions.
+
+In any discussions related to rtems-littlevgl, the maintainers can be CC'd by
+their respective id's given below:
+
+Christian Mauderer (christian.maude...@embedded-brains.de)
+Vijay Kumar Banerjee (vi...@rtems.org)
-- 
2.21.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[rtems-littlevgl PATCH v2 2/2] Update lv_drivers

[Vijay Kumar Banerjee]

---
 lv_drivers | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lv_drivers b/lv_drivers
index 24cedaa..ae69299 16
--- a/lv_drivers
+++ b/lv_drivers
@@ -1 +1 @@
-Subproject commit 24cedaa756b83c50c36f4aa0c625fcdfba89431b
+Subproject commit ae69299c1fadb459d0438575d285f1ccf95bc8e6
-- 
2.21.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-littlevgl PATCH v2 1/2] Add README

[Gedare Bloom]

On Tue, Mar 24, 2020 at 1:09 PM Vijay Kumar Banerjee  wrote:
>
> ---
>  README.md | 47 +++
>  1 file changed, 47 insertions(+)
>  create mode 100644 README.md
>
> diff --git a/README.md b/README.md
> new file mode 100644
> index 000..d0e7b02
> --- /dev/null
> +++ b/README.md
> @@ -0,0 +1,47 @@
> +RTEMS LittlevGL
> +===
> +
> +Welcome to RTEMS LittlevGL (lvgl). This package builds the lvgl library using
> +waf with the required settings for running it with rtems. The lvgl drivers 
> are
> +adapted to the BSD framebuffer and hence requires the latest rtems-libbsd 
> build.
> +
> +About LittlevGL
> +---
> +
> +LittlevGL is a lightweight graphics library for embedded GUI applications. It
> +can be configured using the `lv_conf.h` and the `lv_drv_conf.h` files that 
> are
> +in the top of the rtems-littlevgl directory.
> +
> +The documentation is available at:
> +https://docs.littlevgl.com/en/html/index.html
> +
> +Building and installing rtems-littlevgl
> +---
> +
> +```
> +git clone git://git.rtems.org/packages/rtems-littlevgl.git
> +git submodule update
> +./waf configure --prefix=/path/to/rtems/5
> +./waf build install
> +```
> +
> +Writing embedded GUI app using rtems-littlevgl
> +--
> +
> +The rtems-examples repository has a sample lvgl hello world application that 
> can +be followed for reference on how to write and build an application with 
> lvgl.
something weird happened here?

fix and push

> +The sample app can be found here:
> +https://git.rtems.org/rtems-examples/tree/lvgl/hello/test.c
> +
> +Where to discuss questions and ideas?
> +-
> +
> +The preferred way of carrying out any discussions or questions is to reach 
> out
> +to the users mailing list us...@rtems.org or the devel mailing list
> +devel@rtems.org for more detailed discussions.
> +
> +In any discussions related to rtems-littlevgl, the maintainers can be CC'd by
> +their respective id's given below:
> +
> +Christian Mauderer (christian.maude...@embedded-brains.de)
> +Vijay Kumar Banerjee (vi...@rtems.org)
> --
> 2.21.1
>
> ___
> 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

[PATCH] MAINTAINERS: Add myself to Write After Approval

[Vijay Kumar Banerjee]

---
 MAINTAINERS | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 437b55418b..29e22357a5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -52,6 +52,7 @@ Pavel Pisa pp...@pikron.com
 Christian Mauderer christian.maude...@embedded-brains.de
 Hesham Almataryheshamelmat...@gmail.com
 Amaan Cheval   am...@rtems.org
+Vijay Kumar Banerjee   vi...@rtems.org
 
 Localized Write Permission
 ==
@@ -60,4 +61,5 @@ beagle Ben Gras (b...@rtems.org)
 tms570 Pavel Pisa (p...@cmp.felk.cvut.cz)
 raspberrypiPavel Pisa (p...@cmp.felk.cvut.cz)
 x86_64 Amaan Cheval (am...@rtems.org)
+beagle Vijay Kumar Banerjee (vi...@rtems.org)
 
-- 
2.21.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-littlevgl PATCH v2 1/2] Add README

[Vijay Kumar Banerjee]

On Wed, Mar 25, 2020 at 12:59 AM Gedare Bloom  wrote:

> On Tue, Mar 24, 2020 at 1:09 PM Vijay Kumar Banerjee 
> wrote:
> >
> > ---
> >  README.md | 47 +++
> >  1 file changed, 47 insertions(+)
> >  create mode 100644 README.md
> >
> > diff --git a/README.md b/README.md
> > new file mode 100644
> > index 000..d0e7b02
> > --- /dev/null
> > +++ b/README.md
> > @@ -0,0 +1,47 @@
> > +RTEMS LittlevGL
> > +===
> > +
> > +Welcome to RTEMS LittlevGL (lvgl). This package builds the lvgl library
> using
> > +waf with the required settings for running it with rtems. The lvgl
> drivers are
> > +adapted to the BSD framebuffer and hence requires the latest
> rtems-libbsd build.
> > +
> > +About LittlevGL
> > +---
> > +
> > +LittlevGL is a lightweight graphics library for embedded GUI
> applications. It
> > +can be configured using the `lv_conf.h` and the `lv_drv_conf.h` files
> that are
> > +in the top of the rtems-littlevgl directory.
> > +
> > +The documentation is available at:
> > +https://docs.littlevgl.com/en/html/index.html
> > +
> > +Building and installing rtems-littlevgl
> > +---
> > +
> > +```
> > +git clone git://git.rtems.org/packages/rtems-littlevgl.git
> > +git submodule update
> > +./waf configure --prefix=/path/to/rtems/5
> > +./waf build install
> > +```
> > +
> > +Writing embedded GUI app using rtems-littlevgl
> > +--
> > +
> > +The rtems-examples repository has a sample lvgl hello world application
> that can +be followed for reference on how to write and build an
> application with lvgl.
> something weird happened here?
>
> fix and push
>
> Pushed!
https://git.rtems.org/packages/rtems-littlevgl/commit/?id=9135baf7d2591a907740f30d5ecffb3e77d1f1be


> > +The sample app can be found here:
> > +https://git.rtems.org/rtems-examples/tree/lvgl/hello/test.c
> > +
> > +Where to discuss questions and ideas?
> > +-
> > +
> > +The preferred way of carrying out any discussions or questions is to
> reach out
> > +to the users mailing list us...@rtems.org or the devel mailing list
> > +devel@rtems.org for more detailed discussions.
> > +
> > +In any discussions related to rtems-littlevgl, the maintainers can be
> CC'd by
> > +their respective id's given below:
> > +
> > +Christian Mauderer (christian.maude...@embedded-brains.de)
> > +Vijay Kumar Banerjee (vi...@rtems.org)
> > --
> > 2.21.1
> >
> > ___
> > 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

discussion related to source for porting headers and methods to RTEMS and newlib

[Eshan Dhawan]

Hello everyone,
I have identified sources to port headers and methods to RTEMS and Newlib.
I have given priority to FreeBSD for the choice of source. But method not
present in FreeBSD can be ported from alternative sources like NetBSD and
musl.

-> Missing methods of math.h: I have compiled a list of methods and their
sources. Some need to be implemented from scratch.
list: Math.h missing functions


-> sys/ipc.h: This header and its function can be ported from FreeBSD.
ipc.h : https://github.com/freebsd/freebsd/blob/master/sys/sys/ipc.h
ftok.c: https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/ftok.c

->fmtmsg.h: its implementation is also present in FreeBSD.
https://github.com/freebsd/freebsd/blob/master/include/fmtmsg.h
https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/fmtmsg.c


->spawn.h: Its implementation is in FreeBSD.
https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/posix_spawn.c

-> pselect() from  : its implementation is also from FreeBSD
https://github.com/freebsd/freebsd/blob/master/lib/libc/sys/pselect.c

-> confstr() from : Its implementation is from FreeBSD
https://github.com/udp/freebsd-libc/blob/master/gen/confstr.c.

I would like everyone to review it and provide your suggestions.

Thanks
-Eshan
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

discussion related to implementation of File descriptor functions in RTEMS

[Eshan Dhawan]

Hello everyone,
As @Vaibhav Gupta  suggested I have also added
adding file descriptor functions to my GSOC project.
I went through the mailing list archives for more information.
RTEMS as its own file descriptor so the functions need to be implemented
from scratch.
I wanted to get more information related to it.

thanks
-Eshan
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: discussion related to implementation of File descriptor functions in RTEMS

[Joel Sherrill]

On Tue, Mar 24, 2020 at 4:57 PM Eshan Dhawan 
wrote:

> Hello everyone,
> As @Vaibhav Gupta  suggested I have also added
> adding file descriptor functions to my GSOC project.
> I went through the mailing list archives for more information.
> RTEMS as its own file descriptor so the functions need to be implemented
> from scratch.
> I wanted to get more information related to it.
>

What's the set of functions you are proposing for those not tracking your
draft proposal?

>
> thanks
> -Eshan
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: discussion related to source for porting headers and methods to RTEMS and newlib

[Gedare Bloom]

email subject can be shortened. almost everything is a discussion :)

On Tue, Mar 24, 2020 at 3:49 PM Eshan Dhawan  wrote:
>
> Hello everyone,
> I have identified sources to port headers and methods to RTEMS and Newlib. I 
> have given priority to FreeBSD for the choice of source. But method not 
> present in FreeBSD can be ported from alternative sources like NetBSD and 
> musl.
>
Considering the simplicity, you may want to compare musl vs freebsd as well.

> -> Missing methods of math.h: I have compiled a list of methods and their 
> sources. Some need to be implemented from scratch.
> list: Math.h missing functions
>
> -> sys/ipc.h: This header and its function can be ported from FreeBSD.
> ipc.h : https://github.com/freebsd/freebsd/blob/master/sys/sys/ipc.h
> ftok.c: https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/ftok.c
>
> ->fmtmsg.h: its implementation is also present in FreeBSD.
> https://github.com/freebsd/freebsd/blob/master/include/fmtmsg.h
> https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/fmtmsg.c
>
> ->spawn.h: Its implementation is in FreeBSD.
> https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/posix_spawn.c
>
I'm worried about the large number of includes there. It may easily
lead you to trouble chasing down transitive include headers, like what
happened with Vaibhav before with search.h support.

> -> pselect() from  : its implementation is also from FreeBSD
> https://github.com/freebsd/freebsd/blob/master/lib/libc/sys/pselect.c
>
> -> confstr() from : Its implementation is from FreeBSD
> https://github.com/udp/freebsd-libc/blob/master/gen/confstr.c.
>
> I would like everyone to review it and provide your suggestions.
>
include details in your proposal also.

> Thanks
> -Eshan
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: discussion related to implementation of File descriptor functions in RTEMS

[Gedare Bloom]

On Tue, Mar 24, 2020 at 3:57 PM Eshan Dhawan  wrote:
>
> Hello everyone,
> As @Vaibhav Gupta suggested I have also added adding file descriptor 
> functions to my GSOC project.
> I went through the mailing list archives for more information.
> RTEMS as its own file descriptor so the functions need to be implemented from 
> scratch.
> I wanted to get more information related to it.
>
Start here: https://docs.rtems.org/branches/master/filesystem/index.html

And ask questions.

> thanks
> -Eshan
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: discussion related to source for porting headers and methods to RTEMS and newlib

[Joel Sherrill]

On Tue, Mar 24, 2020 at 5:33 PM Gedare Bloom  wrote:

> email subject can be shortened. almost everything is a discussion :)
>
> On Tue, Mar 24, 2020 at 3:49 PM Eshan Dhawan 
> wrote:
> >
> > Hello everyone,
> > I have identified sources to port headers and methods to RTEMS and
> Newlib. I have given priority to FreeBSD for the choice of source. But
> method not present in FreeBSD can be ported from alternative sources like
> NetBSD and musl.
> >
> Considering the simplicity, you may want to compare musl vs freebsd as
> well.
>
> > -> Missing methods of math.h: I have compiled a list of methods and
> their sources. Some need to be implemented from scratch.
> > list: Math.h missing functions
> >
> > -> sys/ipc.h: This header and its function can be ported from FreeBSD.
> > ipc.h : https://github.com/freebsd/freebsd/blob/master/sys/sys/ipc.h
> > ftok.c:
> https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/ftok.c


sys/ipc.h has a lot in it. If you head down the path of adding sys/ipc.h,
you need to evaluate what else is in the file.

Adding support for the System V style SHM, Semaphores, or Message Queues is
possible (I think) but is definitely harder than the likely value to the
community.

>
> >
> > ->fmtmsg.h: its implementation is also present in FreeBSD.
> > https://github.com/freebsd/freebsd/blob/master/include/fmtmsg.h
> > https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/fmtmsg.c


By my recollection, this would be a discrete thing to add to Newlib.


>
> >
> > ->spawn.h: Its implementation is in FreeBSD.
> >
> https://github.com/freebsd/freebsd/blob/master/lib/libc/gen/posix_spawn.c
> >
> I'm worried about the large number of includes there. It may easily
> lead you to trouble chasing down transitive include headers, like what
> happened with Vaibhav before with search.h support.
>

posix_spawn() cannot be supported by RTEMS. It is a new safer way to do
fork/exec. Don't spent any time on this. It will never work on RTEMS.

It is also a HUGE amount of methods and constants. :(

>
> > -> pselect() from  : its implementation is also from
> FreeBSD
> > https://github.com/freebsd/freebsd/blob/master/lib/libc/sys/pselect.c


This would be added to rtems-libbsd. There may be specific technical
challenges
why it is not present. Or it could just be an oversight.


>
> >
> > -> confstr() from : Its implementation is from FreeBSD
> > https://github.com/udp/freebsd-libc/blob/master/gen/confstr.c.
>

The implementation of this would go in RTEMS.

It is possible that the FreeBSD code is a guide but this cannot be a direct
copy to port. Each value defined by POSIX as fetchable must be properly
defined for RTEMS. You would need to make a table of all the "names"
that can be looked up in your proposal.

FWIW I think the FreeBSD version is more right than wrong for RTEMS
but it can't be 100% right and needs analysis.

>
> > I would like everyone to review it and provide your suggestions.
> >
> include details in your proposal also.
>

+1

>
> > Thanks
> > -Eshan
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: discussion related to implementation of File descriptor functions in RTEMS

[Eshan Dhawan]

On Wed, Mar 25, 2020 at 4:01 AM Joel Sherrill  wrote:

>
>
> On Tue, Mar 24, 2020 at 4:57 PM Eshan Dhawan 
> wrote:
>
>> Hello everyone,
>> As @Vaibhav Gupta  suggested I have also
>> added adding file descriptor functions to my GSOC project.
>> I went through the mailing list archives for more information.
>> RTEMS as its own file descriptor so the functions need to be implemented
>> from scratch.
>> I wanted to get more information related to it.
>>
>
> What's the set of functions you are proposing for those not tracking your
> draft proposal?
>
Link:
https://docs.google.com/document/d/1n-JOFUbFn6V1kViAGWsEGbVHL9MxlMyKP0BbZhEA1Rs/edit?usp=sharing
I haven't searched about the functions in the list yet. The list was made
by Vaibhav, last year and he told me that it could be added to proposal
this year as well.
I read the archives that these need to be written from scratch.


>> thanks
>> -Eshan
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [rtems-examples PATCH v2 1/2] Update rtems_waf

[Chris Johns]

On 2020-03-25 07:19, Vijay Kumar Banerjee wrote:
On Thu, Mar 19, 2020 at 7:54 AM Chris Johns > wrote:


Both these patches are fine to push. Vijay, please push once your
access has
been sorted out.

Pushed this!


Nice and thanks :)

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel