Should the devmem2 recipe move to oe-core?

Should the devmem2 recipe move to oe-core?

[Philip Balister]

I was poking at the layer index and ran across this:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=devmem

The recipe appears in 4 layers.

Should we just move it to openembedded-core? I wonder how easy it would
be to have the layer index report duplicate recipes?

Philip

Re: Should the devmem2 recipe move to oe-core?

[Andre McCurdy]

On Sat, Nov 28, 2015 at 6:30 PM, Philip Balister <philip@balister.org> wrote:
> I was poking at the layer index and ran across this:
>
> http://layers.openembedded.org/layerindex/branch/master/recipes/?q=devmem
>
> The recipe appears in 4 layers.
>
> Should we just move it to openembedded-core?

The busybox version appears to be better maintained (it's gained
support for 64bit data types, which is still missing from the
original), so maybe better to recommend the busybox version instead.

> I wonder how easy it would
> be to have the layer index report duplicate recipes?
>
> Philip
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: Should the devmem2 recipe move to oe-core?

[Philip Balister]

On 11/30/2015 02:09 AM, Andre McCurdy wrote:
> On Sat, Nov 28, 2015 at 6:30 PM, Philip Balister <philip@balister.org> wrote:
>> I was poking at the layer index and ran across this:
>>
>> http://layers.openembedded.org/layerindex/branch/master/recipes/?q=devmem
>>
>> The recipe appears in 4 layers.
>>
>> Should we just move it to openembedded-core?
> 
> The busybox version appears to be better maintained (it's gained
> support for 64bit data types, which is still missing from the
> original), so maybe better to recommend the busybox version instead.

I think there is "some issue" with the busybix version, possibly related
to automatic readback after write. I'll ask around.

Philip

> 
>> I wonder how easy it would
>> be to have the layer index report duplicate recipes?
>>
>> Philip
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 

Re: Should the devmem2 recipe move to oe-core?

[Philip Balister]

On 11/30/2015 02:09 AM, Andre McCurdy wrote:
> On Sat, Nov 28, 2015 at 6:30 PM, Philip Balister <philip@balister.org> wrote:
>> I was poking at the layer index and ran across this:
>>
>> http://layers.openembedded.org/layerindex/branch/master/recipes/?q=devmem
>>
>> The recipe appears in 4 layers.
>>
>> Should we just move it to openembedded-core?
> 
> The busybox version appears to be better maintained (it's gained
> support for 64bit data types, which is still missing from the
> original), so maybe better to recommend the busybox version instead.

I asked some guys that actually use devmem2 and their comment was that
the "improvements" to the busybox version undermine some operations in
ways that make it less useful than the original.

Philip

> 
>> I wonder how easy it would
>> be to have the layer index report duplicate recipes?
>>
>> Philip
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>