From: Denys Dmytriyenko <denys@ti.com>
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCHv2] abefw: Firmware for OMAP5 ABE
Date: Tue, 3 Sep 2013 13:42:27 -0400 [thread overview]
Message-ID: <20130903174227.GF22235@edge> (raw)
In-Reply-To: <20130821154954.GE24491@edge>
Mrinmayee,
Ping. Do you have an ETA for addressing the comments below? Thanks.
On Wed, Aug 21, 2013 at 11:49:54AM -0400, Denys Dmytriyenko wrote:
> On Wed, Aug 21, 2013 at 03:31:42PM +0000, Maupin, Chase wrote:
> > >-----Original Message-----
> > >From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> > >bounces@yoctoproject.org] On Behalf Of Hingolikar, Mrinmayee
> > >Sent: Wednesday, August 21, 2013 6:48 AM
> > >To: Hingolikar, Mrinmayee; meta-ti@yoctoproject.org
> > >Subject: Re: [meta-ti] [PATCHv2] abefw: Firmware for OMAP5 ABE
> > >
> > >Ping for comments!
> >
> > For some reason I don't see this in my e-mails for the original post. Sorry
> > for the delay.
>
> You are correct - there were no v2 submissions to the list on July 3rd. We
> only reviewed the original patch before.
>
>
> > >> -----Original Message-----
> > >> From: Hingolikar, Mrinmayee
> > >> Sent: Wednesday, July 03, 2013 4:32 PM
> > >> To: meta-ti@yoctoproject.org
> > >> Cc: Hingolikar, Mrinmayee; Heroor, Siddharth
> > >> Subject: [PATCHv2] abefw: Firmware for OMAP5 ABE
> > >>
> > >> * The OMAP5 Audio Backend requires a 'firmware' to enable
> > >> sound. This recipe installs a prebuilt firmware. This
> > >> part is a hack, as in the current form, the firmware
> > >> cannot be cross-compiled. There is a plan to fix this
> > >> and hopefully, this recipe is short-lived. Once the code
> > >> is fixed, we should have new recipes that build the firmware
> > >> and clean up this recipe.
> > >>
> > >> v2:
> > >> * Merged contents from abefw.inc and removed abefw.inc based
> > >> on review.
> > >>
> > >> Signed-off-by: Mrinmayee Hingolikar <mrinmayee@ti.com>
> > >> Signed-off-by: Siddharth Heroor <heroor@ti.com>
> > >> ---
> > >> recipes-bsp/abefw/abefw_1.0.14.bb | 20 ++++++++++++++++++++
> > >> 1 files changed, 20 insertions(+), 0 deletions(-) create mode
> > >100644
> > >> recipes-bsp/abefw/abefw_1.0.14.bb
> > >>
> > >> diff --git a/recipes-bsp/abefw/abefw_1.0.14.bb b/recipes-
> > >> bsp/abefw/abefw_1.0.14.bb
> > >> new file mode 100644
> > >> index 0000000..8db71e4
> > >> --- /dev/null
> > >> +++ b/recipes-bsp/abefw/abefw_1.0.14.bb
> > >> @@ -0,0 +1,20 @@
> > >> +SUMMARY = "Firmware for OMAP5 ABE"
> > >> +HOMEPAGE = "http://git.ti.com"
> > >> +LICENSE = "BSD/GPLv2"
> >
> > This seems wrong. I thought the convention is "BSD | GPLv2" for either
> > license or "BSD & GPLv2" if mixed license.
> >
> > If it is mixed then you probably need 2 entries in LIC_FILES_CHKSUM, one for
> > each license.
> >
> > Also, does the GPLv2 use the "or later" clause such that it should be GPLv2+
> > ?
>
> This was already mentioned in one of the other patches.
>
>
> > >> +LIC_FILES_CHKSUM =
> > >> "file://COPYING;md5=923db086ed9463ab3215b24d87e05ec5"
> > >> +
> > >> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> > >> +COMPATIBLE_MACHINE = "omap5-evm"
> > >> +
> > >> +SRC_URI = "git://git.ti.com/glsdk/abefw-
> > >omap4plus.git;protocol=git"
>
> The git repo itself says omap4plus - why is it limited to OMAP5 only? Can it
> be enabled for OMAP4/Pandaboard too?
>
>
> > Not strictly required but PR = r0 here would help remind you to bump the PR
> > in the future.
> >
> > >> +
> > >> +S = "${WORKDIR}/git"
> > >> +
> > >> +SRCREV = "ceccc0332264e39bdc51e54f80ea7256a3886c58"
> > >> +
> > >> +do_install() {
> > >> + mkdir -p ${D}/lib/firmware
> > >> + cp ${S}/firmware/omap4_abe_new ${D}/lib/firmware/ }
> > >> +
> > >> +FILES_${PN} += "/lib/firmware/omap4_abe_new"
> >
> > I'm sure this has been discussed before, but do you see any confusion about
> > this being omap5-evm only and yet the FW is omap4_abe_new?
> >
> > >> --
> > >> 1.7.0.4
> > >
> > >_______________________________________________
> > >meta-ti mailing list
> > >meta-ti@yoctoproject.org
> > >https://lists.yoctoproject.org/listinfo/meta-ti
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2013-09-03 17:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372849303-21311-1-git-send-email-mrinmayee@ti.com>
2013-08-21 11:48 ` [PATCHv2] abefw: Firmware for OMAP5 ABE Hingolikar, Mrinmayee
2013-08-21 12:52 ` Cooper Jr., Franklin
2013-08-21 15:31 ` Maupin, Chase
2013-08-21 15:49 ` Denys Dmytriyenko
2013-09-03 17:42 ` Denys Dmytriyenko [this message]
2013-10-18 10:29 ` Mrinmayee Hingolikar
2013-07-12 6:43 Hingolikar, Mrinmayee
2013-07-12 13:11 ` Cooper Jr., Franklin
2013-07-22 4:13 ` Siddharth Heroor
2013-07-22 12:12 ` Cooper Jr., Franklin
2013-07-22 12:15 ` Maupin, Chase
2013-07-22 16:24 ` Denys Dmytriyenko
2013-07-19 6:01 ` Hingolikar, Mrinmayee
2013-07-19 11:54 ` Maupin, Chase
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=20130903174227.GF22235@edge \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.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.