The BeagleV Starlight hasn't exited the Beta phase and the BeagleV name
is now associated with the BeagleV-Ahead, which used a different SoC.
Note this in the section title and also adjust the build instruction to
make them reproducible in 2024:
- Given that the board is discontinued, it's not
Most barebox platforms are either completely cache-coherent with respect to
DMA or completely non-coherent. To avoid having to walk the device tree for
non-existent dma-coherent and dma-noncohrent properties, barebox thus
only does this when CONFIG_OF_DMA_COHERENCY is selected.
Hello Antony,
On 11.03.24 12:50, Ahmad Fatoum wrote:
> Hello Antony,
>
> On 10.03.24 21:33, Antony Pavlov wrote:
>> Hi Ahmad!
>>
>> I have tried to rebuild barebox for BeagleV.
>> Alas I was unable to reproduce the steps from Documentation/boards/riscv.rst
>> because of changes in opensbi repo.
Re-sync our code base with Linux which moved quite a lot. This patch is
huge but still is only a partly sync. The main changes are:
- The nvmem_cell struct was split into nvmem_cell and nvmem_cell_entry
- The cells are now parsed and registered during nvmem_register(), no
longer during
The at24 driver does not need to handle the ids by its own since the
nvmem_core does the handling too. This lead into issues where the eeprom
device is named: eeprom00.
Fix the alias handling too since the devie would never be named as
described in the alias, since we never told the nvmem-core to
Expose the nvmem cells via cdevs which is our equivalent to the Linux
sysfs exposure. This allows the easier user queries for board code and
shell. Keep the Linux function name scheme for
nvmem_populate_sysfs_cells() to reduce the diff for nvmem_register()
function.
Signed-off-by: Marco Felsch
Right now the core implementation always make use of DEVICE_ID_DYNAMIC.
This does not allow us having static devices supplied via the of-aliases
node. Therefore sync the code base with Linux to allow single ids,
albeit the id handling is still different.
While on it fix the nvmem_register_cdev()
Constify the nvmem_*_write() functions as the write functions shouldn't
alter the buffer content.
Signed-off-by: Marco Felsch
---
drivers/nvmem/core.c | 10 +-
include/linux/nvmem-consumer.h | 8
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git
This adds the support to load devicetree overlays from an FIT image.
There are quite a few options to handle FIT overlays since the FIT
overlay spec is not very strict.
This patch implement the most configurable case where each overlay does
have it's own config node (including the optional
Since we do support FIT image overlays and file/dir based overlays the
filename variable is not sufficient anylonger. Therefore rename the
local variables as well as the filter function to hook.
To not break any systems keep the old filename based name too but mark
them as deprecated.
Linux did the same in commit v6.7-rc1~61^2~1^2~42 with the reasoning
that this part isn't a NOR but an FRAM and is supported by the at25
driver. Follow this reasoning and drop MB85RS1MT from spi-nor, too.
Signed-off-by: Uwe Kleine-König
---
drivers/mtd/spi-nor/spi-nor.c | 3 ---
1 file changed,
The FIT spec is not very specific when it comes to device-tree overlay
handling. Overlays can be added directely to an config node:
config-a {
compatible = "machine-compatible";
kernel = "kernel-img-name";
fdt = "fdt-base-name",
Add the a parameter which will be used by image-fit to decide if a
config node belongs to a devicetree-overlay.
Signed-off-by: Marco Felsch
---
drivers/of/overlay.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
index
In preparation of adding support for FIT image overlay handling the
global.of.overlay.dir can be reused if we rename it to a more generic
global.of.overlay.path since it does not imply an directory.
This commit adds the ground work by deprecating the old
global.of.overlay.dir and moving the
The upcoming FIT overlay support requires these helpers for performing
check on a fit image.
Signed-off-by: Marco Felsch
---
common/image-fit.c | 4 ++--
include/image-fit.h | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/common/image-fit.c b/common/image-fit.c
index
The current overlay mechanism can handle files only, so filepattern was
obvious. With the next commit this will change, so overlays can also
supplied via FIT images. To prepare the pattern filter to match FIT
config-nodes make the filter and global variable handling the pattern
more generic by
This is now done during of_overlay_global_fixup() so we can drop it
here.
Signed-off-by: Marco Felsch
---
drivers/of/overlay.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
index c8e70ab00091..150b07daccaa 100644
--- a/drivers/of/overlay.c
+++
17 matches
Mail list logo
