From: Adrian Bunk <bunk@stusta.de>
To: Philip Balister <philip@balister.org>
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:14:14 +0200 [thread overview]
Message-ID: <20190131181414.GB28875@localhost> (raw)
In-Reply-To: <64cf5467-80f3-735d-c894-088c918c54fe@balister.org>
On Thu, Jan 31, 2019 at 11:06:22AM +0100, Philip Balister wrote:
> On 01/30/2019 05:50 PM, 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.
>
> Also there is http://layers.openembedded.org/layerindex/recipe/1069/
>
> I was told a while ago the busybox version has some issues. Hunting
> through brain cells, I think it always does a read back after writing
> which can be bad for some hardware. So I've always used the recipe from
> meta-oe instead.
The broken one for that is actually devmem2, the busybox copy of the
code has the read back commented out.
> Philip
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
prev parent reply other threads:[~2019-01-31 18:14 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
2019-01-31 10:06 ` Philip Balister
2019-01-31 18:14 ` Adrian Bunk [this message]
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=20190131181414.GB28875@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.org \
/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