Re: Name of the primary network interface, how to find in bsp header files?

On 9/8/20 6:51 am, Joel Sherrill wrote: > On Sat, Aug 8, 2020 at 7:09 AM Heinz Junkes > wrote: > > Hallo Chris, > I think there's been a misunderstanding. This is more than likely. I do not know what EPICS requires for network initialisation. Is it

Re: [PATCH 5] shell: Only clear std handles when the shell task exits

On 9/8/20 12:10 am, Gedare Bloom wrote: > it should be applied with the doco patch from sebastian Yes and then I need to update the documentation to mention the main loop needs to manage any standard file descriptors. Chris ___ devel mailing list

Re: Name of the primary network interface, how to find in bsp header files?

On Sat, Aug 8, 2020 at 7:09 AM Heinz Junkes wrote: > Hallo Chris, > I think there's been a misunderstanding. > I have implemented the following in the EPICS rtems_init.c : > > ... > sc = rtems_bsd_initialize(); > assert (sc == RTEMS_SUCCESSFUL) > /* Let the callout timer allocate its resources

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

On Sat, Aug 8, 2020 at 11:10 PM Gedare Bloom wrote: > On Sat, Aug 8, 2020 at 11:08 AM Mritunjay Sharma > wrote: > > > > > > > > On Sat, Aug 8, 2020 at 9:46 PM Heinz Junkes > wrote: > >> > >> Hallo Mritunjay, > >> everything looks pretty good. I'm commenting on the text. I also send > this mail

GSoC2020: RTEMS OpenFirmWare FDT Implementation (outline)

Hello, I have created a basic outline of how the RTEMS openfirm API would look like. The implementation is inspired by the openfirm.h implementation in FreeBSD. Please a have look at the last 2 commits https://github.com/gs-niteesh/rtems/commits/ofw-rtems6-fdt-implementation-v1 Since we are

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

On Sat, Aug 8, 2020 at 11:08 AM Mritunjay Sharma wrote: > > > > On Sat, Aug 8, 2020 at 9:46 PM Heinz Junkes wrote: >> >> Hallo Mritunjay, >> everything looks pretty good. I'm commenting on the text. I also send this >> mail >> to two EPICS experts (Andrew Johnson and Michael Davidsaver). Maybe

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

On Sat, Aug 8, 2020 at 9:46 PM Heinz Junkes wrote: > Hallo Mritunjay, > everything looks pretty good. I'm commenting on the text. I also send this > mail > to two EPICS experts (Andrew Johnson and Michael Davidsaver). Maybe they > also have some ideas. > Thank you so much Heinz! It will be

Re: RTEMS 5 on the start page of RTEMS.org

On Sat, Aug 8, 2020, 10:56 AM Christian Mauderer wrote: > Hello Joel, > > On 08/08/2020 17:51, Joel Sherrill wrote: > > > > > > On Sat, Aug 8, 2020, 10:38 AM Christian Mauderer > > wrote: > > > > Hello, > > > > I noted that on the start page of www.rtems.org >

Re: [GSoC 2020] : BSP Buildset for EPICS (next steps)

Hallo Mritunjay, everything looks pretty good. I'm commenting on the text. I also send this mail to two EPICS experts (Andrew Johnson and Michael Davidsaver). Maybe they also have some ideas. > > Current Status: > > 1) Successfully built EPICS7 with RTEMS5 by hand for pc-386 > 2) Worked for

Re: RTEMS 5 on the start page of RTEMS.org

On Sat, Aug 8, 2020 at 9:52 AM Joel Sherrill wrote: > > > > On Sat, Aug 8, 2020, 10:38 AM Christian Mauderer wrote: >> >> Hello, >> >> I noted that on the start page of www.rtems.org, there are still a lot >> of outdated references to the last release. One of the most obvious is >> the

Re: RTEMS 5 on the start page of RTEMS.org

Hello Joel, On 08/08/2020 17:51, Joel Sherrill wrote: > > > On Sat, Aug 8, 2020, 10:38 AM Christian Mauderer > wrote: > > Hello, > > I noted that on the start page of www.rtems.org > , there are still a lot > of outdated

