Dear Haavard Skinnemoen,
In message 20080811092533.3407704c@hskinnemo-gx745.norway.atmel.com you wrote:
It may be intended for debug, but it's available there without warning for the end user.
Hang on...end users can compile custom versions of u-boot now? And
Actually yes, they can. This is what GPL software is all about: enabling end users to do exactly that.
we're somehow responsible for stopping them from bricking their boards when they go and enable options they don't understand?
No, we aren't. But that was not the statement.
The problem is the same when the vendor (or whoever is responsible for setting this option) eneables this feature in a version that will ship to the end user.
And that was the intention of the patch, if I understand it correctly?
The board will most likely still boot, so the "end user" can use other tools to fix the breakage.
How should he, now that console access is disabled?
Then again, maybe this thing deserves its own environment variable? "disable_input" or something?
And how would you then enable it again? Without being able to input anything?
It certainly deserves to be mentioned in README, as I noted before.
The more we discuss about this, the more I tend to simply reject it.
Best regards,
Wolfgang Denk