From: Philip Balister <philip@balister.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Should the devmem2 recipe move to oe-core?
Date: Mon, 30 Nov 2015 09:26:40 -0500 [thread overview]
Message-ID: <565C5CA0.9020906@balister.org> (raw)
In-Reply-To: <CAJ86T=VT051Y_=hEOpiPLs=CYZ=qgRg-a1HOVoGauDR8xJuVCw@mail.gmail.com>
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
>
next prev parent reply other threads:[~2015-11-30 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 2:30 Should the devmem2 recipe move to oe-core? Philip Balister
2015-11-30 7:09 ` Andre McCurdy
2015-11-30 14:26 ` Philip Balister [this message]
2015-12-02 19:44 ` Philip Balister
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=565C5CA0.9020906@balister.org \
--to=philip@balister.org \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.