Re: RTEMS 5 on the start page of RTEMS.org

On Sat, Aug 8, 2020, 10:38 AM Christian Mauderer wrote: > Hello, > > I noted that on the start page of www.rtems.org, there are still a lot > of outdated references to the last release. One of the most obvious is > the Documentation section on the right and the "Release and Active > Development"

RTEMS 5 on the start page of RTEMS.org

Hello, I noted that on the start page of www.rtems.org, there are still a lot of outdated references to the last release. One of the most obvious is the Documentation section on the right and the "Release and Active Development" section. I don't think that our home page is in a git repo so that

Re: [PATCH 5] shell: Only clear std handles when the shell task exits

it should be applied with the doco patch from sebastian On Sat, Aug 8, 2020 at 2:13 AM wrote: > > From: Chris Johns > > Clearing the std file handles when the main loop exited crashes > telnetd as it reuses its session threads. > > Closes #3859 > --- > cpukit/libmisc/shell/shell.c | 26

Re: GSoC 2020: OFW Import To RTEMS License Issue

On Sat, Aug 8, 2020 at 2:48 AM Niteesh G. S. wrote: > > Hello, > > So if I understand correctly, we will be having the following files > under RTEMS. > > 1) rtems-ofw.h / rtems-ofw.c These files will contain the RTEMS > friendly implementation of the OF interface. > For eg: > >

Re: Name of the primary network interface, how to find in bsp header files?

Hallo Chris, I think there's been a misunderstanding. I have implemented the following in the EPICS rtems_init.c : ... sc = rtems_bsd_initialize(); assert (sc == RTEMS_SUCCESSFUL) /* Let the callout timer allocate its resources */ sc = rtems_task_wake_after(2); assert (sc == RTEMS_SUCCESSFUL)

Re: GSoC 2020: OFW Import To RTEMS License Issue

Hello, So if I understand correctly, we will be having the following files under RTEMS. 1) rtems-ofw.h / rtems-ofw.c These files will contain the RTEMS friendly implementation of the OF interface. For eg: rtems_ofw_find_device(phandle_t node) here I plan to implement all the functions that are

Re: [PATCH RTEMS 7/7] libtests/openfirmware: Added a testsuite for openfirmware

On Sat, Aug 8, 2020 at 1:54 PM Chris Johns wrote: > On 8/8/20 6:01 pm, Niteesh G. S. wrote: > > ping. > > I am sorry about the delay in answering. It is the weekend so things can be > slow. I will add some input to see if we can figure this out. I have not > followed all the discussions in

Re: [PATCH RTEMS 7/7] libtests/openfirmware: Added a testsuite for openfirmware

On 8/8/20 6:01 pm, Niteesh G. S. wrote: > ping. I am sorry about the delay in answering. It is the weekend so things can be slow. I will add some input to see if we can figure this out. I have not followed all the discussions in detail so please correct me if I have taken a wrong turn. > On Wed,

[PATCH 5] shell: Only clear std handles when the shell task exits

From: Chris Johns Clearing the std file handles when the main loop exited crashes telnetd as it reuses its session threads. Closes #3859 --- cpukit/libmisc/shell/shell.c | 26 ++ 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/cpukit/libmisc/shell/shell.c

[PATCH] shell: Only clear std handles when the shell task exits

From: Chris Johns Clearing the std file handles when the main loop exited crashes telnetd as it reuses its session threads. --- cpukit/libmisc/shell/shell.c | 26 ++ 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/cpukit/libmisc/shell/shell.c

Re: [PATCH RTEMS 7/7] libtests/openfirmware: Added a testsuite for openfirmware

ping. On Wed, Aug 5, 2020 at 12:16 AM Christian Mauderer wrote: > Hello, > > I think the big question is: Should we make that a public API and keep > it in cpukit or should we make it a BSP support code and move ti to the > bsps/shared section? > > Sebastian and Gedare: Like Niteesh said: There