On 17.01.23 03:48, Chris Johns wrote:
On 16/1/2023 6:56 pm, Sebastian Huber wrote:
On 16.01.23 01:35, Chris Johns wrote:
On 13/1/2023 1:54 am, Sebastian Huber wrote:
On 12.01.23 15:44, Kinsey Moore wrote:
The other two patches look fine to me. The use of dump() that results in this
patch
On 16/1/2023 6:56 pm, Sebastian Huber wrote:
> On 16.01.23 01:35, Chris Johns wrote:
>> On 13/1/2023 1:54 am, Sebastian Huber wrote:
>>> On 12.01.23 15:44, Kinsey Moore wrote:
The other two patches look fine to me. The use of dump() that results in
this
patch does several things:
On Mon, Jan 16, 2023 at 2:47 PM Sebastian Huber
wrote:
>
> On 16.01.23 07:33, Zhu Zhongjie wrote:
> > From: Zhongjie Zhu
> >
> > when Acquires an ISR lock in SMP system, it first call _ISR_Local_disable()
> > to disable ISR, this is the same with in UP system, so we could
> > use the same
On Mon, Jan 16, 2023 at 8:46 AM Frank Kühndel <
frank.kuehn...@embedded-brains.de> wrote:
> Hi Chris,
>
> On 1/16/23 01:02, Chris Johns wrote:
> > Subject:
> > Re: [PATCH 1/1] RSB: Mitigate too short error reports
> > From:
> > Chris Johns
> > Date:
> > 1/16/23, 01:02
> >
> > To:
> > Frank
Hi Chris,
On 1/16/23 01:02, Chris Johns wrote:
Subject:
Re: [PATCH 1/1] RSB: Mitigate too short error reports
From:
Chris Johns
Date:
1/16/23, 01:02
To:
Frank Kühndel , devel@rtems.org
On 22/12/2022 9:09 pm, Frank Kühndel wrote:
On 12/21/22 00:06, Chris Johns wrote:
On 21/12/2022 3:44 am,
On 16.01.23 10:38, 朱忠杰 wrote:
with RTEMS_SMP or RTEMS_PROFILING defined, it will call
_Thread_Dispatch_disable_critical( _context )
only in UP system with RTEMS_PROFILING not defined, it will call
_Thread_Dispatch_disable_critical( NULL ), in this case, the real
function use the lock_context is
Allow users to optionally use the CI from github.
---
.github/actions/build-bsps/action.yml| 49
.github/actions/run-simulator/action.yml | 144 +++
.github/workflows/bsps.yml | 63 ++
.github/workflows/simulator.yml | 72
Mark all new pull requests as stale. Add a note that the CI can be used
but that patches should be sent to the mailing list instead. Close pull
requests after 30 days.
---
.github/workflows/mark-stale.yml | 23 +++
1 file changed, 23 insertions(+)
create mode 100644
Allow users to optionally use the GitHub CI.
---
.github/workflows/toolchain.yml | 196
1 file changed, 196 insertions(+)
create mode 100644 .github/workflows/toolchain.yml
diff --git a/.github/workflows/toolchain.yml b/.github/workflows/toolchain.yml
new file
Mark all new pull requests as stale. Add a note that the CI can be used
but that patches should be sent to the mailing list instead. Close pull
requests after 30 days.
---
.github/workflows/mark-stale.yml | 23 +++
1 file changed, 23 insertions(+)
create mode 100644
Hello,
some weeks ago I created a GitHub Actions based CI script that we
(embedded brains) wanted to use to test patches (see
https://github.com/embedded-brains/rtems/tree/ci). I don't think much of
the RTEMS community noted these. I would like to suggest adding the
scripts to the official RTEMS
with RTEMS_SMP or RTEMS_PROFILING defined, it will call
_Thread_Dispatch_disable_critical( _context )
only in UP system with RTEMS_PROFILING not defined, it will call
_Thread_Dispatch_disable_critical( NULL ), in this case, the real
function use the lock_context is
On 16.01.23 09:36, Zhu Zhongjie wrote:
From: Zhongjie Zhu
there are different cases for _ISR_lock_ISR_disable() and _ISR_lock_ISR_enable()
in the case RTEMS_SMP is defined or RTEMS_PROFILING is defined, so remove the
related code.
../../../cpukit/include/rtems/score/threaddispatch.h: In
From: Zhongjie Zhu
there are different cases for _ISR_lock_ISR_disable() and _ISR_lock_ISR_enable()
in the case RTEMS_SMP is defined or RTEMS_PROFILING is defined, so remove the
related code.
../../../cpukit/include/rtems/score/threaddispatch.h: In function
'_Thread_Dispatch_disable':
14 matches
Mail list logo
