AW: Barebox for Zedboard

2020-03-23 Thread Michael Graichen
Von: Lucas Stach Gesendet: Donnerstag, 19. März 2020 11:53 An: Michael Graichen; barebox@lists.infradead.org Betreff: Re: Barebox for Zedboard Hi Michael, Am Donnerstag, den 19.03.2020, 10:38 + schrieb Michael Graichen: > Hey, > > i have just

AW: Barebox for Zedboard

2020-03-23 Thread Michael Graichen
Von: Lucas Stach Gesendet: Donnerstag, 19. März 2020 11:53 An: Michael Graichen; barebox@lists.infradead.org Betreff: Re: Barebox for Zedboard Hi Michael, Am Donnerstag, den 19.03.2020, 10:38 + schrieb Michael Graichen: > Hey, > > i have just

Re: am335x: load a kernel with integrated initramfs

2020-03-23 Thread Yegor Yefremov
Hi Sascha, On Mon, Mar 23, 2020 at 9:30 AM Sascha Hauer wrote: > > Hi Yegor, > > On Fri, Mar 20, 2020 at 09:29:04AM +0100, Yegor Yefremov wrote: > > I get an "handler failed with: Out of memory" message when trying to > > load my 22MB large kernel-fit.itb. Below you can see the related log: > >

Re: [PATCH 1/2] of: base: parse all available memory nodes

2020-03-23 Thread Ahmad Fatoum
Hi, On 3/23/20 11:21 AM, Clément Leger wrote: >> AFAIK the device_type = "memory" property was mandatory in the early >> days as well, there shouldn't be any /memory nodes without this >> property. Given that, is the add-legacy-node-first still necessary? > > Agreed, I did that after speaking

Re: [PATCH 1/2] of: base: parse all available memory nodes

2020-03-23 Thread Clément Leger
Hi Sascha, - On 23 Mar, 2020, at 11:12, Sascha Hauer s.ha...@pengutronix.de wrote: > On Mon, Mar 16, 2020 at 12:00:07PM +0100, Clement Leger wrote: >> Currently, barebox only parse one memory node which is either the >> "/memory" node or the first node with device_type == "memory". >>

Re: [PATCH 1/2] of: base: parse all available memory nodes

2020-03-23 Thread Sascha Hauer
On Mon, Mar 16, 2020 at 12:00:07PM +0100, Clement Leger wrote: > Currently, barebox only parse one memory node which is either the > "/memory" node or the first node with device_type == "memory". > However, the use of multiple memory nodes with device_type = "memory" > property is allowed by the

Re: am335x: load a kernel with integrated initramfs

2020-03-23 Thread Sascha Hauer
Hi Yegor, On Fri, Mar 20, 2020 at 09:29:04AM +0100, Yegor Yefremov wrote: > I get an "handler failed with: Out of memory" message when trying to > load my 22MB large kernel-fit.itb. Below you can see the related log: > > mounted /dev/nand0.UBI.ubi.kernel on /mnt/nand0.UBI.ubi.kernel > YY:

Re: [PATCH] common: fix typos found with codespell

2020-03-23 Thread Sascha Hauer
On Fri, Mar 20, 2020 at 10:41:19AM +0100, yegorsli...@googlemail.com wrote: > From: Yegor Yefremov > > Signed-off-by: Yegor Yefremov > --- > common/Kconfig| 4 ++-- > common/bbu.c | 2 +- > common/block.c| 2 +- > common/blspec.c | 16

Re: [PATCH] reset: remove duplicate imx8mq-reset.h and use correct defines

2020-03-23 Thread Sascha Hauer
On Fri, Mar 20, 2020 at 06:16:13PM +0100, Lucas Stach wrote: > The defines in the Barebox copy of imx8mq-reset.h had a type, which has been > fixed > in the upstream Linux version of this file. So depending on include ordering > the > reset driver using those defines would fail to compile. Use

Re: [PATCH] common: oftree: trim leading spaces from bootargs

2020-03-23 Thread Sascha Hauer
On Fri, Mar 20, 2020 at 05:07:20PM +0100, Clement Leger wrote: > When barebox concatenates all dynamic bootargs string for linux, if they > are empty, the resulting string might be composed of only spaces. > Currently, there is no check for such string and it leads to > overwriting bootargs in the