Re: [PATCH v2] rtems: Add rtems_interrupt_server_create()

On Fri, Jul 31, 2020 at 5:53 PM Chris Johns wrote: > > OK for the 5 branch. > > Will there be an update to the configuration section in the Classic API > manual? > https://devel.rtems.org/ticket/3269 Seb: "It is on my TODO list to document it in the RTEMS Classic API Guide." > On 1/8/20 2:10 am

Python script distribution standardisation

Hello, I have opened .. https://devel.rtems.org/ticket/4037 to discuss the shell wrappers for python script in the RSB and Tools. Comments are welcome. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v2] rtems: Add rtems_interrupt_server_create()

OK for the 5 branch. Will there be an update to the configuration section in the Classic API manual? On 1/8/20 2:10 am, Sebastian Huber wrote: > Add rtems_interrupt_server_destroy(). > > Before this patch, the only way to create interrupt servers was > rtems_interrupt_server_initialize(). This f

Re: BSP for pico and microzed

On 1/8/20 6:35 am, Christian Mauderer wrote: > On 31/07/2020 22:26, Joel Sherrill wrote: > first a confirmation from my side: I had to do with a customer board > that used a Picozed 7030 just recently. It worked well. If you need a > more detailed configure line, I can look it up. I tend to agree.

Re: BSP for pico and microzed

On 31/07/2020 22:26, Joel Sherrill wrote: > > > On Fri, Jul 31, 2020 at 3:04 PM Jonathan Brandmeyer > mailto:jbrandme...@planetiq.com>> wrote: > > On Fri, Jul 31, 2020 at 11:43 AM Joel Sherrill > wrote: > > Hi > > Do any of the existing Zynq vari

Re: BSP for pico and microzed

On Fri, Jul 31, 2020 at 3:04 PM Jonathan Brandmeyer < jbrandme...@planetiq.com> wrote: > On Fri, Jul 31, 2020 at 11:43 AM Joel Sherrill wrote: > >> Hi >> >> Do any of the existing Zynq variants work on those? I recall posts about >> using them but not which variant was used. >> > > The zedboard B

Re: GSoC 2020: OFW Import To RTEMS License Issue

On Fri, Jul 31, 2020 at 2:16 PM Niteesh G. S. wrote: > Hello, > > In a recent review of these patches > https://lists.rtems.org/pipermail/devel/2020-July/060653.html > Gedare mentioned that we cannot use these patches with the > current license. More details regarding the conversation can be > fo

Re: BSP for pico and microzed

On Fri, Jul 31, 2020 at 11:43 AM Joel Sherrill wrote: > Hi > > Do any of the existing Zynq variants work on those? I recall posts about > using them but not which variant was used. > The zedboard BSP works as-is on the microzed. However, you almost certainly want to set BSP_ZYNQ_RAM_LENGTH=1024

GSoC 2020: OFW Import To RTEMS License Issue

Hello, In a recent review of these patches https://lists.rtems.org/pipermail/devel/2020-July/060653.html Gedare mentioned that we cannot use these patches with the current license. More details regarding the conversation can be found in the following archive. https://lists.rtems.org/pipermail/deve

Re: [PATCH] Strict thread-stack isolation and thread-stack sharing.

On Fri, Jul 31, 2020 at 11:13 AM Utkarsh Rai wrote: > > This patch provides thread-stack isolation and thread-stack sharing > mechanism for a POSIX thread. > > - Thread stacks are isolated with read-only permission. > - We use mmap, shm_open for thread-stack sharing. For mechanism of > thread-st

BSP for pico and microzed

Hi Do any of the existing Zynq variants work on those? I recall posts about using them but not which variant was used. Are there any other common board variants known to work? Thanks. --joel ___ devel mailing list devel@rtems.org http://lists.rtems.or

[PATCH] Strict thread-stack isolation and thread-stack sharing.

This patch provides thread-stack isolation and thread-stack sharing mechanism for a POSIX thread. - Thread stacks are isolated with read-only permission. - We use mmap, shm_open for thread-stack sharing. For mechanism of thread-stack sharing please refer to the related test. --- .../realview-pb

Re: [PATCH v2] rtems: Add rtems_interrupt_server_create()

This looks fine to apply to 5 to me. Maybe give it a day in case someone else wants to complain. On Fri, Jul 31, 2020 at 10:10 AM Sebastian Huber wrote: > > Add rtems_interrupt_server_destroy(). > > Before this patch, the only way to create interrupt servers was > rtems_interrupt_server_initializ

[PATCH v2] rtems: Add rtems_interrupt_server_create()

