On Thu, Sep 15, 2016 at 12:38:13PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> these are the first few patches I did while creating a port for a Netgear
> RN2120.
>
> Best regards
> Uwe
>
> Uwe Kleine-König (4):
> ARM: mvebu_defconfig: oldconfig
> ARM: mvebu_defconfig: enable all machines, A
On Mon, Sep 12, 2016 at 12:20:56PM +0200, Enrico Jorns wrote:
> Barebox commands should not perform any action and return 0 if an
> invalid parameter was given. This might cause undetected unintended
> behvaior when calling commands with wrong options, either manually or
> from a script.
>
> Signe
On Fri, Sep 16, 2016 at 08:43:38AM +0200, Michael Olbrich wrote:
> Caching pointers to device tree nodes or names is not save. The barebox
> internal device tree may be changed by loading a new device tree or through
> fixup handlers. As a result, the string may be deleted.
> Use local copies of th
On Thu, Sep 15, 2016 at 01:10:21PM +0200, Lucas Stach wrote:
> Split into separate function and only call it after the chip type
> and revision is known.
>
> Signed-off-by: Lucas Stach
> ---
> arch/arm/mach-imx/imx6.c | 11 +--
> 1 file changed, 9 insertions(+), 2 deletions(-)
Applied,
On Thu, Sep 15, 2016 at 08:03:26AM +0200, Michael Olbrich wrote:
> address-cells/size-cells can either be set to 1 or 2 for 32 or 63 bit
> addresses respectively. Barebox currently writes 32 bit addresses.
> This makes sure that address-cells/size-cells are both set and have the
> correct value.
>
On Fri, 16 Sep 2016 08:43:38 +0200
Michael Olbrich wrote:
> Caching pointers to device tree nodes or names is not save. The barebox
safe?
> internal device tree may be changed by loading a new device tree or through
> fixup handlers. As
