A register block may be used to specify the interface of devices which
contain registers associated with an integer address. Register blocks
consist of register block members specified by the ``definition``
attribute. Register block members are either instances of registers
specified by the ``registers`` attribute or instances of other register
blocks specified by links with the "register-block-include" link role.
Registers consists of bit fields. The register block members are placed
into the address space of the device relative to the base address of the
register block. Register member offests and the register block size are
specified in units of the address space granule.
Update #3715.
This patch adds the documentation for building and running RTEMS on the Kendryte K210 RISC-V SoC.
The generic riscv introducion was re-arranged to list the multilib variants then the specific
hardware targets. In addition a couple of errors were fixed for the generic QEMU commands.
V2 corrected a typo, expanded K210 Console UART parameters, and addded a hyperlink to renode.io install
instructions.
V3 clarified the multilib variant description, clarified the multilib variant reference platform, and
corrected capitalization on SiFive.
V4 improves the instructions for running the K210 BSP on the Renode.io simulator.
V5 cleaned up the text to be no more than 80 characters per line.
V6 applied word wrap to paragraphs and replaced hard coded RTEMS major versions with macros.
Closes#4876
This patch adds the documentation for building and running RTEMS on the Kendryte K210
RISC-V SoC. The generic riscv introducion was re-arranged to list the multilib variants
then the specific hardware targets. In addition a couple of errors were fixed for the
generic QEMU commands.
V2 corrected a typo, expanded K210 Console UART parameters, and addded a hyperlink
to renode.io install instructions.
Closes#4876
Casting the node returned by rtems_chain_head is incorrect. That node is
owned by the control structure and use of it post-cast could cause
memory corruption. Instead, use rtems_chain_first which returns the
node after the head node. This also corrects node->next to
rtems_chain_next(node) which makes better use of the API.
This commit already clarified that the defines of the removed section
are optional BSP provided default values and not application
configuration options:
commit cf9f2121577b11f8eab5e49c48173c46cf09c627
Author: Sebastian Huber <sebastian.huber@embedded-brains.de>
Date: Wed Nov 17 08:46:56 2021 +0100
c-user: Clarify BSP related configuration settings
