Re: [U-Boot] [PATCH] fdt: fix 'prop (...) not found!' error in 'fdt set' command

2017-09-04 Thread sjg
On 18 August 2017 at 06:41, Hannes Schmelzer wrote: > This commit brings things back to the well known working state of the > command. > - > With commit 9620d87259572ef21f0df60988d9a932ca673779 > (cmd/fdt: support single value replacement within an array) > > there was an error introduced modifyin

Re: [U-Boot] [PATCH] fdt: fix 'prop (...) not found!' error in 'fdt set' command

2017-08-27 Thread Simon Glass
On 18 August 2017 at 06:41, Hannes Schmelzer wrote: > This commit brings things back to the well known working state of the > command. > - > With commit 9620d87259572ef21f0df60988d9a932ca673779 > (cmd/fdt: support single value replacement within an array) > > there was an error introduced modifyin

[U-Boot] [PATCH] fdt: fix 'prop (...) not found!' error in 'fdt set' command

2017-08-18 Thread Hannes Schmelzer
This commit brings things back to the well known working state of the command. - With commit 9620d87259572ef21f0df60988d9a932ca673779 (cmd/fdt: support single value replacement within an array) there was an error introduced modifying (inserting) a property to a device-tree node. fdt_getprop(...) r