Hi Sascha,
On 09.12.19 16:37, Sascha Hauer wrote:
On Mon, Dec 09, 2019 at 01:31:40PM +0100, Stefan Riedmueller wrote:
Change environment device-path from using a separate label to
referencing a device plus partname.
Why? The way it was is fine.
Just to be consistent with phyCORE and
On Mon, Dec 09, 2019 at 01:31:40PM +0100, Stefan Riedmueller wrote:
> Change environment device-path from using a separate label to
> referencing a device plus partname.
Why? The way it was is fine.
Sascha
--
Pengutronix e.K. | |
This is a port of Linux kernel commit
| commit 30a2c8aa3c520d54bcaf3015ca8141b0156448b1
| Author: Roger Pueyo Centelles
| Date: Thu Feb 7 20:09:35 2019 +0100
|
| mtd: spi-nor: Add support for en25qh64
|
| The Eon EN25QH64 is a 64 Mbit SPI NOR flash memory chip found
| on recent
The next patch will add the .imxcfg file as a rule prerequisite, so the
target is rebuilt if it changes. Instead of duplicating it in all rules,
factor out the common parts into a imx_image_rule variable.
As the arguments are now going through an eval, any use of $ must be
escaped with another $
So far changing the DCD table didn't trigger a rerun of the i.MX
image utility. To fix this, we need to have the DCD table as prerequisite
to the .imximg rule. The file name is contained in $(CFG_$(@F)), but
can't be used directly because $@ (and by extension @F) has no value
when first expanded
The following commit will introduce a variable define to remove the
duplication in the different [supe]*imximg rules.
Prepare for this by rearranging the command line flags to line up with
the letters in the extension (i.e. -e -s for esimximg instead of -s -e)
and by splitting off a multi-target
Avoid the example bitstream header to validate the bitstream that should
be loaded into the FPGA. The header is mostly 0x with a few
special values at a certain offsets and can be better described with the
offsets and their magic values.
As a drive by, this fixes/removes a broken check in
On 12/9/19 2:31 PM, Sascha Hauer wrote:
> On Wed, Dec 04, 2019 at 05:01:59PM +0100, Ahmad Fatoum wrote:
>> The next patch will add the .imxcfg file as a rule prerequisite, so the
>> target is rebuilt if it changes. Instead of duplicating it in all rules,
>> factor out the common parts into a
On Wed, Dec 04, 2019 at 05:01:59PM +0100, Ahmad Fatoum wrote:
> The next patch will add the .imxcfg file as a rule prerequisite, so the
> target is rebuilt if it changes. Instead of duplicating it in all rules,
> factor out the common parts into a imx_image_rule variable.
>
> No functional
For NAND flash with eraseblock size 1 MB and more the current
barebox partition size is not sufficient. The 4 FCB copies alone occupy
the 4 MB partition size. Increase the partition size to 16 MB to be fit
for the future and leaving some blocks for bad block handling as well.
Signed-off-by:
The SD card interface is still using the legacy partition binding.
Change this by switching to the new bindings.
Signed-off-by: Stefan Riedmueller
---
No changes in v2
---
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
Use the simpler name phycard instead of the article number pcaaxl3
for device tree file names and image names of the phyCARD-i.MX 6.
Also make the dtsi file includeable for i.MX 6Solo/DualLight as well.
Signed-off-by: Stefan Riedmueller
---
Changes in v2:
- Remove the model and compatible from
The EEPROM is a configurable option. So make it configurable from the
dts file.
Signed-off-by: Stefan Riedmueller
---
No changes in v2
---
arch/arm/dts/imx6q-phytec-phycard.dts| 4
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 1 +
2 files changed, 5 insertions(+)
diff --git
Signed-off-by: Stefan Riedmueller
---
Changes in v2:
- Added this patch
---
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi
b/arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi
index
Bring the device tree nodes in alphabetical order and in this context
also remove the deprecated iomux group.
Signed-off-by: Stefan Riedmueller
---
No changes in v2
---
arch/arm/dts/imx6q-phytec-pcaaxl3.dtsi | 182 -
1 file changed, 90 insertions(+), 92
Change environment device-path from using a separate label to
referencing a device plus partname.
Signed-off-by: Stefan Riedmueller
---
No changes in v2
---
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
Make use of SPDX license identifiers and update copyright notices and
model descriptions of the phyCARD-i.MX 6 SOM.
Signed-off-by: Stefan Riedmueller
---
Changes in v2:
- Don't remove dtsi's model and compatible yet
---
arch/arm/dts/imx6q-phytec-pbaa03.dts | 13 -
On Mon, Dec 09, 2019 at 11:42:36AM +0100, Steffen Trumtrar wrote:
> To allow marking an imd tag with properties, add a flags field to the
> imd_header.
>
> Signed-off-by: Steffen Trumtrar
> ---
> include/image-metadata.h | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git
Hi All,
I released barebox-2019.12.0. With this release the STM32MP1 support
continues to evolve, we gained MMC/SD support, PMIC support and ethernet
support. Another important thing is that we now have vi style bindings
for the internal editor, check it out! We also have some important ext4
Currently, the default environment is only used when the
barebox environment on the persistent store is not valid
or when ENVFS_FLAGS_FORCE_BUILT_IN is set in the super block.
However, ENVFS_FLAGS_FORCE_BUILT_IN can be cleared and the
environmnet variables in the persistent store will be
used
Hi Roland,
On 09.12.19 11:20, Roland Hieber wrote:
On Mon, Dec 09, 2019 at 10:01:43AM +0100, Stefan Riedmueller wrote:
Make use of SPDX license identifiers and update copyright notices and
model descriptions of the phyCARD-i.MX 6 SOM.
Signed-off-by: Stefan Riedmueller
---
Add a new imd type "checksum". This type consists of the CRC32 checksum
of the whole barebox image minus the checksum itself.
The checksum can be written to the imd field with the bareboximd host-tool.
It can be verified with said tool or with "imd" on the target.
Signed-off-by: Steffen Trumtrar
Add support for verifying an image by use of the imd checksum.
If the checksum that is saved in the image and the one that is
calculated over the image differ, barebox_update aborts.
Signed-off-by: Steffen Trumtrar
---
common/bbu.c | 4
1 file changed, 4 insertions(+)
diff --git
Instead of using "8" as the size of an imd_header, use the sizeof operator.
Signed-off-by: Steffen Trumtrar
---
common/imd.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/common/imd.c b/common/imd.c
index 913a01de87bf..e0dab69644c0 100644
--- a/common/imd.c
+++
To allow marking an imd tag with properties, add a flags field to the
imd_header.
Signed-off-by: Steffen Trumtrar
---
include/image-metadata.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/include/image-metadata.h b/include/image-metadata.h
index 5904d95acd37..ca73e6cf6ec6
On 12/4/19 1:56 PM, Ahmad Fatoum wrote:
> UEFI 2.1D specifies two protocols for abstracting both the PCI host bus
> controller and for PCI devices. The protocol for PCI devices provides
> function pointers for accessing IO Port, Memory and PCI configuration
> space, among others. The protocol for
On Wed, Dec 04, 2019 at 03:07:19PM +0100, Ahmad Fatoum wrote:
> Microsoft specifies an ACPI Watchdog Action Table for its server
> offerings that abstracts away hardware-specifics of watchdog devices.
> This can be an alternative to implementing many different watchdog
> driver in barebox for x86
On Mon, Dec 09, 2019 at 10:01:43AM +0100, Stefan Riedmueller wrote:
> Make use of SPDX license identifiers and update copyright notices and
> model descriptions of the phyCARD-i.MX 6 SOM.
>
> Signed-off-by: Stefan Riedmueller
> ---
> arch/arm/dts/imx6q-phytec-pbaa03.dts | 13 -
>
Hi Sascha,
On 19-12-09 11:00, Sascha Hauer wrote:
> The patch does the right thing: When a regulator can't be found and
> -EPROBE_DEFER is returned we forward it. However, we have several boards
> in the tree which do not have any driver for the regulator, but still
> work because the regulator
Hi Sam,
On Mo, 2019-12-09 at 10:05 +0100, Sam Ravnborg wrote:
> Hi Lucas.
>
> On Mon, Dec 09, 2019 at 09:00:29AM +0100, Lucas Stach wrote:
> > When using the RO_DATA_SECTION macro, all the individual components
> > are put into the rodata section. As they now end up in the same
> > section there
The patch does the right thing: When a regulator can't be found and
-EPROBE_DEFER is returned we forward it. However, we have several boards
in the tree which do not have any driver for the regulator, but still
work because the regulator is enabled by default or by board code.
Revert this patch
Before reparenting the ENFC_SEL mux we have to make sure the GPMI_IO clk
is disabled as recommended in the reference manual. Otherwise glitches
may occur on the GPMI clk which result in a later NAND failure:
MXS: Timeout resetting block via register 0x01806000
mxs_nand
Hi Clement,
On Mon, Sep 23, 2019 at 01:36:34PM +0200, Clement Leger wrote:
> Durign a previous patch, 0x2 was mistakenly converted to BIT(2) whereas
> it should be BIT(1).
> ---
> include/linux/mtd/spi-nor.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied now, thanks.
Note you
On Wed, Dec 04, 2019 at 05:01:58PM +0100, Ahmad Fatoum wrote:
> The following commit will introduce a variable define to remove the
> duplication in the different [supe]*imximg rules.
>
> Prepare for this by rearranging the command line flags to line up with
> the letters in the extension (i.e.
Hi Lucas.
On Mon, Dec 09, 2019 at 09:00:29AM +0100, Lucas Stach wrote:
> When using the RO_DATA_SECTION macro, all the individual components
> are put into the rodata section. As they now end up in the same
> section there is no alignment enforced between them anymore. This
> leads to unaligned
For NAND flash with eraseblock size 1 MB and more the current
barebox partition size is not sufficient. The 4 FCB copies alone occupy
the 4 MB partition size. Increase the partition size to 16 MB to be fit
for the future and leaving some blocks for bad block handling as well.
Signed-off-by:
Change environment device-path from using a separate label to
referencing a device plus partname.
Signed-off-by: Stefan Riedmueller
---
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git
The SD card interface is still using the legacy partition binding.
Change this by switching to the new bindings.
Signed-off-by: Stefan Riedmueller
---
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 21 -
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git
The EEPROM is a configurable option. So make it configurable from the
dts file.
Signed-off-by: Stefan Riedmueller
---
arch/arm/dts/imx6q-phytec-phycard.dts| 4
arch/arm/dts/imx6qdl-phytec-phycard-som.dtsi | 1 +
2 files changed, 5 insertions(+)
diff --git
Use the simpler name phycard instead of the article number pcaaxl3
for device tree file names and image names of the phyCARD-i.MX 6.
Signed-off-by: Stefan Riedmueller
---
arch/arm/boards/phytec-som-imx6/lowlevel.c | 6 ++---
arch/arm/dts/Makefile | 2 +-
Make use of SPDX license identifiers and update copyright notices and
model descriptions of the phyCARD-i.MX 6 SOM.
Signed-off-by: Stefan Riedmueller
---
arch/arm/dts/imx6q-phytec-pbaa03.dts | 13 -
arch/arm/dts/imx6q-phytec-pcaaxl3.dtsi | 14 +++---
2 files changed, 7
Bring the device tree nodes in alphabetical order and in this context
also remove the deprecated iomux group.
Signed-off-by: Stefan Riedmueller
---
arch/arm/dts/imx6q-phytec-pcaaxl3.dtsi | 182 -
1 file changed, 90 insertions(+), 92 deletions(-)
diff --git
Hi Patrick,
On Sat, Dec 07, 2019 at 10:15:26AM +, Patrick Schneider wrote:
> I have a use case where I would need to be able to manipulate the
> fstab on the rootfs before booting, so I wondered if it is possible to
> write to a mounted ubifs from barebox?
> Currently I am trying with:
>
>
When using the RO_DATA_SECTION macro, all the individual components
are put into the rodata section. As they now end up in the same
section there is no alignment enforced between them anymore. This
leads to unaligned start pointers when any of the components have a
unaligned size. Enforce some
44 matches
Mail list logo
