From: Tom Rini Date: Tue, 4 Nov 2014 17:54:36 -0500 Subject: [U-Boot] Inconsistency between $filesize and commands which accept numeric params In-Reply-To: <20141104221140.1789A380E22@gemini.denx.de> References: <1414677435.2064.34.camel@hellion.org.uk> <20141030152146.356D83809B0@gemini.denx.de> <1414683178.2064.51.camel@hellion.org.uk> <20141104154412.GI15133@bill-the-cat> <1415116135.11486.51.camel@hellion.org.uk> <20141104205302.495EE38334F@gemini.denx.de> <20141104205800.GM15133@bill-the-cat> <20141104212046.4989038334F@gemini.denx.de> <20141104220213.GN15133@bill-the-cat> <20141104221140.1789A380E22@gemini.denx.de> Message-ID: <20141104225436.GO15133@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 ... ' 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 ' and within > 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. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: