On 13.02.2008 18:11, ron minnich wrote:
On Feb 13, 2008 9:05 AM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
Alternatives are "-" (used by memreserve and inside names) or ":" (used by memreg) or "_" (used inside names). I hope at least one of them is considered as reasonable alternative.
@ in this case seperates the type of resources (pci) from the instance of it (device, function).
So @ is a seperator. Using _ will add ambiguity as it is NOT a seperator. same problem for -.
OK.
Stepan, will the OFW guys kill us if we allow ':' as well as @.
I still am not sure that allowing @ AND : is really that good an idea -- it means some dts files will not look like others; and if we put the dts binary blob in the lar, tools that translate the blob to source (such as the dtc itself) will print @, not :.
In that case I'd retract my opposition to @, but only if the v3 design doc gets an additional paragraph specifying the syntax with a hint to potential misunderstandings with @.
I'm happy to allow ':' but be aware it's not problem-free.
Thanks for giving an analysis of the separator problem.
Regards, Carl-Daniel