SPI Framework

Hello, for a project, I want to integrate the following software pieces into RTEMS: - cpukit: a general SPI framework which shall be used for upcoming SPI drivers - cpukit: a generic RS232/485 Termios driver for the microcontroller NXP89LPC935 http://pdf1.alldatasheet.com/datasheet-pdf/view

[PATCH] librtems++: Remove from RTEMS.

This is old and there are better design patterns for threading and C++. We recommend you use the new C++ standards based support. Closes #2777. --- c/src/configure.ac | 6 - c/src/librtems++/Makefile.am | 23 - c/src/librtems++/README

Re: Add RTEMS_BSD_CONFIG_xxx and rc.conf interface for PF

On 09/08/2016 00:32, Christian Mauderer wrote: The appended patch set adds - RTEMS_BSD_CONFIG_FIREWALL_PF - RTEMS_BSD_CONFIG_FIREWALL_PFLOG - RTEMS_BSD_CONFIG_FIREWALL_PFSYNC for enabling the PF firewall. Further it adds an rc.conf interface that mimics the one in FreeBSD. It handles the

Re: [PATCH] build-system: Always enable C++ if the compiler is present.

I think this is a good idea. It reduces the configuration options a bit and doesn't add any run time code. It barely adds any build time. On Aug 9, 2016 10:11 PM, "Chris Johns" wrote: > We always build a C++ compiler and building with C++ does not effect > RTEMS or the runtime. This patch always

[PATCH] build-system: Always enable C++ if the compiler is present.

We always build a C++ compiler and building with C++ does not effect RTEMS or the runtime. This patch always enabled the support. There is no need to manually enable it any more. You can disable C++ with '--disable-cxx'. If an architecture does not have a C++ compiler support is automatically dis

Re: RSB toolchain builds on Windows 10/Windows Subsystem for Linux

On 09/08/2016 23:51, Alan Cudmore wrote: I thought I would try the new Windows Subsystem for Linux to see how the RSB toolchain build would go. WSL is a port of the Ubuntu 14.04 user space binaries to the windows 10 kernel: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux The RSB toolch

RSB toolchain builds on Windows 10/Windows Subsystem for Linux

I thought I would try the new Windows Subsystem for Linux to see how the RSB toolchain build would go. WSL is a port of the Ubuntu 14.04 user space binaries to the windows 10 kernel: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux The RSB toolchain builds the same here as it does on a na

RE: librtems++ examples

Thank you for your fast reply -Message d'origine- De : devel [mailto:devel-boun...@rtems.org] De la part de Chris Johns Envoyé : mardi 9 août 2016 07:30 À : devel@rtems.org Objet : Re: librtems++ examples On 09/08/2016 00:57, Boughedada Kamal wrote: > > I found librtems++ wrapper for the

Re: libbsd: Manipulating object files using waf build system

Am 02.08.2016 um 08:04 schrieb Christian Mauderer: > Hello, > > I have a second waf problem beneath the one already discussed in the > other thread: Is it possible to do some object file manipulation before > linking? To be exact I would need to rename some of the sections in the > object files. >

[PATCH] libbsp/arm: Add the TTB table to the default MMU set up as read/write.

This lets the table be changed at runtime for dynamic loading and debugger support. --- c/src/lib/libbsp/arm/shared/include/arm-cp15-start.h | 4 1 file changed, 4 insertions(+) diff --git a/c/src/lib/libbsp/arm/shared/include/arm-cp15-start.h b/c/src/lib/libbsp/arm/shared/include/arm-cp15-

[PATCH] arm/xilinx_zynq: Disable the MMU and the data and instruction cache on boot.

The u-boot loader can enable the MMU plus the data and instruction caches. Disable them and if the data cache is enabled clear it before turn the caches off. Closes #2774. --- c/src/lib/libbsp/arm/shared/include/arm-cp15-start.h | 4 c/src/lib/libbsp/arm/xilinx-zynq/startup/bspstartmmu.c