From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] busybox: add devmem
Date: Thu, 31 Jan 2019 20:26:33 +0200 [thread overview]
Message-ID: <20190131182633.GC28875@localhost> (raw)
In-Reply-To: <CAMKF1sq6Syjj5D3YT463z+d4NiVRaFNmTvM6gww5npLGvWR9nA@mail.gmail.com>
On Wed, Jan 30, 2019 at 02:18:06PM -0800, Khem Raj wrote:
> On Wed, Jan 30, 2019 at 12:31 PM Adrian Bunk <bunk@stusta.de> wrote:
>
> > On Wed, Jan 30, 2019 at 08:50:02AM -0800, Khem Raj wrote:
> > > On Wed, Jan 30, 2019 at 1:34 AM Adrian Bunk <bunk@stusta.de> wrote:
> > > >
> > > > This is a tiny but pretty useful tool.
> > > >
> > >
> > > question is, do we need this enabled in default config, or could be add
> > it via
> > > some DISTRO_FEATURE meant for validation etc. May be if you explain your
> > > usecase then we might be able to make a better assessment.
> >
> > Sorry for being too terse.
> >
> > devmem allows reading and writing hardware configuration registers,
> > which is useful both for debugging and for scripts.
> >
>
> Thanks for the info this seems useful can you also report how much does it
> increase size of busybox
In a -O2 build for arm64 busybox.nosuid grows 4 kB.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-01-31 18:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 9:34 [PATCH] busybox: add devmem Adrian Bunk
2019-01-30 16:50 ` Khem Raj
2019-01-30 19:47 ` Andre McCurdy
2019-01-30 20:01 ` Khem Raj
2019-01-30 20:09 ` Scott Ellis
2019-01-31 10:09 ` Philip Balister
2019-01-31 12:14 ` Leon Woestenberg
2019-01-30 20:31 ` Adrian Bunk
2019-01-30 22:18 ` Khem Raj
2019-01-30 22:31 ` Richard Purdie
2019-01-30 22:44 ` Leon Woestenberg
2019-01-30 22:47 ` Tom Rini
2019-01-31 19:04 ` Adrian Bunk
2019-01-31 19:58 ` Tom Rini
2019-01-31 18:26 ` Adrian Bunk [this message]
2019-01-31 10:06 ` Philip Balister
2019-01-31 18:14 ` Adrian Bunk
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=20190131182633.GC28875@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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