From: Roland Stigge <stigge@antcom.de>
To: Rob Landley <rob@landley.net>
Cc: devicetree-discuss@lists.ozlabs.org, grant.likely@secretlab.ca,
rob.herring@calxeda.com, rdunlap@xenotime.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
w.sang@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] Documentation: devicetree: Fix value format description
Date: Sun, 06 May 2012 10:02:06 +0200 [thread overview]
Message-ID: <4FA62FFE.6090301@antcom.de> (raw)
In-Reply-To: <4FA57504.2070308@landley.net>
Hi,
On 05/05/12 20:44, Rob Landley wrote:
> On 05/05/2012 06:38 AM, Roland Stigge wrote:
>> Numeric values in dts files can be specified in decimal and hex (the latter
>> prefixed 0x). The current documentation is updated with this patch to prevent
>> confusion about what is meant with values without "0x" (previously hex, now
>> dec).
>
> This updates the documentation to consistently say 0x in front of hex
> values, but doesn't change the device tree _parser_. What did the parser
> previously do with this input?
I can add the following para to the patch description if you ack:
===========================================================================
Background:
Since 2011's update to scripts/dtc/dtc-lexer.l, we only support the
/dts-v1/ format which mandates "0x" for hex values. Practically,
literals (<V1>[0-9]+|0[xX][0-9a-fA-F]+ -> DT_LITERAL) are handled via
strtoull() with base==0 ("auto"), while we previously also had a
DT_LEGACYLITERAL (<INITIAL>[0-9a-fA-F]+), forcing base==16. Not anymore.
===========================================================================
Thanks in advance,
Roland
next prev parent reply other threads:[~2012-05-06 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 11:38 [PATCH RESEND] Documentation: devicetree: Fix value format description Roland Stigge
[not found] ` <1336217886-27224-1-git-send-email-stigge-uj/7R2tJ6VmzQB+pC5nmwQ@public.gmane.org>
2012-05-05 18:44 ` Rob Landley
2012-05-06 8:02 ` Roland Stigge [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-16 20:33 Roland Stigge
2012-05-17 1:09 ` Rob Landley
2012-05-19 21:03 ` Grant Likely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FA62FFE.6090301@antcom.de \
--to=stigge@antcom.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=w.sang@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).