Re: [PATCH] cpu-supplement: Add ARM BSPs chapter

2017-10-25 Thread Sebastian Huber
Please review this patch carefully. It adds a new chapter "ARM Board Support Packages" following the "ARM Specific Information" chapter. It adds a template structure for other BSPs. Where should we place common BSP configuration options like BSP_PRESS_KEY_FOR_RESET? We probably don't want to a

[PATCH] cpu-supplement: Add ARM BSPs chapter

2017-10-25 Thread Sebastian Huber
Add NXP i.MX section as a BSP example. Update #2854. --- cpu-supplement/arm-bsps.rst | 138 cpu-supplement/index.rst| 1 + 2 files changed, 139 insertions(+) create mode 100644 cpu-supplement/arm-bsps.rst diff --git a/cpu-supplement/arm-bsps.rs

Re: Update the RTEMS Porting Guide

2017-10-25 Thread Sebastian Huber
On 25/10/17 15:14, Joel Sherrill wrote: This isn't nearly as important as completing the conversion of the POSIX Users Guide to Sphinx. It is in a middle state and doesn't follow the same format as the Classic API Users Guide. Why do we need separate Classic and POSIX Users Guides? In the nea

Re: [PATCH 1/4] Add riscv32 to autotools files

2017-10-25 Thread Sebastian Huber
Hello Hesham, thanks for your RISC-V port. Most files have a BSD-like license. Would it be possible to use a BSD-2 license for all the files which have the RTEMS license in the patch set? -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +4

[PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain v2

2017-10-25 Thread Hesham Almatary
Update #3109 --- rtems/config/4.12/rtems-riscv64.bset | 16 1 file changed, 16 insertions(+) create mode 100644 rtems/config/4.12/rtems-riscv64.bset diff --git a/rtems/config/4.12/rtems-riscv64.bset b/rtems/config/4.12/rtems-riscv64.bset new file mode 100644 index 000..406c

[PATCH] RSB - Add support for RISC-V RV64 (64-bit) toolchain

2017-10-25 Thread Hesham Almatary
From: Hesham Almatary Update #3109 --- rtems/config/4.12/rtems-riscv64.bset | 16 1 file changed, 16 insertions(+) create mode 100644 rtems/config/4.12/rtems-riscv64.bset diff --git a/rtems/config/4.12/rtems-riscv64.bset b/rtems/config/4.12/rtems-riscv64.bset new file mode 10

[PATCH] Tester - RISC-V: Add spike simulator and scripts/BSPs for riscv ports v2

2017-10-25 Thread Hesham Almatary
Update #3109 --- tester/rtems/rtems-bsps-riscv32.ini | 25 tester/rtems/rtems-bsps-riscv64.ini | 25 tester/rtems/testing/bsps/riscv64_generic.ini | 38 ++ tester/rtems/testing/bsps/riscv64_generic.mc | 53 tes

[PATCH] Tester - RISC-V: Add spike simulator and scripts/BSPs for riscv ports

2017-10-25 Thread Hesham Almatary
From: Hesham Almatary Update #3109 --- tester/rtems/rtems-bsps-riscv32.ini | 25 tester/rtems/rtems-bsps-riscv64.ini | 25 tester/rtems/testing/bsps/riscv64_generic.ini | 38 ++ tester/rtems/testing/bsps/riscv64_generic.mc | 53 +

Re: Update the RTEMS Porting Guide

2017-10-25 Thread Sebastian Huber
On 25/10/17 15:14, Joel Sherrill wrote: This isn't nearly as important as completing the conversion of the POSIX Users Guide to Sphinx. It is in a middle state and doesn't follow the same format as the Classic API Users Guide. A high priority item for me is a place for BSP documentation. --

Re: Update the RTEMS Porting Guide

2017-10-25 Thread Joel Sherrill
This isn't nearly as important as completing the conversion of the POSIX Users Guide to Sphinx. It is in a middle state and doesn't follow the same format as the Classic API Users Guide. On Wed, Oct 25, 2017 at 8:00 AM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > ple

Update the RTEMS Porting Guide

2017-10-25 Thread Sebastian Huber
Hello, please review this ticket: https://devel.rtems.org/ticket/3208 -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key availa

importing selected (dual license) linux modules

2017-10-25 Thread Thomas Doerfler
Hi, in the past few months, Sebastian has extended the RTEMS libbsd infrastructure so it technically can import/export modules from/to the Linux kernel tree. This extension is quite delicate, because in general, the Linux kernel sources are published under GPLv2, which is definitively incompatibl