another beginner-level question, i'm sure, but what's the
distinction between V_PROMPT and CONFIG_SYS_PROMPT for customizing the
u-boot prompt?
based on the output from a straightforward grep, it appears that
every example of customizing the prompt has the form:
#define V_PROMPT "OMAP3_EVM # "
... snip ...
#define CONFIG_SYS_PROMPT V_PROMPT
as in, V_PROMPT is set, for no other reason than to subsequently set
CONFIG_SYS_PROMPT a few lines later, at which point V_PROMPT never
seems to be used again.
is this just a historical holdover? any reason why
CONFIG_SYS_PROMPT can't be set directly and V_PROMPT ignored/removed?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
