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 kn

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 doc

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 p

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

On 18/07/2019 19:37, dufa...@hda.com wrote: On Jul 18, 2019, at 01:16 , Sebastian Huber wrote: I think the should not include the low level io.h header file. Is there an up-to-date definition of what should be in ? The latest "RTEMS BSP and Driver Guide” says: I don't have an up-to-

Re: Docs Style Guide

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 docs [1]. Thank you for raising this. We should start to collect Documentation S

Re: GSoC Project | Basic Support for Trace Compass

On 19/07/2019 06:08, Ravindra Kumar Meena wrote: Hi, I had a look at the variant examples documented here https://diamon.org/ctf/#ex-variants. The examples explain how variant work. First, it takes the id and on the basis of id passed it selects the struct(compact, extended) present in varian

Re: GSoC Project | Basic Support for Trace Compass

Hi, I had a look at the variant examples documented here https://diamon.org/ctf/#ex-variants. The examples explain how variant work. First, it takes the id and on the basis of id passed it selects the struct(compact, extended) present in variant data-type. If id passed to the variant is in the ra

Re: Docs Style Guide

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 docs [1]. > > Thank you for raising this. > > > We should start to collect Documentation Style notes in a wiki page,

Re: Docs Style Guide

On Thu, Jul 18, 2019, 3:54 PM 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 docs [1]. > > > > Thank you for raising this. > > > >

Re: Docs Style Guide

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 docs [1]. > > Thank you for raising this. > > > We should start to collect Documentation Style notes in a wiki page,

Re: Docs Style Guide

On Thu, Jul 18, 2019 at 12:33 PM Joel Sherrill wrote: > On Thu, Jul 18, 2019, 12:35 PM 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 docs [1]. [...] >> > >> > [1] >> > https://docs.rtems.org/b

Re: [PATCH v4] ndbm test suite

On Thu, Jul 18, 2019 at 11:05 AM Vaibhav Gupta wrote: > > --- > testsuites/psxtests/Makefile.am | 7 + > testsuites/psxtests/configure.ac | 1 + > testsuites/psxtests/psxndbm01/init.c | 305 +++ > 3 files changed, 313 insertions(+) > create mode 100644 testsu

Re: Docs Style Guide

On Thu, Jul 18, 2019, 12:35 PM 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 docs [1]. > > Thank you for raising this. > > > We should start to collect Documentation Style notes in a wiki page, >

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

> On Jul 18, 2019, at 01:16 , Sebastian Huber > wrote: > >>> I think the should not include the low level io.h header file. Is there an up-to-date definition of what should be in ? The latest "RTEMS BSP and Driver Guide” says: "The file include/bsp.h contains prototypes and definitions sp

Re: Docs Style Guide

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 docs [1]. Thank you for raising this. > We should start to collect Documentation Style notes in a wiki page, > and then push it to the docs [1]. If anyone has some initial set

Re: GSoC Linux UIO driver for PRU

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. > However this doesn't have priority right now, does it? I th

[PATCH v4] ndbm test suite

--- testsuites/psxtests/Makefile.am | 7 + testsuites/psxtests/configure.ac | 1 + testsuites/psxtests/psxndbm01/init.c | 305 +++ 3 files changed, 313 insertions(+) create mode 100644 testsuites/psxtests/psxndbm01/init.c diff --git a/testsuites/psxtests/Make

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

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 a/user/bsps/arm/beagle.rst b/user/bsps/arm/beagle.rst > index a36efde..84bfe2d 100644 > -

Docs Style Guide

Reviewing the BB doc patch, I realized that we need a style guide for writing docs [1]. We should start to collect Documentation Style notes in a wiki page, and then push it to the docs [1]. If anyone has some initial set of thoughts, it would be good to put them down in reply to this email. My i

[PATCH] user/bsps : Add documentation for Beagle

--- user/bsps/arm/beagle.rst | 91 +++- 1 file changed, 89 insertions(+), 2 deletions(-) diff --git a/user/bsps/arm/beagle.rst b/user/bsps/arm/beagle.rst index a36efde..84bfe2d 100644 --- a/user/bsps/arm/beagle.rst +++ b/user/bsps/arm/beagle.rst @@ -1,8 +1,95 @

Re: Requirement Identifiers

On 18/07/2019 15:36, Sebastian Huber wrote: On 11/07/2019 15:44, Sebastian Huber wrote: On 11/07/2019 15:19, Joel Sherrill wrote: Early on, we discussed that there wasn't a Rest backend to Doorstop. If we are having to add that anyway, can each "category" be generated as a chapter? We could g

Re: Requirement Identifiers

On 11/07/2019 15:44, Sebastian Huber wrote: On 11/07/2019 15:19, Joel Sherrill wrote: Early on, we discussed that there wasn't a Rest backend to Doorstop. If we are having to add that anyway, can each "category" be generated as a chapter? We could generate 100+ chapters but we can't have 100+

Re: GSoC PRU: simplebus vs nexus

