Dear Matthias Fuchs, In message <[EMAIL PROTECTED]> you wrote: > > when I disable CONFIG_AUTOBOOT_KEYED ctrl-c checking is not disabled.
I think there is one "dis" ot "not" too many. > We are using CONFIG_AUTOBOOT_KEYED to have a special key (SPACE) to > abort autoboot and not the 'any' key. I thought so. > Is there any special reason why ctrl-c checking is disabled for > CONFIG_AUTOBOOT_KEYED? Excellent question. Next question, please. I think the rationale behind this is to prevent users from getting an interactive prompt by just pressing ^C - the intention of CONFIG_AUTOBOOT_KEYED is similar to a login with password - without the correct password you are denied access to an interactive inter- face. But if you could use ^C as soon as the bootcmd has started - what should happen next? We cannot simply drop you into the interactive shell? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] When the ax entered the forest, the trees said, "The handle is one of us!" -- Turkish proverb _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
