Re: [PATCH v2] user/bsps : Add documentation for Beagle

On Fri, Jul 19, 2019 at 7:27 PM Chris Johns wrote: > > On 20/7/19 6:41 am, Gedare Bloom wrote: > > On Fri, Jul 19, 2019 at 11:02 AM Christian Mauderer > > wrote: > >> > >> On 19/07/2019 18:21, Gedare Bloom wrote: > >>> Looks good to me. I'm currently not able to apply it, verify the doc > >>>

Re: Build failed for RTEMS Source Builder

On 20/7/19 4:48 am, Vijay Kumar Banerjee wrote: > On Sat, Jul 20, 2019, 12:03 AM Himanshu Sekhar Nayak > mailto:himanshuwindows...@gmail.com>> wrote: > > Hi Chris, > > After your solution, I changed the required source directories Great. Are you able to please post the patch? > but

Re: GSoC Linux UIO driver for PRU

On 19/7/19 8:32 pm, Nils Hölscher wrote: > I am currently adding more and more libbsd deps to my build, that are not in > rtems or rtems-libbsd. > Now I have been touching these to files of the BSD kernel: >

Re: [PATCH v2] user/bsps : Add documentation for Beagle

On 20/7/19 6:41 am, Gedare Bloom wrote: > On Fri, Jul 19, 2019 at 11:02 AM Christian Mauderer > wrote: >> >> On 19/07/2019 18:21, Gedare Bloom wrote: >>> Looks good to me. I'm currently not able to apply it, verify the doc >>> build, and push it though. (Workstation issues.) >>> >> >> I agree

Re: GSoC Project | Basic Support for Trace Compass

> > This looks very nice. > > The next step is to translate the record items into corresponding events > of LTTNG. We should start with the following event which I guess is used > by Trace Compass for the task switch view. I don't know it, we have to > try it out. We can also look at the analyses

Re: Docs Style Guide

> On 19 Jul 2019, at 3:09 pm, Sebastian Huber > wrote: > >> On 19/07/2019 00:23, Gedare Bloom wrote: >>> On Thu, Jul 18, 2019 at 11:35 AM Chris Johns wrote: On 19/7/19 1:32 am, Gedare Bloom wrote: Reviewing the BB doc patch, I realized that we need a style guide for writing

Re: GSoC Project | Basic Support for Trace Compass

On 19/07/2019 08:38, Ravindra Kumar Meena wrote: This looks very nice. The next step is to translate the record items into corresponding events of LTTNG. We should start with the following event which I guess is used by Trace Compass for the task switch view. I don't

[PATCH] Makefile.inc: Add support for staged builds.

From: Chris Johns - Allow the RTEMS_ROOT to be conditionally supplied. This can be a staging area before being moved to the final install prefix location. - Update the default.cfg to use RTEMS_ROOT and to not rely on the exec_prefix so it's paths can be staged. - Fix and add the needed

[PATCH v2] user/bsps : Add documentation for Beagle

--- user/bsps/arm/beagle.rst | 110 ++- 1 file changed, 108 insertions(+), 2 deletions(-) diff --git a/user/bsps/arm/beagle.rst b/user/bsps/arm/beagle.rst index a36efde..eb4ecfb 100644 --- a/user/bsps/arm/beagle.rst +++ b/user/bsps/arm/beagle.rst @@ -1,8

Re: [PATCH] user/bsps : Add documentation for Beagle

On Thu, Jul 18, 2019 at 9:07 PM Gedare Bloom wrote: > On Thu, Jul 18, 2019 at 8:24 AM Vijay Kumar Banerjee > wrote: > > > > --- > > user/bsps/arm/beagle.rst | 91 +++- > > 1 file changed, 89 insertions(+), 2 deletions(-) > > > > diff --git

Coverity Model

Hello, you can add a model file to Coverity to reduce the false positive rate of the static analysis. I didn't check that the RTEMS scan can profit from this since we already supply a lot of code to the scan. What I found interesting is that Qemu uses this:

Re: build of libbsd for powerpc fails with error: redefinition of 'eieio'

> On Jul 19, 2019, at 01:21 , Sebastian Huber > wrote: > > A sounds like a good approach. Finding all users of these defines > is a bit of work. They are used by shared code, so every BSP which uses this > shared code needs the new header file. That is mostly addressed by rebuilding all

BSP names

Hello, I worked a bit with Doorstop and found the YAML file quite interesting. The file format is not without problems: https://arp242.net/yaml-config.html However, for simple configuration stuff it is easy to write, read and process. Changes can be reviewed well in Git (content is spread

Re: GSoC Linux UIO driver for PRU

On Thu, 18 Jul 2019 at 19:18, Chris Johns wrote: > On 18/7/19 7:11 pm, Nils Hölscher wrote: > > @chr...@rtems.org but where do we place the > shell > > part, which exists between BSD and RTEMS? > > LibBSD has a number of shell commands so this should not be a problem.

Re: BSP names

On Fri, Jul 19, 2019 at 4:33 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > I worked a bit with Doorstop and found the YAML file quite interesting. > The file format is not without problems: > > https://arp242.net/yaml-config.html > > However, for simple

Re: Coverity Model

Hi Sebastian, On Fri, Jul 19, 2019 at 2:57 AM Sebastian Huber wrote: > > Hello, > > you can add a model file to Coverity to reduce the false positive rate > of the static analysis. I didn't check that the RTEMS scan can profit > from this since we already supply a lot of code to the scan. What I

Re: [PATCH v2] user/bsps : Add documentation for Beagle

Looks good to me. I'm currently not able to apply it, verify the doc build, and push it though. (Workstation issues.) On Fri, Jul 19, 2019 at 2:07 AM Vijay Kumar Banerjee wrote: > > --- > user/bsps/arm/beagle.rst | 110 ++- > 1 file changed, 108

Re: [PATCH v2] user/bsps : Add documentation for Beagle

On 19/07/2019 18:21, Gedare Bloom wrote: > Looks good to me. I'm currently not able to apply it, verify the doc > build, and push it though. (Workstation issues.) > I agree that it looks OK. Thanks from me too for contributing to the documentation. It's something that most developers don't like

Re: Build failed for RTEMS Source Builder

Hi Chris, After your solution, I changed the required source directories but seems like idk why it needs sudo privileges ? https://paste.ofcode.org/38mtbHLLH9WggmRkXWZDq4r Thanks Himanshu ___ devel mailing list devel@rtems.org

Re: Build failed for RTEMS Source Builder

On Sat, Jul 20, 2019, 12:03 AM Himanshu Sekhar Nayak < himanshuwindows...@gmail.com> wrote: > Hi Chris, > > After your solution, I changed the required source directories but seems > like idk why it needs sudo privileges ? > > https://paste.ofcode.org/38mtbHLLH9WggmRkXWZDq4r > The path /opt/

Re: [PATCH v2] user/bsps : Add documentation for Beagle

On Fri, Jul 19, 2019 at 10:32 PM Christian Mauderer wrote: > On 19/07/2019 18:21, Gedare Bloom wrote: > > Looks good to me. I'm currently not able to apply it, verify the doc > > build, and push it though. (Workstation issues.) > > > > I agree that it looks OK. Thanks from me too for

Re: [PATCH v2] user/bsps : Add documentation for Beagle

On Fri, Jul 19, 2019 at 11:02 AM Christian Mauderer wrote: > > On 19/07/2019 18:21, Gedare Bloom wrote: > > Looks good to me. I'm currently not able to apply it, verify the doc > > build, and push it though. (Workstation issues.) > > > > I agree that it looks OK. Thanks from me too for