On Tue, Sep 10, 2019 at 12:06:10PM +0200, Uwe Kleine-König wrote:
> In the Linux dts files skeleton.dtsi was dropped (in commit abe60a3a7afb
> ("ARM: dts: Kill off skeleton{64}.dtsi") for v5.1-rc1). At least one
> reason for this also applies for barebox: memory nodes are supposed to have
> a unit
On Mon, Sep 09, 2019 at 09:40:13PM +0200, Uwe Kleine-König wrote:
> These settings used to be specified per-mode. But the device tree
> bindings have these two values attached to the display and not to each
> mode. Also for the supported boards it doesn't matter as they all only
> have a single
Hello,
On Thu, Sep 12, 2019 at 08:16:17AM +0200, Sascha Hauer wrote:
> On Mon, Sep 09, 2019 at 10:34:51PM +0200, Uwe Kleine-König wrote:
> > + ret = mci_send_ext_csd(mci, ext_csd);
> > + if (ret) {
> > + printf("Failure to read EXT_CSD register\n");
> > + free(ext_csd);
>
On Wed, Sep 11, 2019 at 05:03:03PM +0200, Marco Felsch wrote:
> If the current regulator can't be requested because of -EPROBE_DEFER we
> shouldn't print a error and ignore it.
>
> Signed-off-by: Marco Felsch
> ---
> drivers/mci/mci-core.c | 4
> 1 file changed, 4 insertions(+)
Applied,
On Wed, Sep 11, 2019 at 05:00:18PM +0200, Marco Felsch wrote:
> The upstream dt-bindings abstracts the DA9063/2 PMIC MFD by multiple
> of-subnodes and the linux-mfd core creates platform-devices for each
> node. Due to the lack of a mfd fw we need to add the platform-devices by
> our own to reuse
On Wed, Sep 11, 2019 at 05:07:06PM +0200, Marco Felsch wrote:
> Currently the the driver don't handle any error and return immediately.
> Handling the errors correctly is a must to support defered probing.
>
> Signed-off-by: Marco Felsch
> ---
> drivers/mci/imx-esdhc.c | 30
On Thu, Sep 12, 2019 at 08:54:10AM +0200, Ahmad Fatoum wrote:
> I've picked up v1 of the patch from here:
> https://barebox.infradead.narkive.com/mn9ZpGu6/patch-2-3-marsboard-add-new-board
>
> and worked in the review feedback from back then.
>
> v1 -> v2:
> - rebased on current upstream/next
>
On Wed, Sep 11, 2019 at 09:27:37PM +0200, Uwe Kleine-König wrote:
> state_get_name() is not used and so can be removed.
> state_backend_dtb_file() and state_backend_raw_file() were dropped in
> c999b507da98 ("state: Refactor state framework").
>
> Signed-off-by: Uwe Kleine-König
> ---
>
On Mon, Sep 09, 2019 at 10:57:53AM +0200, Sascha Hauer wrote:
> On Fri, Sep 06, 2019 at 03:20:01PM +0200, Michael Tretter wrote:
> > Hello,
> >
> > This is the v2 for adding device tree overlay support to barebox.
> >
> > The biggest change is the new function of_overlay_apply_tree() which
> >
On Thu, Sep 12, 2019 at 08:42:40AM +0200, Uwe Kleine-König wrote:
> Hello,
>
> -m was an intermediate step. You suggested to use -m instead of
> "setmax", but while implementing I noticed that with options there is no
> need for a keyword or option.
>
> Can you please squash this into my patch?:
On Mon, Sep 09, 2019 at 10:34:51PM +0200, Uwe Kleine-König wrote:
> + ret = mci_send_ext_csd(mci, ext_csd);
> + if (ret) {
> + printf("Failure to read EXT_CSD register\n");
> + free(ext_csd);
> + return ERR_PTR(-EIO);
> + }
> +
> + return
From: Ahmad Fatoum
Have it compile as part of the defconfig, to improve coverage.
Signed-off-by: Ahmad Fatoum
---
arch/arm/configs/imx_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/imx_v7_defconfig
b/arch/arm/configs/imx_v7_defconfig
index
This board is produced by Embest/Element 14 and is based on i.MX6 Dual.
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.html
Signed-off-by: Eric Bénard
Signed-off-by: Ahmad Fatoum
---
Documentation/boards/imx/embest-marsboard.rst | 82 +++
As done in the Linux Kernel. Most of the packed structures we have
are optimized to not generate any unaligned accesses, so this warning
produces a lot of false positives which are hard to fix in the code.
Signed-off-by: Sascha Hauer
---
Makefile | 2 ++
1 file changed, 2 insertions(+)
diff
I've picked up v1 of the patch from here:
https://barebox.infradead.narkive.com/mn9ZpGu6/patch-2-3-marsboard-add-new-board
and worked in the review feedback from back then.
v1 -> v2:
- rebased on current upstream/next
- removed seperate defconfig and added board to imx_v7_defconfig (Lucas)
-
On Mon, Sep 09, 2019 at 09:28:17PM -0700, Andrey Smirnov wrote:
> On Mon, Sep 9, 2019 at 3:23 AM Sascha Hauer wrote:
> >
> > On Sat, Sep 07, 2019 at 04:54:55PM -0700, Andrey Smirnov wrote:
> > > GCC9 for ARM produces the following warnings:
> > >
> > > fastmap.c: In function 'ubi_attach_fastmap':
When a tee_res has been acquired it must be released when bootm returns
(for dryrun)
Signed-off-by: Sascha Hauer
---
common/bootm.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/bootm.c b/common/bootm.c
index d7232f6afa..b50b76ed6f 100644
--- a/common/bootm.c
+++ b/common/bootm.c
On Thu, 2019-09-12 at 09:13 +0200, Sascha Hauer wrote:
> When a tee_res has been acquired it must be released when bootm
> returns
> (for dryrun)
>
> Signed-off-by: Sascha Hauer
> ---
> common/bootm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/common/bootm.c b/common/bootm.c
>
The of_diff command compares two device trees against each other
and prints a diff-like result. This can be handy to find out the
differences between the barebox live tree and the one we start the
kernel with. Another usecase would be to examine the changes our
of_fixup process introduces (of_diff
of_diff compares two device trees against each other and prints a
diff-like result.
Signed-off-by: Sascha Hauer
---
drivers/of/base.c | 141 ++
include/of.h | 1 +
2 files changed, 132 insertions(+), 10 deletions(-)
diff --git
of_get_reproducible_name() returns an allocated string, so we must free
it.
Signed-off-by: Sascha Hauer
---
drivers/of/base.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/drivers/of/base.c b/drivers/of/base.c
index 838f530f85..22077fa397 100644
---
For layerscape images, barebox currently generates a second stage
barebox that lacks the RCW and PBI and as such can be bootm'd as
any other barebox ARM image. A previous commit implemented bootm
handlers for the RCW and PBI prefixed images and thus the 2nd.image
no longer serves a real purpose.
Some peripherals are still missing, but the main functionality to boot
an OS is already in place. Document how to use it.
Signed-off-by: Ahmad Fatoum
---
Documentation/boards/layerscape.rst | 61 +++
.../boards/layerscape/ls1046ardb.rst | 36 +++
architecture is statically initialized to zero, which happens to be
ARCH_ARM as it's the first enum element.
Make this a bit clearer by explicitly assigning ARM_ARM to architecture.
Signed-off-by: Ahmad Fatoum
---
scripts/pblimage.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
We do not yet support USB on the Layerscape platforms, but when we do,
it's imaginable that we would want to export barebox_update targets over
Fastboot. Prepare for this by adding the layerscape images to those that
filetype_is_barebox_image returns true for.
Signed-off-by: Ahmad Fatoum
---
The layerscape images are preceeded by a RCW and PBI, which are interpreted
by the Layerscape Hardware Pre-Bootloader and aren't executable as ARM code.
To maintain the ability to network boot them, add a bootm handler that
skips the fixed-size header.
Signed-off-by: Ahmad Fatoum
---
We already disable PHYs 4-7, which are currently unusable as they hang
off SGMII, which barebox' FMan driver does not yet support.
Follow suit for the SGMII eth0 and eth1 as well, so they don't
unnecessarily clutter the barebox output with
Unable to find a PHY (unknown ID?)
messages.
barebox already has a copy_file for copying files. Extend the API by a
copy_file_2 that takes a source offset into account.
This is useful for handling SoC-specific image formats which have a
fixed-size header, as copy_file_2 can now skip that header and create a
file with the full barebox image
On the i.MX6qp the enfc_sel mux is at bits 15-17, not on 16-17. Fix
this. During clock tree initialization we reparented the enfc_sel to:
clk_set_parent(clks[IMX6QDL_CLK_ENFC_SEL],
clks[IMX6QDL_CLK_PLL2_PFD2_396M]);
This resulted in a register setting 0b110 for the enfc_sel mux which is
With 76b6f74c53 we begin embedding a struct mtd_info into struct
nand_chip. With this mtd_to_nand() must be changed accordingly.
Fixes: 76b6f74c53 ("mtd: nand: Embed struct mtd_info into struct nand_chip")
Signed-off-by: Sascha Hauer
---
include/linux/mtd/nand.h | 2 +-
1 file changed, 1
Hello Ahmad,
On Thu, Sep 12, 2019 at 12:28:59PM +0200, Ahmad Fatoum wrote:
> barebox already has a copy_file for copying files. Extend the API by a
> copy_file_2 that takes a source offset into account.
Can you give that function a more descriptive name? Something like
copy_file_from_offset()?
Hello Uwe,
On 9/12/19 3:06 PM, Uwe Kleine-König wrote:
> Hello Ahmad,
>
> On Thu, Sep 12, 2019 at 12:28:59PM +0200, Ahmad Fatoum wrote:
>> barebox already has a copy_file for copying files. Extend the API by a
>> copy_file_2 that takes a source offset into account.
>
> Can you give that
On Thu, Sep 12, 2019 at 03:37:49PM +0200, Ahmad Fatoum wrote:
> Hello Uwe,
>
> On 9/12/19 3:06 PM, Uwe Kleine-König wrote:
> > Hello Ahmad,
> >
> > On Thu, Sep 12, 2019 at 12:28:59PM +0200, Ahmad Fatoum wrote:
> >> barebox already has a copy_file for copying files. Extend the API by a
> >>
33 matches
Mail list logo
