On 11/26/2014 10:57 AM, James Thomas wrote:
On 32-bit systems fdtput writes 0xfffffffe as 0x7fffffff, which takes
some time to complete.
Setting this to 0 accomplishes the same goal
A value of 0 doesn't mean the same thing. 0 means that bootdelay is
enabled, just with an immediate timeout, whereas -2 means that bootdelay
is disabled completely, so that boot can't be interrupted. The
difference is that when bootdelay is 0, the user can still press a key
before the boot delay check, and break into the boot process. This would
make the flasher less reliable.
Can you explain why the correct value doesn't get into the DTB? It seems
better to fix that bug in fdtput instead. Or perhaps there's a bug in
the command-line arguments to fdtput that should be fixed?
BTW, you don't need to send a cover letter when you're only sending one
patch. In fact, even with a multi-patch series, you can often get away
without a cover letter assuming all the patch descriptions are complete,
which they should be anwyay:-)
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
