On Tue, Nov 04, 2014 at 11:11:40PM +0100, Wolfgang Denk wrote:
Dear Tom,
In message 20141104220213.GN15133@bill-the-cat you wrote:
Hm.... is there a way to determine in advance where we are passing a number as argument [see "common/cmd_fdt.c" lines 260ff] ?
The problem is that 'fdt set ... <decimal>' is valid and 'fdt set ... <0xhex>' is valid (as it 'fdt set ... string'). What I'm saying is that we should think of it as 'fdt set <input to DT>' and within <input to DT> we assume DT conventions, not U-Boot conventions.
Yes, I fully understand what you mean. I just wonder if there is a user-friendly way to prevent such errors.
I think we should at least document this behaviour - both in the help message for this command, and in the manual.
I think this is a documentation (readme and command help) only thing.