public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] command "sspi": add write-only flag '.w' (discard read data)
Date: Thu, 21 Jul 2011 11:01:21 +0200	[thread overview]
Message-ID: <m2oc0odn32.fsf@ohwell.denx.de> (raw)
In-Reply-To: <201107202127.22405.vapier@gentoo.org> (Mike Frysinger's message of "Wed, 20 Jul 2011 21:27:21 -0400")

Hi Mike,

[...]

>> Following the common U-Boot way to do this, I'd suggest
>> 	sspi [<bus>:]<cs>[.<mode>] <bit_len> <dout> [din_env_var]
>> and either never print the read result to the console (my favorite) or
>> only if no env variable to store is passed. To be defined, comments
>> welcome.
>
> is this the common u-boot approach ?  seems like extending every random func 
> to take a supplementary env var is the wrong way.  if the hush shell simply 
> supported syntax like:
> 	foo="`sspi ......`"
> then every command would get this for free

Indeed - this would be the best solution and I would greatly appreciate
such a feature as it would be a big step in what we can script
(elegantly) in U-Boot.

Cheers
  Detlev

-- 
More than any other time in history, mankind faces a crossroads.  One
path leads  to despair  and utter  hopelessness.   The other to total
extinction.  Let us pray, we have the wisdom to choose correctly.
                                        -- Woody Allen
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  reply	other threads:[~2011-07-21  9:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 17:32 [U-Boot] [PATCH] command "sspi": add write-only flag '.w' (discard read data) Andreas Pretzsch
2011-07-18 17:49 ` Mike Frysinger
2011-07-20 17:04   ` Andreas Pretzsch
2011-07-21  1:27     ` Mike Frysinger
2011-07-21  9:01       ` Detlev Zundel [this message]
2011-07-22 18:02         ` Andreas Pretzsch
2011-07-22 19:07           ` Mike Frysinger

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=m2oc0odn32.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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