Re: GSoC Project | Basic Support for Trace Compass

On 22/07/2019 08:46, Ravindra Kumar Meena wrote: Where did you find what? In babeltrace output the value of _prev_state is always 0, 1, 1026 but mostly it is 0 or 1. There is no fixed pattern in the value of _prev_state in babeltrace output. _prev_state is a member of event.field. You

Re: GSoC Project | Basic Support for Trace Compass

> > Where did you find what? > In babeltrace output the value of _prev_state is always 0, 1, 1026 but mostly it is 0 or 1. There is no fixed pattern in the value of _prev_state in babeltrace output. _prev_state is a member of event.field. > > I found: > > event { > name = "sched_switch";

Re: GSoC Project | Basic Support for Trace Compass

On 22/07/2019 07:47, Ravindra Kumar Meena wrote: *Plan of the week:* Last week I added packet.header, packet.context, event.header, env object in the metadata. I will continue to work on adding event object in the metadata. I have added the few parts of the sched_switch event. https://github

Re: Requirement Identifiers

Hello, I would like to clarify one detail with respect to the requirement identifiers. The current consensus is that the requirements should be grouped by component, e.g. RTEMS ^-- RTEMS-Classic ^-- RTMES-Classic-Task ^-- RTMES-Classic-Semaphore ^-- RTEMS-POSIX The group name and a n

GSoC Project | Basic Support for Trace Compass

*Plan of the week:* Last week I added packet.header, packet.context, event.header, env object in the metadata. I will continue to work on adding event object in the metadata. I have added the few parts of the sched_switch event. https://github.com/rmeena840/rtems-tools/commit/7b1488364b86df5ec956

Re: Loading libBSD driver modules

Hello Nils, yes, you can add devices after initialization. For example: int my_attach(void) { device_t dev; device_t child; dev = device_find_child(root_bus, "nexus", 0); if (dev == NULL) { return ENXIO; } child = device_add_child

[PATCH] user/bsps : Fix formatting and typo in arm/beagle

--- user/bsps/arm/beagle.rst | 55 +++- 1 file changed, 37 insertions(+), 18 deletions(-) diff --git a/user/bsps/arm/beagle.rst b/user/bsps/arm/beagle.rst index 84bfe2d..eb4ecfb 100644 --- a/user/bsps/arm/beagle.rst +++ b/user/bsps/arm/beagle.rst @@ -5,10 +5,10

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

On 21/7/19 6:09 pm, Christian Mauderer wrote: > On 21/07/2019 04:46, Chris Johns wrote: >> On 20/7/19 4:50 pm, Christian Mauderer wrote: >>> On 19/07/2019 20:59, Vijay Kumar Banerjee wrote: On Fri, Jul 19, 2019 at 10:32 PM Christian Mauderer >>> > wrote:

Re: Loading libBSD driver modules

On 21/7/19 8:55 pm, Nils Hölscher wrote: > Is there a way to load libBSD driver modules one by one? > Currently rtems loads all drivers at once with rtems_bsd_initialize. > But I need to debug via network, so I need to have libBSD network support > before > loading my PRU driver Module. Sorry I d

[PATCH 2/7] sb/config: Fix GDB probes when using python-config.

From: Chris Johns - Fix the config file handling of shell calls where the shell command has nesting braces. - Fix the bool check to support a '!' next to the check value. --- source-builder/config/gdb-common-1.cfg | 5 +-- source-builder/sb/config.py| 47 --

[PATCH 6/7] sb/setbuilder: Support staging of build set build before installing.

From: Chris Johns - Staging lets build sets use previously built build sets. - Fix the rtems-bsp builds to support staging. --- rtems/config/5/rtems-libbsd.bset | 2 +- rtems/config/rtems-bsp.cfg | 28 +++- rtems/config/tools/rtems-libbsd-common.cfg | 2 +- source

[PATCH 1/7] 5/packages: Add curl and update all packages with RTEMS 5 and LibBSD

From: Chris Johns - Update rtems-bsp support to correctly handle hosts for BSP. - Clean up the options for a BSP. - Check all RTEMS 5 packages and add 5/rtems-packages for all that build. - Update download locations and checksum of all packages. - The work requires the kernel and Libbsd hacve th

[PATCH 7/7] rtems/bsp: Build packages for the beagle BSP.

From: Chris Johns Closes #3769 --- rtems/config/5/bsps/beagleboneblack.bset | 6 +- rtems/config/5/rtems-or1k.bset | 1 - rtems/config/5/rtems-riscv.bset| 1 - rtems/config/5/rtems-x86_64.bset | 1 - rtems/config/rtems-bsp.cfg | 93

[PATCH 3/7] rtems: Add kernel, libbsd and BSP building as packages.

From: Chris Johns --- rtems/config/5/bsps/beagleboneblack.bset| 19 ++ rtems/config/5/rtems-default.bset | 1 - rtems/config/5/rtems-kernel.bset| 15 ++ rtems/config/5/rtems-libbsd.bset| 8 + rtems/config/rtems-base.bset| 9 + rtems/c

[PATCH 4/7] sb/config: Add triplet processing command.

From: Chris Johns --- source-builder/sb/config.py | 31 +++ 1 file changed, 31 insertions(+) diff --git a/source-builder/sb/config.py b/source-builder/sb/config.py index 2c3a13e..8541cb5 100644 --- a/source-builder/sb/config.py +++ b/source-builder/sb/config.py @@ -6

[PATCH 5/7] sb/options: Update copyright year to 2019.

From: Chris Johns --- source-builder/sb/options.py | 19 +-- 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/source-builder/sb/options.py b/source-builder/sb/options.py index d8e7a88..9fe0269 100644 --- a/source-builder/sb/options.py +++ b/source-builder/sb/options

[PATCH] RTEMS BSP Buildset

This series of patches adds BSP buildset support to the RSB. A top level BSP buildset can be added that can include the tools, kernel and 3rd party packages, such as libbsd. A single buildset command will build and install a complete BSP development environment: $ ../source-builder/sb-buildset --

Loading libBSD driver modules

Hi, Is there a way to load libBSD driver modules one by one? Currently rtems loads all drivers at once with rtems_bsd_initialize. But I need to debug via network, so I need to have libBSD network support before loading my PRU driver Module. Best, Nils _

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

On 21/07/2019 04:46, Chris Johns wrote: > On 20/7/19 4:50 pm, Christian Mauderer wrote: >> On 19/07/2019 20:59, Vijay Kumar Banerjee wrote: >>> On Fri, Jul 19, 2019 at 10:32 PM Christian Mauderer >> > wrote: >>> >>> On 19/07/2019 18:21, Gedare Bloom wrote: >>> > L