Re: Oselas 2018.12.0 toolchain seems to break barebox for AM335x

Good day, everyone. *bump* On 2019-10-25 10:48 a.m., Andreas Geisenhainer wrote: Hello Sascha, hello barebox-ml. > On 2019-07-10 9:58 a.m., Sascha Hauer wrote: >> On Mon, Jul 08, 2019 at 04:15:00PM +0200, Andreas Geisenhainer wrote: >>> We're running barebox an a Phytec PhyCORE AM335x platf

[PATCH 2/2] ARM: dts: imx6: phycore: Update License, copyright and model description

Make use of SPDX license identifiers and update copyright notices and model descriptions of the phyCORE-i.MX 6 SOM's. Signed-off-by: Stefan Riedmueller --- arch/arm/dts/imx6dl-phytec-phycore-som-emmc.dts | 10 ++ arch/arm/dts/imx6dl-phytec-phycore-som-nand.dts | 13 - arch/ar

[PATCH 1/2] ARM: dts: imx6: phycore: Make use of upstream devicetree

Make use of the upstream devicetree for the phyCORE-i.MX 6 and the phyBOARD-Mira to reduce code duplication. In this context also add a Mira devicetree for barebox to better differentiate between phyCORE related settings and baseboard related settings. Signed-off-by: Stefan Riedmueller --- arch/

Re: barebox on VoCore2

On Mon, 11 Nov 2019 10:48:26 +0100 Mauro Condarelli wrote: > Hi, > I would like to use barebox with a custom board (VoCore2, based on > MT7628) currently running on a paleolithic version of u-boot. > I've seen there has been some work on this board > (http://lists.infradead.org/pipermail/barebox/

Re: state: eMMC boot0-partitions backend for Linux

Hello Christoph, On 11/3/19 4:45 PM, Christoph Fritz wrote: > Hi, > > I would like to use emmc-hardware-partition boot1 as a state backend, > this has the charm of keeping the big hw-partition clean while using SLC > for e.g. serial numbers. > Within barebox using an emmc-hardware-partition boot

[PATCH] ARM: am335x: Enable MMC2 clock

Since Kernel commit 5b63fb90adb9 ("ARM: dts: Fix incomplete dts data for am3 and am4 mmc") (barebox commit 419db1f984 ("dts: update to v5.3-rc7")) the AM33xx MMC2 controller is unconditionally enabled in the dts. This has the effect that the driver probes for this device and then can't access the r

[PATCH 0/1] net: designware: eqos: stop DMA on halt

Hello Sascha, Would be great if you could apply this to master. Thanks, Ahmad Ahmad Fatoum (1): net: designware: eqos: stop DMA on halt drivers/net/designware_stm32.c| 2 ++ drivers/net/designware_tegra186.c | 2 ++ 2 files changed, 4 insertions(+) -- 2.20.1 _

[PATCH 1/1] net: designware: eqos: stop DMA on halt

designware_eqos.c contains an eqos_stop implementation to stop the NIC when halting the interface. Unfortunately it wasn't used leading to memory corruption on boot, possibly due to DMA. Fix this. Signed-off-by: Ahmad Fatoum --- drivers/net/designware_stm32.c| 2 ++ drivers/net/designware_te

barebox on VoCore2

Hi, I would like to use barebox with a custom board (VoCore2, based on MT7628) currently running on a paleolithic version of u-boot. I've seen there has been some work on this board (http://lists.infradead.org/pipermail/barebox/2017-August/030945.html), but it's unclear to me if this resulted in a

Re: [PATCH v3 1/4] watchdog: always populate watchdog priority from device tree if possible

On Fri, Nov 08, 2019 at 12:03:29PM +0100, Ahmad Fatoum wrote: > So far, only the da9063 and da9053 have made use of the optional barebox > watchdog-priority binding. Move it into the core, so other device > drivers automatically have their watchdog-priority property parsed as > well. This patch doe

Re: [PATCH v2 01/18] ARM: zynq: zedboard: enable MACB driver in defconfig

On Sat, Nov 09, 2019 at 03:28:20PM +0100, Lucas Stach wrote: > The board support is a bit more useful with active networking. > > Signed-off-by: Lucas Stach > --- > arch/arm/configs/zedboard_defconfig | 1 + > 1 file changed, 1 insertion(+) > Applied, thanks Sascha -- Pengutronix e.K.