Hello,
there is still the licensing issue with this BSP discussed in an earlier thread.
So the BSP (most likely) still can not be included into the main repository.
Anyway it seems to be useful to re-post the last version of the BSP with bug
fixes, some of the suggested improvements and further
On 6/18/2014 9:50 AM, Christian Mauderer wrote:
Hello,
there is still the licensing issue with this BSP discussed in an earlier
thread.
So the BSP (most likely) still can not be included into the main repository.
Anyway it seems to be useful to re-post the last version of the BSP with bug
On 2014-06-17 11:08, Chris Johns wrote:
On 17/06/2014 6:51 pm, Sebastian Huber wrote:
On 2014-06-16 21:56, Chris Johns wrote:
On 14/06/2014 2:00 am, Sebastian Huber wrote:
Module:rtems
Branch:master
Commit:73bf499ce7710ff8e75833042f88d1ff5b3e84fa
Changeset:
Hello,
The GPIO API has been updated with doxygen documentation and code
comments, along with a blog post that explains the current API work flow
[1], and another blog post explaining how the API can be tested using
the Raspberry Pi [2], both containing links to the actual code.
Currently
Hi,
I have updated my blog with series of posts providing information about the
progress of the project, and other tutorials describing how to build
rtems-or1k toolchain, RTEMS kernel and how to run/debug RTEMS from
or1ksim/gdb. If you are interested in the project, you may want to have a
look at
Hi,
I am currently working on rtems-test integration with qemu (especially
couverture-qemu) for pc386 BSP. Up to now pc386 used two approaches:
1. It used pc386_fda floppy image which boots test.exe from the same
directory
tree:
qemu/
hd/
pc386_fda
test.exe
install/
On 6/25/2014 5:48 PM, Chris Johns wrote:
On 26/06/2014 5:56 am, Krzysztof Mięsowicz wrote:
Hi again and sorry for spam. Soon after writing mail to you I found the
solution (at least I think so :-D ).
Thanks for posting the solution. The pc is the only qemu bsp I know of
with a boot loader
On SMP rtems_interrupt_lock_context must be used. Most tests fail with a
NULL pointer exception when exiting, except on NGMP where main memory is
at 0x.
---
c/src/lib/libbsp/sparc/leon3/console/console.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git
Hello,
for SMP support we need atomic operations. We use the ones provided by the C11
and C++11 standards. For this it is necessary to use -std=gnu++11 as a GCC
option since otherwise an include of atomic yields to compile time errors.
Does anyone know how to add this option to the CXXFLAGS
The GCC 4.9 ships its own stdatomic.h which is not C++ compatible.
The suggested solution was to include atomic in case C++ is used.
This works at least with GCC 4.9. See also:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60940
---
I checked this behaviour more, and it seems that when I run test through
rtems-test command and it invokes this qemu-system-i386 command through
execute module, it waits after test completion for key press. When I'm
starting qemu-system-i386... simply from command line or through shell
script,
On Thu, Jun 26, 2014 at 5:26 PM, Chris Johns chr...@rtems.org wrote:
On 27/06/2014 4:09 am, Joel Sherrill wrote:
See pc386/configure.ac for this
RTEMS_BSP_CLEANUP_OPTIONS(1, 1)
dnlargument 1 indicates the default value for BSP_PRESS_KEY_FOR_RESET
dnlargument 2 indicates the
On 06/27/2014 06:25 PM, Joel Sherrill wrote:
I see this as two state changes within a single scheduler
operation but that sounds the same as your double
migration. We are likely replacing heir twice and tripping
the same condition.
If you want a test case of this, we can get our code
cleaned up
On Jun 27, 2014 3:04 PM, Sebastian Huber sebastian.hu...@embedded-brains.de
wrote:
On 06/27/2014 06:25 PM, Joel Sherrill wrote:
I see this as two state changes within a single scheduler
operation but that sounds the same as your double
migration. We are likely replacing heir twice and
---
c/src/lib/libbsp/sparc/leon3/console/console.c | 31 +-
.../libbsp/sparc/leon3/console/printk_support.c| 13 ---
c/src/lib/libbsp/sparc/leon3/include/leon.h| 33
c/src/lib/libbsp/sparc/shared/include/apbuart.h|1 +
Hello everybody,
we have advanced with preparation RTEMS multilib toolchain which
targets Cortex-R in big-endian thumb mode. The required RTEMS ARM
target fragments are included in followup patch.
I have used next configure script options
CFLAGS=-O2 -pipe LDFLAGS=-s \
Is h_args on the stack or in global space when passed into
rtems_interrupt_handler_install?
--jennifer
-Original Message-
From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Andre
Marques
Sent: Monday, June 30, 2014 1:09 PM
To: Gedare Bloom; Wendell Silva
Cc:
On 2014-07-01 16:56, Sebastian Huber wrote:
gcc/ChangeLog
2014-07-01 Sebastian Huber sebastian.hu...@embedded-brains.de
* config/arm/t-rtems-eabi: Add
mthumb/march=armv7-r/mfpu=vfpv3-d16/mfloat-abi=hard,
mbig-endian/mthumb/march=armv7-r, and
PATCHv2: BSP_fatal_exit defined in header
Instead of calling the system call TA instruction directly it
is better paractise to isolate the trap implementation to the
system call functions.
BSP_fatal_exit() is added.
---
c/src/lib/libbsp/sparc/erc32/Makefile.am |1 +
Without the source the error code does not say that much.
Let it be up to the CPU/BSP to determine the error code
reported on fatal shutdown.
This patch does not change the current behaviour, just
adds the option to handle the source of the fatal halt.
---
cpukit/score/cpu/arm/rtems/score/cpu.h
By removing the bsp_reset() mechanism and instead relying on the
CPU_Fatal_halt() routine SMP and single-core can halt by updating
the _Internal_errors_What_happened structure and set the state to
SYSTEM_STATE_TERMINATED (the generic way). This will be better
for test scripts and debugger that can
In order to support older toolchains and LEON3 v7 systems the
-mcpu=leon3 flag can not be used in the LEON3 BSP. The SMP
kernel however requires -mcpu=leon3 for the CAS support only
present in GCC-4.8 and GCC-4.9.
---
.../libbsp/sparc/leon3/make/custom/leon3smp.cfg|8
1 files
Adds functions to request cache operations on a set of cores.
Daniel Cederman (3):
score: Use consistent type for SMP messages
score: Add function to send a SMP message to a set of CPUs
score: Add SMP support to the cache manager
c/src/lib/libcpu/shared/src/cache_manager.c | 166
Adds functions that allows the user to specify which cores that should
perform the cache operation. SMP messages are sent to all the specified
cores and the caller waits until all cores have acknowledged that they
have flushed their cache. Implementation is shown using both function
pointers and
Check that data cache snooping exists and is enabled on all cores.
---
c/src/lib/libbsp/shared/include/fatal.h |1 +
c/src/lib/libbsp/sparc/leon3/include/leon.h | 10 ++
c/src/lib/libbsp/sparc/leon3/startup/bspsmp.c |8 ++--
3 files changed, 17 insertions(+), 2
The flush instruction on LEON flushes both the data and the instruction
cache. Flushing of just the instruction cache can be done by setting
the flush instruction cache bit in the cache control register.
---
c/src/lib/libbsp/sparc/leon3/include/cache_.h |4 +++-
I don't have a problem with this in principle but reviewing
the earlier patches and seeing similar names in other
BSPs makes me wonder if we can't get a better name.
Isn't this really just bsp_reset?
I don't see needing the symbol BSP_fatal_exit().
On 7/3/2014 2:29 AM, Daniel Hellstrom wrote:
On 7/3/2014 2:29 AM, Daniel Hellstrom wrote:
By removing the bsp_reset() mechanism and instead relying on the
CPU_Fatal_halt() routine SMP and single-core can halt by updating
the _Internal_errors_What_happened structure and set the state to
SYSTEM_STATE_TERMINATED (the generic way). This
I don't know why but I don't see any file changes on this.
On 7/3/2014 4:37 AM, Daniel Cederman wrote:
Adds functions to request cache operations on a set of cores.
Daniel Cederman (3):
score: Use consistent type for SMP messages
score: Add function to send a SMP message to a set of CPUs
This is OK.
I assume there are other use cases to justify adding it.
On 7/3/2014 4:37 AM, Daniel Cederman wrote:
Make _SMP_Broadcast_message() use the function to send a message to all CPUs
except itself.
---
cpukit/score/include/rtems/score/smpimpl.h | 10 ++
Comments inline. But mostly the same style comments.
Check that they aren't needed in other places. I didn't
note them everywhere.
On 7/3/2014 4:37 AM, Daniel Cederman wrote:
Adds functions that allows the user to specify which cores that should
perform the cache operation. SMP messages are
I assume this is just fixing the types to match the
assumed prototype.
This needs a comment but if that's the intent, it is
OK.
On 7/3/2014 4:37 AM, Daniel Cederman wrote:
---
cpukit/score/include/rtems/score/smpimpl.h |2 +-
cpukit/score/src/smp.c |2 +-
2 files
On 07/04/2014 08:25 AM, Sebastian Huber wrote:
On 2014-07-03 09:29, Daniel Hellstrom wrote:
By removing the bsp_reset() mechanism and instead relying on the
CPU_Fatal_halt() routine SMP and single-core can halt by updating
the _Internal_errors_What_happened structure and set the state to
On 2014-07-04 11:56, Daniel Cederman wrote:
With this implementation cache routines must not be called from
interrupt context. This should be mentioned in the documentation.
It is extremely difficult to implement it in a way so that it can be
used from interrupt context.
There are
On 2014-07-04 11:56, Daniel Cederman wrote:
I think it is a general bug if you change the trap responsible for the
IPI after the start request of the secondary processors. At which point
does this problem happen currently?
The trap responsible for IPIs is only set before the secondary
On Jul 4, 2014 1:00 PM, Pavel Pisa p...@cmp.felk.cvut.cz wrote:
Hello Sebastian,
On Tuesday 01 of July 2014 16:58:40 Sebastian Huber wrote:
On 2014-07-01 16:56, Sebastian Huber wrote:
gcc/ChangeLog
2014-07-01 Sebastian Huber sebastian.hu...@embedded-brains.de
*
Hi,
When loading an object file which is in an archive file using such a
command dlo tmp.ra:xx.rap, it shows file not found. This patch fix it.
Regards,
Peng.
0001-Fix-colon-problem.patch
Description: Binary data
___
devel mailing list
I had a closer look at the change, and it makes no sense. If you look at
void _SMP_Send_message( uint32_t cpu_index, unsigned long message )
{
Per_CPU_Control *cpu = _Per_CPU_Get_by_index( cpu_index );
_Atomic_Fetch_or_ulong( cpu-message, message, ATOMIC_ORDER_RELAXED );
I think instruction cache operations scoped by processors make no sense on SMP.
Every processor should have the same view to the instruction memory.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189
Add a new low-level device API to Termios that passes the TTY structure
to the low-level device functions. This greatly simplifies the
low-level device drivers since they are no longer forced to derive their
private data from the minor number.
It makes it possible to use the TTY low-level lock
From: Christian Mauderer christian.maude...@embedded-brains.de
---
.../libbsp/sparc/leon3/console/printk_support.c| 51
c/src/lib/libbsp/sparc/leon3/include/leon.h| 19 ---
.../libbsp/sparc/shared/include/apbuart_termios.h | 19 +++
Hi,
On Tue, Jul 8, 2014 at 3:19 PM, Jennifer Averett
jennifer.aver...@oarcorp.com wrote:
The attached patches are a starting point for discussions for adding capture
support
to core objects. We started to write notes based on our discussions but the
text
was harder to follow than just
On 7/9/2014 10:34 AM, Gedare Bloom wrote:
On Tue, Jul 8, 2014 at 5:37 PM, Joel Sherrill joel.sherr...@oarcorp.com
wrote:
Hi
If you take the patches in their entirety, most of the tests
appear to be about 500 bytes smaller on the erc32.
What is the change in wkspace size? Basically you
When a thread is removed from a thread queue or is unblocked
by receiving an event, the same actions are required.
+ timeout watchdog canceled,
+ thread must be unblocked, and
+ (MP only) proxy cleaned up
This patch makes sure there is only one copy of this code.
---
OK Sebastian, Thank you very much!
On Thu, Jul 10, 2014 at 11:53 AM, Sebastian Huber
sebastian.hu...@embedded-brains.de wrote:
On 2014-07-10 16:43, Gabriel Ibarra wrote:
Hello, I'm working with a board with a few amount of RAM (lpc1768- 32k), I
recently updated the last version of RTEMS
On 7/10/2014 9:53 AM, Sebastian Huber wrote:
On 2014-07-10 16:43, Gabriel Ibarra wrote:
Hello, I'm working with a board with a few amount of RAM (lpc1768- 32k), I
recently updated the last version of RTEMS and now I have more overhead, I
found that the responsible of this new overhead is an
From: Joel Sherrill joel.sherr...@oarcorp.com
---
IGNORE ME
--
1.7.1
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Use of the cenable command was resulting in a lock in
rtems_interrupt_lock_acquire due to nesting.
---
cpukit/libmisc/capture/capture.c | 39 ++-
1 file changed, 22 insertions(+), 17 deletions(-)
diff --git a/cpukit/libmisc/capture/capture.c
---
testsuites/libtests/Makefile.am | 1 +
testsuites/libtests/capture01/Makefile.am | 20 +++
testsuites/libtests/capture01/capture01.doc | 19 +++
testsuites/libtests/capture01/capture01.scn | 35
testsuites/libtests/capture01/init.c| 253
On 10/07/2014 6:09 pm, Sebastian Huber wrote:
Hello Jennifer,
I am about to go on vacation so I can only give some short comments.
Have fun.
This patch looks a bit like approach of the Timeline Tool from Edisoft:
http://lists.rtems.org/pipermail/users/2007-October/017112.html
I am more
On 2014-07-11 04:08, Chris Johns wrote:
On 10/07/2014 11:44 pm, Jennifer Averett wrote:
Use of the cenable command was resulting in a lock in
rtems_interrupt_lock_acquire due to nesting.
I am rejecting this change. RTEMS as an RTOS should provide support to handle
this case in a consistent
On 2014-07-11 09:12, Daniel Cederman wrote:
+BSP_fatal_exit(
LEON3_FATAL_INVALID_CACHE_CONFIG_SECONDARY_PROCESSOR );
bsp_fatal()?
I wanted to use bsp_fatal, but it tries to acquire a ticket lock which does not
work when data cache snooping is disabled.
Ok, can you please add this
On 2014-07-09 16:40, Gedare Bloom wrote:
On Wed, Jul 9, 2014 at 3:02 AM, Daniel Cederman ceder...@gaisler.com wrote:
The flush instruction on LEON flushes both the data and the instruction
cache. Flushing of just the instruction cache can be done by setting
the flush instruction cache bit in
+BSP_fatal_exit(
LEON3_FATAL_INVALID_CACHE_CONFIG_SECONDARY_PROCESSOR );
bsp_fatal()?
I wanted to use bsp_fatal, but it tries to acquire a ticket lock which
does not work when data cache snooping is disabled.
On 2014-07-09 09:28, Sebastian Huber wrote:
On 2014-07-09 09:02, Daniel
I'm currently working on adding tests. Thank you for your other comments!
On 2014-07-09 09:41, Sebastian Huber wrote:
The new cache manager functions should have tests, see also
http://git.rtems.org/rtems/tree/testsuites/sptests/spcache01/init.c
On 2014-07-09 09:02, Daniel Cederman wrote:
---
doc/bsp_howto/console.t | 716 ++-
1 files changed, 331 insertions(+), 385 deletions(-)
diff --git a/doc/bsp_howto/console.t b/doc/bsp_howto/console.t
index 555cf04..e35ca36 100644
--- a/doc/bsp_howto/console.t
+++ b/doc/bsp_howto/console.t
@@
I've been developing code just fine running in SRAM with the current head. I
just tried to run out of flash. My software put the program in flash just
fine, but it doesn't run, it winds up in the BAM code trying to boot off the
serial port / CAN.
The difference between SRAM and FLASH is only
I think today or yesterday is a suitable tag.
Pavel is the arm fix in Newlib CVS?
We can bump it again when openrisc code is merged.
Sebastian did you want a GCC bump also?
On Jul 10, 2014 9:26 PM, Chris Johns chr...@rtems.org wrote:
On 9/07/2014 2:40 am, Joel Sherrill wrote:
On 7/8/2014
This test verifies that affinity is honored when set prior to task start.
---
testsuites/smptests/Makefile.am| 1 +
testsuites/smptests/configure.ac | 1 +
testsuites/smptests/smpschedaffinity01/Makefile.am | 19 +++
This task walks the affinity of self across all the cores.
---
testsuites/smptests/Makefile.am| 1 +
testsuites/smptests/configure.ac | 1 +
testsuites/smptests/smpschedaffinity03/Makefile.am | 19
testsuites/smptests/smpschedaffinity03/init.c
This test verifies priority is inherited from a high priority
semaphore by a lower priority task.
---
testsuites/smptests/Makefile.am| 1 +
testsuites/smptests/configure.ac | 1 +
testsuites/smptests/smpschedsem01/Makefile.am | 19 +
On a long weekend but is there a chance Jennifer missed using something like
rtems_test_assert which also ensures that the call exited OS critical sections?
On Jul 12, 2014 9:35 AM, Ben Gras b...@shrike-systems.com wrote:
All,
After a rebase of my tree capture01 didn't build (see
All,
This patch is submitted as its values are used in my to-be-submitted
beagle bsp.
---
c/src/lib/libbsp/shared/include/uart-output-char.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/c/src/lib/libbsp/shared/include/uart-output-char.h
Hi,
When the first time executing such a command dlo libxx.ra:yy.rap or dlo
libxx.a:yy.o, RTL complains no format loader found. when executing the
command the second time, the archive files can be loaded correctly. It is
because cache flush uses `file_size = -1` while file_size is unsigned type
,
Check that data cache snooping exists and is enabled on all cores.
---
c/src/lib/libbsp/shared/include/fatal.h |2 ++
c/src/lib/libbsp/sparc/leon3/include/leon.h | 10 ++
c/src/lib/libbsp/sparc/leon3/startup/bspsmp.c | 14 --
3 files changed, 24 insertions(+),
Invokes SMP cache management routines under different scenarios.
---
testsuites/smptests/Makefile.am |1 +
testsuites/smptests/configure.ac |1 +
testsuites/smptests/smpcache01/Makefile.am| 19 ++
testsuites/smptests/smpcache01/init.c | 291
Ok great. Yes it was gsoc and the commit mentions it.
On Jul 14, 2014 8:10 PM, Joel Sherrill joel.sherr...@oarcorp.com wrote:
On Jul 14, 2014 12:27 PM, Ben Gras b...@shrike-systems.com wrote:
Dear all,
I'm pretty close to be able to submit an initial version of the Beagle*
bsp. I'm
On 14/07/2014 11:23 pm, Peng Fan wrote:
When the first time executing such a command dlo libxx.ra:yy.rap or
dlo libxx.a:yy.o, RTL complains no format loader found. when
executing the command the second time, the archive files can be loaded
correctly. It is because cache flush uses `file_size =
Just passing along.
Sebastian had two patches he wanted to see on the 4.9 branch and
gcc head.
Are there any others?
What issues do we have moving to a 4.9.x release? I recall there being
code generation issues but not the details.
Original Message
Subject:GCC 4.9.1
On 17/07/2014 6:25 am, Joel Sherrill wrote:
Hi
sys/cdefs.h in the nios2 tools is too old to build the current RTEMS.
Newer versions provide __DEVOLATILE
Support is in 4.9.x but it is lacking the RTEMS specifics to allow us to
built it.
On 17/07/2014 12:46 am, Joel Sherrill wrote:
Just passing along.
Sebastian had two patches he wanted to see on the 4.9 branch and
gcc head.
Are there any others?
What issues do we have moving to a 4.9.x release? I recall there being
code generation issues but not the details.
I think there
On 17/07/2014 8:47 am, Joel Sherrill wrote:
On 7/16/2014 5:27 PM, Chris Johns wrote:
On 17/07/2014 6:25 am, Joel Sherrill wrote:
Hi
sys/cdefs.h in the nios2 tools is too old to build the current RTEMS.
Newer versions provide __DEVOLATILE
Support is in 4.9.x but it is lacking the RTEMS
Hi,
I am trying to get ticker.exe working properly for or1ksim BSP but
there is a problem. When I run ticker, I only get the following output
*** BEGIN OF TEST CLOCK TICK ***
TA1 - rtems_clock_get_tod - 09:00:00 12/31/1988
TA2 - rtems_clock_get_tod - 09:00:00 12/31/1988
TA3 -
-Original Message-
From: devel [mailto:devel-boun...@rtems.org] On Behalf Of Hesham
Moustafa
Sent: Thursday, July 17, 2014 4:58 AM
To: rtems-de...@rtems.org
Subject: Problem with ticker.exe for or1ksim/OpenRISC BSP
Hi,
I am trying to get ticker.exe working properly for
On 7/17/2014 4:57 AM, Hesham Moustafa wrote:
Hi,
I am trying to get ticker.exe working properly for or1ksim BSP but
there is a problem. When I run ticker, I only get the following output
*** BEGIN OF TEST CLOCK TICK ***
TA1 - rtems_clock_get_tod - 09:00:00 12/31/1988
TA2 -
---
gcc/ChangeLog| 6 ++
gcc/config.gcc | 6 +-
gcc/config/nios2/rtems.h | 33 +
gcc/config/nios2/t-rtems | 3 +++
4 files changed, 47 insertions(+), 1 deletion(-)
create mode 100644 gcc/config/nios2/rtems.h
create mode 100644
Hi
Just posted a gcc patch for gcc's head which should work with 4.9.x.
Feedback appreciated. Hopefully Chris can add this to the RSB.
Based on that toolset, there are two tests that fail to build.
spcache01
tmcontext01
Both are related to missing cache functions. Crunching the log gives
this
Hello Joel,
why don't you use this patch, which contains also a bunch of useful
multilibs?
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg02124.html
On 07/17/2014 08:35 PM, Joel Sherrill wrote:
---
gcc/ChangeLog| 6 ++
gcc/config.gcc | 6 +-
Make RSB download newlib-cvs for or1k targets as OpenRISC
support has been added to newlib recently; thus, newlib-2.1 release
and its or1k support patch is not used anymore.
---
rtems/config/4.11/rtems-or1k.bset | 5 +
rtems/config/tools/rtems-gcc-4.8.2-newlib-cvs-1.cfg | 2
Hi André,
I have a couple of SPI devices to try now. I have the SPI FRAM chip:
https://www.adafruit.com/product/1897
and something that could be interesting, an SPI based LCD/touchscreen:
https://www.adafruit.com/products/1601
I can also verify that the RTEMS BSP works fine on the new Raspberry
On Fri, Jul 18, 2014 at 1:35 AM, Hesham Moustafa
heshamelmat...@gmail.com wrote:
On Thu, Jul 17, 2014 at 3:10 PM, Joel Sherrill
joel.sherr...@oarcorp.com wrote:
This definitely sounds like not handling the context switch necessary
part of the
IRQ processing properly so always returning to
On Fri, Jul 18, 2014 at 11:37 AM, Philipp Eppelt
philipp.epp...@mailbox.tu-dresden.de wrote:
---
This is an updated version of an earlier unmerged patch, which extends the
cpukit/score/cpu/i386/ model with guards to distinguish between
paravirtualized (--enable-paravirt) and native
The ASM macro needs to be properly used in rtems/score/cpu.h.
I sent a patch to devel@ but it is really a hack. Things compile but
I wouldn't trust it.
+ ASM should protect C only code from being used in .S code.
And vice-versa.
When I started, there was C code exposed to .S. When I blocked
Hi, I have a simple loopback program in my board (bsp lpc_176x), It reads
information from a tty and returns it through the same tty (using POSIX
functions), I tested it sending characters with a PC's terminal and I saw
the ECHO on the terminal, I found an unusual behavior with some bsp
Either account for it in workspace sizing or use malloc.
On principle, I guess any dynamic allocated memory that isn't mandatory to
get RTEMS to work should come from malloc.
-Gedare
On Mon, Jul 21, 2014 at 10:41 AM, Jennifer Averett
jennifer.aver...@oarcorp.com wrote:
The capture engine
On July 21, 2014 10:44:15 AM CDT, Gedare Bloom ged...@rtems.org wrote:
Either account for it in workspace sizing or use malloc.
On principle, I guess any dynamic allocated memory that isn't mandatory
to get RTEMS to work should come from malloc.
With one malloc and two workspace allocates, I
---
cpukit/score/include/rtems/score/rbtree.h | 11 +--
cpukit/score/src/rbtreeextract.c | 3 ---
testsuites/sptests/sprbtree01/init.c | 5 +
3 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/cpukit/score/include/rtems/score/rbtree.h
---
cpukit/score/include/rtems/score/rbtree.h | 7 +++
cpukit/score/src/rbtree.c | 3 ---
cpukit/score/src/rbtreeextract.c | 10 --
cpukit/score/src/rbtreeinsert.c | 3 ---
testsuites/sptests/sprbtree01/init.c | 3 ---
5 files changed, 3
---
cpukit/score/src/rbtree.c| 7 +-
cpukit/score/src/rbtreeextract.c | 152 +--
cpukit/score/src/rbtreefind.c| 7 +-
cpukit/score/src/rbtreeinsert.c | 69 ++
cpukit/score/src/rbtreeiterate.c | 12 ++--
There could be something wrong here but I don't see it on a quick review.
On 7/21/2014 11:31 AM, Sebastian Huber wrote:
---
cpukit/score/src/rbtree.c| 7 +-
cpukit/score/src/rbtreeextract.c | 152
+--
cpukit/score/src/rbtreefind.c| 7 +-
On 07/21/2014 07:23 PM, Joel Sherrill wrote:
Unless the chain has changed to have the property of
dangerous to extract if not on, this should be OK.
My thinking is that higher level code would be checking a state
of some sort and know whether to extract from the underlying
chain or rbtree
On 7/21/2014 12:54 PM, Sebastian Huber wrote:
On 07/21/2014 07:23 PM, Joel Sherrill wrote:
Unless the chain has changed to have the property of
dangerous to extract if not on, this should be OK.
My thinking is that higher level code would be checking a state
of some sort and know whether to
This change is necessary to support Cortex-M4 and Cortex-R based chips
in RTEMS.
This patch should be applied to GCC 4.8, 4.9 and mainline. I do not
have write access, so in case this gets approved, please commit it for
me.
gcc/ChangeLog
2014-07-21 Sebastian Huber
One issue with rbtree formatting is in some places if/while conditional
expressions are put on the same line as the conditional statement. We
should prefer to put them explicitly on separate lines, since that is the
prevailing style of score and I have added such a convention to our style
wiki
On 07/21/2014 10:23 PM, Gedare Bloom wrote:
One issue with rbtree formatting is in some places if/while conditional
expressions are put on the same line as the conditional statement. We
should prefer to put them explicitly on separate lines, since that is the
prevailing style of score and I have
On 07/21/2014 10:23 PM, Gedare Bloom wrote:
/* TODO: Error message? */
- if (!the_rbtree) return;
+ if ( !the_rbtree ) return;
Like here.
Ok, this is not an uncrustify bug. It was already a one-liner (like the
other). Unfortunately there is no option to wipe out one-liner.
--
The test sptests/sp35 showed a NULL pointer access due to an invalid
maximum node field (e.g. a tree with one element and NULL as the maximum
node).
---
cpukit/score/include/rtems/score/rbtree.h| 16 ++--
cpukit/score/src/rbtreeinsert.c | 4 +-
Thanks, I have added a section at
http://www.rtems.org/wiki/index.php/Coding_Conventions#Tools and
uploaded/linked to your configuration.
-Gedare
On Tue, Jul 22, 2014 at 6:32 AM, Sebastian Huber
sebastian.hu...@embedded-brains.de wrote:
On 07/22/2014 12:22 PM, Sebastian Huber wrote:
On
Hi,
we are working in a very RAM constrained board, and noticed that
some symbols could be moved to ROM by declaring them const.
I have a slight idea about creating a consts-candidate detector tool
KICS! (Keep It Const, St.! :) ), and wanted to hear some other
people ideas.
Initial thoughts:
On 7/22/2014 1:05 PM, Daniel Gutson wrote:
Hi,
we are working in a very RAM constrained board, and noticed that
some symbols could be moved to ROM by declaring them const.
Have you been through the configure options like switching scheduler,
lowering
stack sizes, etc.?
I have a slight
1 - 100 of 35902 matches
Mail list logo
