Re: [oe] [kirkstone][PATCH 3/3] devmem2: update SRC_URI according to redirect

[Denys Dmytriyenko <denis@denix.org>]

https://lists.openembedded.org/g/openembedded-devel/message/97339


On Mon, May 30, 2022 at 10:07:07AM -0400, Philip Balister wrote:
> On 5/25/22 14:41, Martin Jansa wrote:
> >buildroot removed it in 2019 and recommends to use busybox version instead:
> >https://github.com/buildroot/buildroot/commit/2b2579afebfc7a9b8a458af1f2d206101fbfa19c
> >
> >"Use the the Busybox devmem utility, instead, which provides the
> >same functionality."
> 
> I want to say there is an issue with the busybox devmem. As I recall
> (and this is an ancient memory), if you use busybox devmem to write,
> it does a readback. This is a bad thing if the address you write to
> is a hardware device that uses the read to reset state.
> 
> Philip
> 
> >
> >On Wed, May 25, 2022 at 8:32 PM Khem Raj <raj.khem@gmail.com
> ><mailto:raj.khem@gmail.com>> wrote:
> >
> >    On Wed, May 25, 2022 at 11:08 AM Denys Dmytriyenko <denis@denix.org
> >    <mailto:denis@denix.org>> wrote:
> >     >
> >     > Sure, I can do that and put it in the repo, since I've made few
> >    patches on top
> >     > of it... Before I do that, are there any objections? Bootlin?
> >
> >    I would suggest to cross post with buildroot and see if there is
> >    interest in using it from
> >    a separate repository.
> >
> >     >
> >     >
> >     > On Wed, May 25, 2022 at 08:03:58PM +0200, Martin Jansa wrote:
> >     > > Anyone willing to create a repo for this on github instead of
> >    patching this
> >     > > in metadata?
> >     > >
> >     > > This is another reproducer for do_patch issue described here
> >     > > https://lists.yoctoproject.org/g/yocto/message/56602