>>> On 09.01.17 at 17:34, <ian.jack...@eu.citrix.com> wrote:
> Jan Beulich writes ("Re: [PATCH v2] ns16550: Add command line parsing
> adjustments"):
>> See e.g. the cpufreq=, i.e. we're talking of
>>
>> com1=<name1>:<value1>,<name2>:<value2>,...
>
> I think we will have to use `=', so
> com1=<name1>=<value1>,<name2>=<value2>,...
>
> Since we already have BDFs which I think contain `:', and that would
> be more confusing than the `nested' equals signs.
Oh, indeed. Otoh these two sub-options then would b prefixed
by <name>= (or <name>:) too, so there would be visual
separation. Another option would be to allow both : and = as
top level separators.
> Also it would be good to support a few positional parameters. Most
> people would want to write something like
> com1=115200,8n1,irq=7
Right, I had been thinking of this too, but then wasn't sure to
suggest such a mixture. Perhaps the first two options could
even remain completely nameless then (I think those are the
ones which had been there from the beginning)?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
