Re: pppd unaligned trap on Sparc/LEON3 - Questions about network config

On 22/3/19 2:06 am, Cudmore, Alan P. (GSFC-5820) wrote: > I have PPP nearly working between RTEMS/LEON3 and Linux. > > The two sides negotiate the PPP link and the PPP link seems to stay up. The > Linux side sends occasional EchoReq packets to RTEMS, which it replies to with > EchoRep. > >   > >

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On Thu, Mar 21, 2019 at 9:05 AM Vaibhav Gupta wrote: > > > On Thu, Mar 21, 2019 at 6:10 PM Joel Sherrill wrote: > >> >> >> On Thu, Mar 21, 2019, 2:43 AM Vaibhav Gupta >> wrote: >> >>> Hello, >>> After series of discussions and exploring things, I got Idea about >>> various things in this projec

Re: rtems-libbsd build error

Am 21.03.19 um 15:36 schrieb Vijay Kumar Banerjee: > > On Wed, 20 Mar 2019 at 01:52, Christian Mauderer > wrote: > > Am 19.03.19 um 20:37 schrieb Vijay Kumar Banerjee: > > > > > > > > On Tue, 19 Mar 2019 at 02:44, Christian Mauderer > mailto:l..

Re: pppd unaligned trap on Sparc/LEON3 - Questions about network config

I have PPP nearly working between RTEMS/LEON3 and Linux. The two sides negotiate the PPP link and the PPP link seems to stay up. The Linux side sends occasional EchoReq packets to RTEMS, which it replies to with EchoRep. In my example, the RTEMS/LEON3 IP is 192.168.3.1 and the Linux peer IP is

Re: rtems-libbsd build error

On Wed, 20 Mar 2019 at 01:52, Christian Mauderer wrote: > Am 19.03.19 um 20:37 schrieb Vijay Kumar Banerjee: > > > > > > > > On Tue, 19 Mar 2019 at 02:44, Christian Mauderer > > wrote: > > > > Am 18.03.19 um 20:31 schrieb Vijay Kumar Banerjee: > > > > > > >

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On Thu, Mar 21, 2019 at 6:10 PM Joel Sherrill wrote: > > > On Thu, Mar 21, 2019, 2:43 AM Vaibhav Gupta > wrote: > >> Hello, >> After series of discussions and exploring things, I got Idea about >> various things in this project. >> I have got Interested in following sub-tickets: >> -- #2970 - Ad

Re: RTEMS Requirement Management Tools

Moved to devel On Thu, Mar 21, 2019 at 6:23 AM Jose Valdez wrote: > Hello All, > > > > This e-mail will serve to answer some questions that were raised in other > e-mails regarding Requirement Management Tools selection and this project > in general. > > > > First of all, sorry if the way I am s

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On 21/03/2019 14:14, Joel Sherrill wrote: On Thu, Mar 21, 2019 at 7:52 AM Sebastian Huber > wrote: On 21/03/2019 13:39, Joel Sherrill wrote: > > >      * >         -- pselect() from >      * >         -- sockatmark() fro

Re: [PATCH 2/3] Add the T Test Framework

On 20/03/2019 23:18, Chris Johns wrote: 3. What does 'T' in THE_T_TEST_FRAMEWORK_H stand for? I prefer we prefix RTEMS_ where it makes sense. The 'T' is just a random name which associates with testing. I searched a bit for and a T_ prefix and didn't found an existing project. So, there should

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On Thu, Mar 21, 2019 at 7:52 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 21/03/2019 13:39, Joel Sherrill wrote: > > > > > > * > > -- pselect() from > > * > > -- sockatmark() from > > > > Sebastian.. are these not in the new tcpip stack? > > They

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On 21/03/2019 13:39, Joel Sherrill wrote: * -- pselect() from * -- sockatmark() from Sebastian.. are these not in the new tcpip stack? They are declared in the header files. They are not included in libbsd, but this should be an issue. -- Sebastian Huber, embed

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On Thu, Mar 21, 2019, 2:43 AM Vaibhav Gupta wrote: > Hello, > After series of discussions and exploring things, I got Idea about various > things in this project. > I have got Interested in following sub-tickets: > -- #2970 - Add ftw.h to Newlib : https://devel.rtems.org/ticket/2970 > -- #2971 -

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

On 21/03/2019 13:16, Vaibhav Gupta wrote: Yes I checked them, they can be, Most of them can be ported from glibc / freebsd/ netbsd . But for some of them, they don't even have a linux man page. I guess they need to written from scratch. . I don't know, but if they can be bought under POSIX Compil

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

Yes I checked them, they can be, Most of them can be ported from glibc / freebsd/ netbsd . But for some of them, they don't even have a linux man page. I guess they need to written from scratch. . I don't know, but if they can be bought under POSIX Compilance Umbrella, I am ready to work on them.

Re: Sub-Tickets selected for POSIX Compilance GSoc Project

It would be nice if the *at() file descriptor functions could be implemented in this GSoC project, e.g. dirent.h:int   scandirat(int, const char *, struct dirent ***, sys/socket.h:int  bindat(int, int, const struct sockaddr *, socklen_t); sys/socket.h:int  connectat(int, int, const struc

Sub-Tickets selected for POSIX Compilance GSoc Project

Hello, After series of discussions and exploring things, I got Idea about various things in this project. I have got Interested in following sub-tickets: -- #2970 - Add ftw.h to Newlib : https://devel.rtems.org/ticket/2970 -- #2971 - Add fenv.h to Newlib : https://devel.rtems.org/ticket/2971 -- #29