On 18/07/2019 12:58, Nils Hölscher wrote: Hi, What is the state of simplebus in rtems-libbsd? It works fine. I found the simplebus files in the rtems-libbsd repository, but when building the compiler is not able to resolve the following include: #include Not all header files are installed

GSoC PRU: simplebus vs nexus

Hi, What is the state of simplebus in rtems-libbsd? I found the simplebus files in the rtems-libbsd repository, but when building the compiler is not able to resolve the following include: #include Should I go with nexus instead as described in this Blog from 2015 or is it outdated? https://ragu

Re: GSoC Project | Basic Support for Trace Compass

On 18/07/2019 11:28, Ravindra Kumar Meena wrote: I would use two structures for this in C, one for the compact header and one for the large header. I would not use bit fields in C. Without bit fields how I would assign it exact 27-bit timestamp? You open the C book that you already

Re: GSoC Project | Basic Support for Trace Compass

> > I would use two structures for this in C, one for the compact header and > one for the large header. I would not use bit fields in C. > Without bit fields how I would assign it exact 27-bit timestamp? It is mentioned on https://diamon.org/ctf/#ex-variants that we can use union in C for variant

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 11:14, Nils Hölscher wrote: > > > On Thu, 18 Jul 2019 at 10:48, Christian Mauderer > > wrote: > > On 18/07/2019 10:30, Nils Hölscher wrote: > > Hi, > > > > Do I need to add an rtems_filesystem_file_handlers_r struct to

Re: GSoC Linux UIO driver for PRU

On Thu, 18 Jul 2019 at 10:48, Christian Mauderer < christian.maude...@embedded-brains.de> wrote: > On 18/07/2019 10:30, Nils Hölscher wrote: > > Hi, > > > > Do I need to add an rtems_filesystem_file_handlers_r struct to the pru > > driver to register it or are the cdevsw sufficient? > > Current st

Re: GSoC Linux UIO driver for PRU

Thanks everyone, @Sebastian Huber I was just confused because of the examples I got earlier using rtems IMFS but now everything is clear. The BSD Documentation helps thanks again. @Christian Mauderer Thanks for pointing out the relevant parts I wasn't seeing at the moment. The defines were in

Re: GSoC Linux UIO driver for PRU

On 18/7/19 6:48 pm, Sebastian Huber wrote: > On 18/07/2019 10:41, Nils Hölscher wrote: >> So I will be fine just using the BSD structs? > > I don't know what you want to do. If you already have FreeBSD kernel code, > then > using the FreeBSD API is probably easier. Does this determine where we p

[PATCH v5] Add mmap

--- freebsd/sys/kern/kern_conf.c | 8 +++ freebsd/sys/sys/conf.h | 2 +- rtemsbsd/include/machine/vm.h | 2 ++ rtemsbsd/sys/fs/devfs/devfs_devs.c | 38 ++ testsuite/cdev01/test_cdev.c | 21 - testsuite/cdev01/test_cdev

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 10:30, Nils Hölscher wrote: > Hi, > > Do I need to add an rtems_filesystem_file_handlers_r struct to the pru > driver to register it or are the cdevsw sufficient? > Current status of the driver: > https://github.com/nilhoel1/rtems-pru/blob/pruss-shell/pruss.c#L806 > > I am still not

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 10:41, Nils Hölscher wrote: So I will be fine just using the BSD structs? I don't know what you want to do. If you already have FreeBSD kernel code, then using the FreeBSD API is probably easier. But how do I register devices with the FreeBSD API, since the examples you provid

Re: GSoC Linux UIO driver for PRU

So I will be fine just using the BSD structs? But how do I register devices with the FreeBSD API, since the examples you provided earlier don't hold anymore. Or am I getting something wrong on my side? On Thu, 18 Jul 2019 at 10:38, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On

Re: GSoC Linux UIO driver for PRU

On 18/07/2019 10:30, Nils Hölscher wrote: Do I need to add an rtems_filesystem_file_handlers_r struct to the pru driver to register it or are the cdevsw sufficient? Current status of the driver: https://github.com/nilhoel1/rtems-pru/blob/pruss-shell/pruss.c#L806 I am still not clear what the

Re: [PATCH v4] Add mmap

On 18/07/2019 10:34, Vijay Kumar Banerjee wrote: Does the MAP_SHARED not end up here somehow? The MAP* flags are checked by the RTEMS mmap before calling the mmap handler, so it doesn't end up here. The map parameters are used to check erros and set the other attributes accordingly. The mm

Re: [PATCH v4] Add mmap

Hi, On Thu, Jul 18, 2019 at 10:39 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 17/07/2019 22:28, Vijay Kumar Banerjee wrote: > > +static int > > +testmmap(struct cdev *dev, vm_ooffset_t offset, vm_paddr_t *paddr, > > + int nprot, vm_memattr_t *memattr) > > +{ > > +

Re: GSoC Linux UIO driver for PRU

Hi, Do I need to add an rtems_filesystem_file_handlers_r struct to the pru driver to register it or are the cdevsw sufficient? Current status of the driver: https://github.com/nilhoel1/rtems-pru/blob/pruss-shell/pruss.c#L806 I am still not clear what the differences between these two structs are.