From: Karthik Ramanan <a0393906@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH v2] dspdce-fw: Updated dspdce firmware for latest IPC version
Date: Mon, 27 Oct 2014 14:11:57 +0530 [thread overview]
Message-ID: <544E0555.3010507@ti.com> (raw)
In-Reply-To: <20141007191647.GD1731@edge>
On 08-Oct-14 12:46 AM, Denys Dmytriyenko wrote:
> Karthik,
>
> I'm at lost here. You did address my previous comment of not leaving 2
> versions, just updating from .02 to .04, but I don't understand why do you
> need an .inc file for, if there's only one version left?
>
> I traced it a bit back and there was a recommendation from Franklin about
> creating .inc file for a different recipe for ipumm-fw, but in that case it is
> warranted due to the fact that you pull 2 different sources for 2 platforms.
> So, in that case it might be better having 2 separate recipes for different
> machines with common parts in the .inc file, but see for yourself if that
> produces cleaner and simpler results. It's not alwats clear cut and you may
> need to experiment to choose the right option...
>
> Either way, dspdce-fw doesn't seem to need an .inc file.
>
Denys,
There is a case where there may be multiple dspdce firmware versions
based on different versions of IPC. It will make sense that we introduce
the inc file when there is a need.
I will abandon this patch and resubmit a v3 for this.
Regards
Karthik
prev parent reply other threads:[~2014-10-27 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 11:43 [for master] dspdce-fw: Updated dspdce-fw binaries Karthik Ramanan
2014-09-24 11:43 ` [for master] dspdce-fw: Updated dspdce firmware for latest IPC version Karthik Ramanan
2014-09-30 21:15 ` Denys Dmytriyenko
2014-10-01 5:44 ` [PATCH v2] " Karthik Ramanan
2014-10-07 19:16 ` Denys Dmytriyenko
2014-10-27 8:41 ` Karthik Ramanan [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=544E0555.3010507@ti.com \
--to=a0393906@ti.com \
--cc=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.