All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] devmem2
Date: Tue, 26 Apr 2011 16:19:24 +0200	[thread overview]
Message-ID: <87sjt53xjn.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <941721.92187.qm@web161408.mail.bf1.yahoo.com> (David Anders's message of "Tue, 26 Apr 2011 06:24:52 -0700 (PDT)")

>>>>> "David" == David Anders <dave123_aml@yahoo.com> writes:

 David> Peter,

 David> the primary commit that makes the devmem applet unusable for
 David> most debugging is this one:

 David> commit 043246560fcd5bb7bfb2caa2db270c3c0e8e06f4
 David> Author: Denis Vlasenko <vda.linux@googlemail.com>
 David> Date:   Sun Oct 26 17:26:55 2008 +0000

 David>     devmem: make it more script-friendly; don't do any reads
 David>      and output nothing if writing was requested. -100 bytes


 David> for board bring up and general development, for which devmem is
 David> primarily used, having devmem report the value before the write
 David> is important, as well as reporting the value after the write.

Ok, but adding a little shell wrapper to do that would be simple to do.

Forcing 2 extra read actions isn't that nice, both for the
script-friendlyness, but also for registers where reads have side
effects.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-04-26 14:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 14:17 [Buildroot] devmem2 Xianghua Xiao
2011-04-21 14:48 ` Bjørn Forsman
2011-04-26  2:28   ` David Anders
2011-04-26  5:36     ` Peter Korsgaard
2011-04-26 13:24       ` David Anders
2011-04-26 14:19         ` Peter Korsgaard [this message]
2011-04-26 14:40           ` David Anders
2011-04-21 19:23 ` Peter Korsgaard
2011-04-22 14:36   ` Xianghua Xiao
  -- strict thread matches above, loose matches on Subject: below --
2011-04-27  1:51 Ken McGuire
2011-04-27  2:15 ` David Anders
2011-04-27  3:55   ` Xianghua Xiao
2011-04-27  5:28     ` Peter Korsgaard
2011-04-27 12:44       ` Xianghua Xiao
2011-04-27  5:26   ` Peter Korsgaard
2011-04-27  5:25 ` Peter Korsgaard

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=87sjt53xjn.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.