On Fri, Mar 9, 2018 at 12:57 AM,  <devel-requ...@rtems.org> wrote:
> Send devel mailing list submissions to
>         devel@rtems.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.rtems.org/mailman/listinfo/devel
> or, via email, send a message with subject or body 'help' to
>         devel-requ...@rtems.org
>
> You can reach the person managing the list at
>         devel-ow...@rtems.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of devel digest..."
>
>
> Today's Topics:
>
>    1. Enabling smptests for i386/pc386 (for #2138) (Amaan Cheval)
>    2. Need testing on motorola_powerpc and beatnik BSPs (Joel Sherrill)
>    3. Gsoc 2018 (Salil Sirotia)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 08 Mar 2018 18:22:31 +0000
> From: Amaan Cheval <amaan.che...@gmail.com>
> To: RTEMS <devel@rtems.org>
> Subject: Enabling smptests for i386/pc386 (for #2138)
> Message-ID:
>         <cag+weg17i3sjzwyzttsistrgiwg3e1t1iunlrlgusrdzckv...@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> In reference to #2138; I'd like to give fixing this issue a shot to get my
> feet
> wet with RTEMS.
>
> I tried enabling the tests in ./testsuites/smptests/ to find a way to make
> the
> test fail at first, so I'd have a frame of reference, but I couldn't quite
> get
> the test to be compiled for i386 at all.
>
> (I'm not quite sure yet how --enable-tests determines which of the
> testsuites
> get built - I think bspopts.h.in is generated based on the BSP-specific
> config?)
>
> Based on the little note about --enable-smp in the docs[1], I added the
> switch,
> along with --enable-tests during the configure stage.
>
> Full command:
>
> ../kernel/configure --prefix=$HOME/bin/rtems/5-i386 --target=i386-rtems5
> --enable-rtemsbsp=pc386 --enable-posix --enable-tests --enable-smp
>
> This results in a failure at the make step[2] (at least as of commit cf2024
> (and
> a quick test against 828049, after running bootstrap -H as well)).
>
> Before the preinstall stage was removed, BSP_HAS_SMP in
> ./c/src/lib/libbsp/i386/pc386/include/bspopts.h.in was undef'd as well,
> which
> seems to be relevant.
>
> I haven't dug enough into what may be causing the error; I'm sending this
> email
> erring on the side of asking too many questions, since I figured it'd be
> more
> effective to just get help and work faster from the collective genius of the
> community!
>
> Am I just doing something inherently misguided in even trying to enable
> these
> tests for i386?
>
>
> [1]
> https://docs.rtems.org/branches/master/c-user/symmetric_multiprocessing_services.html#introduction
> [2] https://gist.github.com/AmaanC/03566c18793ff61a25328bfaf395df09
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 8 Mar 2018 13:17:54 -0600
> From: Joel Sherrill <j...@rtems.org>
> To: "rtems-de...@rtems.org" <devel@rtems.org>
> Subject: Need testing on motorola_powerpc and beatnik BSPs
> Message-ID:
>         <caf9ehcvadrumim2pl3dg4df1gysvpvefote4hgyhxmsdy5p...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi
>
> We have a patch for allowing the BSP to boot when more than 256MB RAM.
> It has only been tested on qemu and we would like to ensure it doesn't
> negatively impact anyone on real HW. The motorola_powerpc and beatnik BSPs
> are impacted.
>
> This is ticket #3322 and we would appreciate some testing with this patch
> on the master.
>
> Thanks.
>
> --joel
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.rtems.org/pipermail/devel/attachments/20180308/94780d40/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 9 Mar 2018 00:57:00 +0530
> From: Salil Sirotia <salil.siro...@gmail.com>
> To: devel@rtems.org
> Subject: Gsoc 2018
> Message-ID:
>         <caeijvqzwxxtrjvndd5vf0htp74p_ghgjsplg03jvn52x92j...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hello Developers,
>
> This is Salil Sirotia, Doing Masters from Indian Institute of
> Technology, Dhanbad. I want to participate in GSoC 2018 at your
> organization.
>
> I have gone through the RTEMS Wiki page. I have set up the environment
> for SPARC and edited the application "Hello World". I am attaching the
> Screenshot of that Application Would you like to review the same.
>
>
> I am pretty good in C/C++, Python, Shell Scripting and worked on git and
> GDB.
>
> I have gone through the open tickets and interested in POSIX
> Compliance Project: https://devel.rtems.org/ticket/2966. And i already have
> some idea about how to build new libraries and I think i might be able to
> do some good work in this project Would you like to point me some docs? I
> am really interested in this project.
>
> Thanks & regards,
> Salil Sirotia,
Hi Salil Sirotia,

Welcome to RTEMS Organization. I would like to suggest you to go
through the POSIX Compliance doc:
https://docs.rtems.org/branches/master/posix-compliance/

For this project, You need to build newlib-cygwin. Here you can find
newlib-cygwin building process:

https://posix4rtemsandnewlib.wordpress.com/2017/07/22/newlib-buiding-process/

It would be good if you have Knowledge of BSP specific methods and
reentrant version of methods. You can go through BSP Development doc
to get some understanding of BSP specific methods.

@gedare/@Joel correct me if I am wrong.

Any comments and suggestions from others would be greatly appreciated.

Thanks & Regards,
Aditya Upadhyay

> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.rtems.org/pipermail/devel/attachments/20180309/2b653eeb/attachment.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: Screenshot from 2018-02-20 22-24-05.png
> Type: image/png
> Size: 198435 bytes
> Desc: not available
> URL: 
> <http://lists.rtems.org/pipermail/devel/attachments/20180309/2b653eeb/attachment.png>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
> ------------------------------
>
> End of devel Digest, Vol 76, Issue 23
> *************************************
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to