From: Denys Dmytriyenko <denys@ti.com>
To: Karthik Ramanan <a0393906@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [master PATCH v2 1/1] ipumm-fw: Updated ipumm firmware for latest IPC version
Date: Wed, 22 Oct 2014 14:00:16 -0400 [thread overview]
Message-ID: <20141022180016.GO25408@edge> (raw)
In-Reply-To: <5447EFA0.8090909@ti.com>
On Wed, Oct 22, 2014 at 11:25:44PM +0530, Karthik Ramanan wrote:
> On 22-Oct-14 10:18 PM, Denys Dmytriyenko wrote:
> >On Mon, Oct 13, 2014 at 08:42:59PM +0530, Karthik Ramanan wrote:
> >>* This includes the error handling support.
> >>* Minor bug fixes
> >
> >Karthik,
> >
> >Quick question - is there a separate download link for am57xx-evm or should
> >dra7xx-evm one be used for it?
> >
> Denys,
>
> I believe that the same can be reused for am57xx-evm. We don't have
> a separate download link for the am57xx-evm.
>
> Since the IPUMM binary was only used for dra7xx-evm until now the
> naming makes it sound like its specific to dra7xx-evm, we should
> change this going ahead.
Thanks. I sent out v3 of your patch with the modifications to allow am57xx-evm
to be built using the same dra7xx-evm binary - please provide any feedback.
And I agree we should look into naming it properly in the future.
--
Denys
next prev parent reply other threads:[~2014-10-22 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 15:12 [master PATCH v2 0/1] Updating IPUMM recipes to the latest Karthik Ramanan
2014-10-13 15:12 ` [master PATCH v2 1/1] ipumm-fw: Updated ipumm firmware for latest IPC version Karthik Ramanan
2014-10-22 16:48 ` Denys Dmytriyenko
2014-10-22 17:55 ` Karthik Ramanan
2014-10-22 18:00 ` Denys Dmytriyenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-13 15:10 [master PATCH v2 0/1] Updating IPUMM recipes to the latest Karthik Ramanan
2014-10-13 15:10 ` [master PATCH v2 1/1] ipumm-fw: Updated ipumm firmware for latest IPC version Karthik Ramanan
2014-10-13 15:25 ` R, Karthik
2014-10-21 4:36 ` Karthik Ramanan
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=20141022180016.GO25408@edge \
--to=denys@ti.com \
--cc=a0393906@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.