Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ken McGuire <kenm@desertweyr.com>
To: buildroot@busybox.net
Subject: [Buildroot] devmem2
Date: Tue, 26 Apr 2011 19:51:38 -0600	[thread overview]
Message-ID: <1303869098.2489.67.camel@kenm-i7> (raw)

I use devmem/devmem2 on a daily basis.


On Tue, 2011-04-26 at 07:40 -0700, David Anders wrote:
> Peter,
> 
> yes we've had all this argument before and devmem in buildroot has
stayed the same and everyone has continued using devmem2. basically it
still boils down to the request that devmem2 not be removed from
buildroot.
> 
> Dave
> 
> 
> 

I was thrilled when this applet was added to Busybox (which I've been
using since 2002).
The last version of Busybox I use (for omap4) is 1.17.4 and its'
devmem.c applet was 93 lines including comments and 10 lines which were
commented out. The devmem2.c that I use every day is 79 lines including
comments. Having it as a busybox applet is a nice feature.
 
Unfortunately since the referenced changes, busybox's devmem is more
difficult to use, not impossible, just a pita because it is different
form devmem2 which I use on non busybox/uClibc/buildroot based systems
(the final software configuration). Now, I compile devmem2 outside of
Bulildroot, it just takes a few seconds and I have a little script to do
it when I change uclibc/libc versions or machine architectures.

Busybox, Buildroot and uClibc are great tools and I think that Buildroot
evolving into a mini-distro is not as really a "bad thing(tm)" as some
seem to think. Keep up the good work. 

That's my opinion, maybe the right thing to do is just remove devmem
from busybox, even devmem2 from the Buildroot "distro". I can live with
building it myself. 


   ...ken... aka cynfab aka GPSFan aka WA2VFN aka NGMB...




> 
> --- On Tue, 4/26/11, Peter Korsgaard <jacmet@uclibc.org> wrote:
> 
> > From: Peter Korsgaard <jacmet@uclibc.org>
> > Subject: Re: devmem2
> > To: "David Anders" <dave123_aml@yahoo.com>
> > Cc: "Peter Korsgaard" <jacmet@uclibc.org>, "Xianghua Xiao"
<xiaoxianghua@gmail.com>, "Bj?rn Forsman" <bjorn.forsman@gmail.com>,
buildroot at busybox.net
> > Date: Tuesday, April 26, 2011, 9:19 AM
> > >>>>> "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
> > 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

             reply	other threads:[~2011-04-27  1:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  1:51 Ken McGuire [this message]
2011-04-27  2:15 ` [Buildroot] devmem2 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
  -- strict thread matches above, loose matches on Subject: below --
2011-04-21 14:17 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
2011-04-26 14:40           ` David Anders
2011-04-21 19:23 ` Peter Korsgaard
2011-04-22 14:36   ` Xianghua Xiao

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=1303869098.2489.67.camel@kenm-i7 \
    --to=kenm@desertweyr.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox