---
bsps/arm/imx/spi/imx-ecspi.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/bsps/arm/imx/spi/imx-ecspi.c b/bsps/arm/imx/spi/imx-ecspi.c
index 26ba812f62..4732b84713 100644
--- a/bsps/arm/imx/spi/imx-ecspi.c
+++ b/bsps/arm/imx/spi/imx-ecspi.c
@@ -350,6 +350,9 @@
From: Joel Sherrill
---
.../gdbmbsim/startup/_hw_exception_handler.S | 38 +
cpukit/score/cpu/microblaze/cpu.c | 168 +++
cpukit/score/cpu/microblaze/rtems/asm.h | 125 ++
cpukit/score/cpu/microblaze/rtems/score/cpu.h | 1263 +
.../cpu/microblaze/rtems/scor
Hi,
This patch set adds support for the MicroBlaze architecture along with
a basic BSP based on Xilinx's KCU105 PetaLinux BSP configuration.
The initial architecture port was started 6 or 7 years ago, I believe.
To make authorship clear and preserve file history, the work is broken
up into three
From: Hesham ALMatary
---
.../microblaze_fpga/console/console-io.c | 74 +
.../microblaze/microblaze_fpga/include/bsp.h | 48 ++
.../microblaze/microblaze_fpga/include/tm27.h | 48 ++
.../microblaze/microblaze_fpga/start/start.S | 109 +
.../startup/_excepti
You also might separate the exception manager addition away from the
topic of recoverable exceptions. This introduces/extends the classic
API, so it needs to be vetted carefully. Although the new header
claims to be a classic API, it appears to not follow classic API
conventions. You might need to
If the rest of the patch set isn't ready, please split this out for
separate submission. It looks fine to me.
On Wed, Sep 22, 2021 at 6:17 PM Kinsey Moore wrote:
>
> All other architectures use uint32_t for interrupt levels and there is
> no reason not to do so on AArch64.
> ---
> cpukit/score/c
looks ok to me.
On Thu, Sep 23, 2021 at 1:05 PM Kinsey Moore wrote:
>
> Context validation for AArch64 was ported from the ARM implementation
> without a reinterpretation of the actual requirements. The spcontext01
> test just happened to pass because the set of scratch registers in ARM
> is a su
Joel, i think the patch looks good.
On Fri, Sep 24, 2021 at 6:19 PM zack leung wrote:
>
> bump
>
>
> On Thu, 23 Sept 2021 at 00:21, zack leung wrote:
>>
>> I can send an example of the exception if you want.
>>
>> zack
>>
>> On Wed, 22 Sept 2021 at 18:01, Gedare Bloom wrote:
>>>
>>> Joel,
>>>
>
ok
On Thu, Sep 30, 2021 at 5:51 AM Sebastian Huber
wrote:
>
> This function was unused. It was a relict of the thread queue rework done
> during the SMP support development. In an early stage, the extract operation
> was called with a NULL thread queue. However, this is no longer the case.
>
On Fri, Sep 24, 2021 at 12:22 PM Sebastian Huber
wrote:
>
> Replace the boolen return value with the new enum
> Thread_queue_Deadlock_status. This improves the code readability.
> Improve documentation. Shorten function names.
> ---
> cpukit/include/rtems/score/threadqimpl.h | 50 ++
This looks ok
On Wed, Sep 29, 2021 at 11:40 PM Sebastian Huber
wrote:
>
> On 23/09/2021 07:38, Sebastian Huber wrote:
> > For uniprocessor configurations, this patch removes dead code in the
> > _Thread_queue_Surrender() and _Thread_queue_Surrender_priority_ceiling()
> > functions.
> >
> > Dead c
Hi
I need to produce a small test case but on the way to realizing the
IDLE task stacks needed to be allocated special, I tripped across a
problem where the computed workspace needed size was so low, it
tripped the second condition in the error check in
_Heap_Get_first_and_last_block:
if (
h
Change size of kEmptyThreadName from THREAD_API_COUNT to
THREAD_NAME_SIZE.
Closes #4519
---
trace/record/record-main-lttng.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/trace/record/record-main-lttng.cc
b/trace/record/record-main-lttng.cc
index 7cfa48c..faa762d 100644
--
On Thu, Sep 30, 2021 at 12:39 AM Sebastian Huber
wrote:
>
> On 30/09/2021 00:43, Joel Sherrill wrote:
> > Hi
> >
> > In Feb 2020, idle thread stack memory was changed to be statically
> > allocated which is good for most RTEMS deployments. However, it is
> > broken when you REALLY need it to be al
This function was unused. It was a relict of the thread queue rework done
during the SMP support development. In an early stage, the extract operation
was called with a NULL thread queue. However, this is no longer the case. The
extract operation is only called if we have a non-NULL thread queu
Hi Chris,
Am 30.09.21 um 02:23 schrieb Chris Johns:
On 29/9/21 6:38 pm, Christian MAUDERER wrote:
To be honest: If sponsored work is a legal problem, we have that with or without
a note in the files. It's only more visible with a note in the files. I don't
think that a legal problem would be a
16 matches
Mail list logo