From: Zhongjie Zhu
Fast Idle is not supported in SMP and n ISRs per tick, so move the code
into the normal clock driver, make this more clearly.
---
bsps/shared/dev/clock/clockimpl.h | 119 +-
1 file changed, 51 insertions(+), 68 deletions(-)
diff --git
From: Ryan Long
---
.../microblaze_fpga/include/bsp/intc.h| 2 --
bsps/microblaze/microblaze_fpga/irq/irq.c | 36 ++-
2 files changed, 19 insertions(+), 19 deletions(-)
diff --git a/bsps/microblaze/microblaze_fpga/include/bsp/intc.h
From: Ryan Long
---
.../microblaze_fpga/console/console-io.c | 19 ++--
.../microblaze_fpga/console/debug-io.c| 29 +++
bsps/microblaze/shared/dev/serial/uartlite.c | 9 +-
3 files changed, 49 insertions(+), 8 deletions(-)
diff --git
From: Ryan Long
---
bsps/microblaze/microblaze_fpga/fs/jffs2_qspi.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/bsps/microblaze/microblaze_fpga/fs/jffs2_qspi.c
b/bsps/microblaze/microblaze_fpga/fs/jffs2_qspi.c
index 39328b6b7c..49859a03f1 100644
---
This allows drivers to read configuration data from the device tree if
the BSP is built with device tree support.
---
.../include/bsp/microblaze-fdt-support.h | 65 +
bsps/microblaze/microblaze_fpga/fdt/bsp_fdt.c | 23 --
bsps/microblaze/microblaze_fpga/include/bsp.h | 3
This patch set adds device tree support to the following MicroBlaze BSP drivers:
- AXI Interrupt Controller
- JFFS2 QSPI
- AXI UART Lite
- AXI Timer clock
Previously, the only way to configure the above drivers was to use build
configuration options. Now when a device tree is present, the BSP
---
bsps/microblaze/microblaze_fpga/clock/clock.c | 50 ---
.../microblaze_fpga/include/bsp/timer.h | 2 -
2 files changed, 32 insertions(+), 20 deletions(-)
diff --git a/bsps/microblaze/microblaze_fpga/clock/clock.c
b/bsps/microblaze/microblaze_fpga/clock/clock.c
index
On Thu, Jan 12, 2023 at 5:11 PM Joel Sherrill wrote:
> Will this need to be added as an expected fail on other architectures?
>
> Just wondering how many bsp test configuration files need touching
>
I suppose I could set it to enabled for only AArch64 for now. It would
definitely fail on other
Will this need to be added as an expected fail on other architectures?
Just wondering how many bsp test configuration files need touching
On Thu, Jan 12, 2023, 4:55 PM Kinsey Moore wrote:
> This adds a test verifying basic TLS functionality in loadable modules
> now that at least one
On 1/12/2023 4:54 PM, Kinsey Moore wrote:
The mask 0xff is used by ELF32 while ELF64 uses 0x. These are
automatically selected based on the build type when using ELF_R_TYPE().
---
cpukit/libdl/rtl-rap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This adds a test verifying basic TLS functionality in loadable modules
now that at least one architecture supports it.
---
spec/build/testsuites/libtests/dl11.yml | 38 +++
spec/build/testsuites/libtests/grp.yml | 2 +
testsuites/libtests/dl11/dl-load.c | 142
The mask 0xff is used by ELF32 while ELF64 uses 0x. These are
automatically selected based on the build type when using ELF_R_TYPE().
---
cpukit/libdl/rtl-rap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/libdl/rtl-rap.c b/cpukit/libdl/rtl-rap.c
index
This prints the relocation type that was found to be missing in addition
to its address to aid in bug reports.
---
cpukit/libdl/rtl-mdreloc-aarch64.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/cpukit/libdl/rtl-mdreloc-aarch64.c
b/cpukit/libdl/rtl-mdreloc-aarch64.c
This adds basic TLS relocation support for AArch64 to libdl. This lets
loadable modules use TLS symbols hosted in the main binary. This does
not allow loadable modules to host their own TLS symbols.
---
cpukit/libdl/rtl-mdreloc-aarch64.c | 38 ++
1 file changed, 38
When generating the symbol table for loadable modules, include TLS
symbols so that the modules can reference them.
---
linkers/rtems-syms.cpp | 5 +
rtemstoolkit/rld-elf.cpp | 1 +
rtemstoolkit/rld-symbols.cpp | 3 +++
3 files changed, 9 insertions(+)
diff --git
On 1/12/2023 10:38 AM, Sebastian Huber wrote:
On 12.01.23 16:52, Kinsey Moore wrote:
Annotation of expected test states with a description could get quite
repetitive, but I suppose that's better than losing the information.
I'm fine with this going in for now with a ticket to address this
On 12.01.23 16:52, Kinsey Moore wrote:
Annotation of expected test states with a description could get quite
repetitive, but I suppose that's better than losing the information. I'm
fine with this going in for now with a ticket to address this issue and
we can pull the annotations back in when
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:
* Removal of whitespace
This is fine for whitespace at the base level of indentation. Whitespace
within an indented block may be more important for
On 12.01.23 13:03, Sebastian Huber wrote:
Merge the "default" and "default-by-variant" attributes. Use an
"enabled-by" expression to select the default value based on the enabled
set. This makes it possible to select default values depending on other
options. For example you could choose
Replace the variant patterns in the default-by-variant list with an
explicit list of matching BSPs.
The change was tested by comparing the output of
./waf bspdefaults
before and after the change.
---
.../bsps/aarch64/xilinx-zynqmp/optclki2c0.yml | 8 +++
Use yaml.dump(data, default_flow_style=False, allow_unicode=True) to
format all build items.
---
spec/build/bsps/aarch64/a53/optramlen.yml | 2 +-
spec/build/bsps/aarch64/a53/tsta53.yml| 22 +++-
spec/build/bsps/aarch64/a72/optramlen.yml | 2 +-
Merge the "default" and "default-by-variant" attributes. Use an
"enabled-by" expression to select the default value based on the enabled
set. This makes it possible to select default values depending on other
options. For example you could choose memory settings based on whether
RTEMS_SMP is
22 matches
Mail list logo