Add rtems_interrupt_server_destroy(). Before this patch, the only way to create interrupt servers was rtems_interrupt_server_initialize(). This function creates the default interrupt server and in SMP configurations additional interrupt servers for the additional processors. The interrupt server i

Re: [PATCH 1/1] rtems: Add rtems_interrupt_server_build()

On 31/07/2020 17:27, Gedare Bloom wrote: reviewing for feature on 5/ On Fri, Jul 31, 2020 at 5:43 AM Sebastian Huber wrote: Add rtems_interrupt_server_destroy(). Before this patch, the only way to create interrupt servers was rtems_interrupt_server_initialize(). This function creates the def

Re: Thread 2: Need help in understanding exisiting RTEMS code

On Fri, Jul 31, 2020 at 5:48 AM Richi Dubey wrote: > > Thank you for your answer. I learned ack today and it is coming pretty handy > along with cscope. > Note that 'grep' is more reliable, but takes a bit more time to run. 'ack' filters the files that it checks, so it can miss things sometimes.

Re: [PATCH 1/1] rtems: Add rtems_interrupt_server_build()

I think it is OK to add to 5, since it is an extension to an undocumented API ;) On Fri, Jul 31, 2020 at 9:27 AM Gedare Bloom wrote: > > reviewing for feature on 5/ > > On Fri, Jul 31, 2020 at 5:43 AM Sebastian Huber > wrote: > > > > Add rtems_interrupt_server_destroy(). > > > > Before this patc

Re: [PATCH 1/1] rtems: Add rtems_interrupt_server_build()

reviewing for feature on 5/ On Fri, Jul 31, 2020 at 5:43 AM Sebastian Huber wrote: > > Add rtems_interrupt_server_destroy(). > > Before this patch, the only way to create interrupt servers was > rtems_interrupt_server_initialize(). This function creates the default > interrupt server and in SMP c

Re: [PATCH 1/1] rtems: Add rtems_interrupt_server_build()

I think the name should be changed to rtems_interrupt_server_create() instead of rtems_interrupt_server_build() for a future compatibility with rtems_task_build(): https://devel.rtems.org/ticket/3959 ___ devel mailing list devel@rtems.org http://list

Re: Thread 2: Need help in understanding exisiting RTEMS code

Thank you for your answer. I learned ack today and it is coming pretty handy along with cscope. On Thu, Jul 30, 2020 at 9:32 PM Gedare Bloom wrote: > On Thu, Jul 30, 2020 at 7:30 AM Richi Dubey wrote: > > > > I request someone to help me with my earlier question: > https://lists.rtems.org/piper

Re: Need help in understanding some of the existing code in RTEMS

> > It was difficult to find this mail. Descriptive subjects would be helpful. Thank you for your efforts. I understand. Here are important scheduler-specific macros: > https://git.rtems.org/rtems/tree/cpukit/include/rtems/scheduler.h#n131 Exactly what I was looking for! Thanks. On Thu, Jul 30,

[PATCH 2/2] irqs01/smpirqs01: New tests

Close #4034. --- spec/build/testsuites/libtests/grp.yml | 2 + spec/build/testsuites/libtests/irqs01.yml| 19 ++ spec/build/testsuites/smptests/grp.yml | 2 + spec/build/testsuites/smptests/smpirqs01.yml | 20 ++ testsuites/libtests/irqs01/init.c| 294

[PATCH 0/2] Add custom interrupt servers with tests

This patch set is intended for the master branch. It adds two test programs using the new build system as an example. Sebastian Huber (2): rtems: Add rtems_interrupt_server_build() irqs01/smpirqs01: New tests bsps/shared/irq/irq-server.c | 360 +-- cpukit/inc

[PATCH 1/2] rtems: Add rtems_interrupt_server_build()

Add rtems_interrupt_server_destroy(). Before this patch, the only way to create interrupt servers was rtems_interrupt_server_initialize(). This function creates the default interrupt server and in SMP configurations additional interrupt servers for the additional processors. The interrupt server i

[PATCH 1/1] rtems: Add rtems_interrupt_server_build()

Add rtems_interrupt_server_destroy(). Before this patch, the only way to create interrupt servers was rtems_interrupt_server_initialize(). This function creates the default interrupt server and in SMP configurations additional interrupt servers for the additional processors. The interrupt server i

[PATCH 0/1] Add custom interrupt servers

This patch is intended for the RTEMS 5 release branch. Even though it adds a new feature I think it is important to add. It fixes a real application issue with libbsd and an UART over SPI. Sebastian Huber (1): rtems: Add rtems_interrupt_server_build() bsps/shared/irq/irq-server.c | 36