From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] get a confirmation from user
Date: Fri, 9 Nov 2007 17:19:56 -0400 [thread overview]
Message-ID: <200711091619.56580.vapier@gentoo.org> (raw)
some Blackfins have a small amount of One-Time-Programmable (OTP) memory on
them. the memory is not part of the Blackfin memory map, it can only be
accessed via on-chip functions. due to the nature of the memory (it cannot
be reprogrammed) and the way the memory is handled/documented (it's pretty
friggin confusing), i'd like to show a confirmation prompt to the user which
explains what is going to happen (which can be bypassed with a --force option
to the command for non-interactive sessions).
is there any common code to do this ? or do i have to write the small while
(1) { tstc()/getc()/ctrlc() } loop myself in order to get the "YES" string ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20071109/65a30dd2/attachment.pgp
reply other threads:[~2007-11-09 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200711091619.56580.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox