Re: Interested for GSoC 2023

2023-02-26 Thread Vihas Makwana
> > > Another GCC related project could be Rust RTEMS Support but I don't know > what that entails beyond turning it on and seeing what goes wrong. I tried > to build it last year and got far enough to decide to wait before trying > again. > I have to look deeper into this Rust one and I'll let yo

Re: Interested for GSoC 2023

2023-02-26 Thread Joel Sherrill
On Sun, Feb 26, 2023, 3:44 PM Vihas Makwana wrote: > Hello, > > My name is Vihas Makwana, and I'm a software developer. > > I came across RTEMS while reviewing the "Organizations" for GSoC 2023. > By going through the Project Ideas [1], the following ideas caught my > attention: > > -- Use Addres

Interested for GSoC 2023

2023-02-26 Thread Vihas Makwana
A minor change. Signed-off-by: Vihas Makwana --- testsuites/samples/hello/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/ini t.c index 83f6342ab3..3b70772917 100644 --- a/testsuites/samples/hello/init.c +++ b/te

Interested for GSoC 2023

2023-02-26 Thread Vihas Makwana
Hello, My name is Vihas Makwana, and I'm a software developer. I came across RTEMS while reviewing the "Organizations" for GSoC 2023. By going through the Project Ideas [1], the following ideas caught my attention: -- Use Address Sanitizer (ASAN) with RTEMS [2] -- POSIX Compliance [3] -- IMFS -

Re: GSoC project suggestion for the BSP Raspberry pi 4B aarch64

2023-02-26 Thread Joel Sherrill
The Pynq is a low cost Zynq board I have wanted to have support for. http://www.pynq.io/board.html Basic support should be a matter of tweaking the settings and adding a bsp variant On Sat, Feb 25, 2023, 10:21 AM Alan Cudmore wrote: > Improving Raspberry Pi 4 support would be a great GSOC proj

Re: Project Discussion for GSoC 2023

2023-02-26 Thread Viraj Jagadale
Thanks, Gabriel, I will surely go through it this week. I have been reading about writing driver code and noted the following steps that I would need to follow: 1. Select the hardware device for which the driver has to be written. 2. Read the device specification and protocol used.