From: "nus1998" <nus1998@yeah.net>
To: "Tom Hochstein" <tom.hochstein@nxp.com>
Cc: "Otavio Salvador" <otavio.salvador@ossystems.com.br>,
"Lauren Post" <lauren.post@nxp.com>,
"meta-freescale@lists.yoctoproject.org"
<meta-freescale@lists.yoctoproject.org>
Subject: Re: [meta-freescale] imx-vpuwrap_4.5.4 error
Date: Fri, 27 Mar 2020 10:08:22 +0800 (CST) [thread overview]
Message-ID: <3244bc9d.1f6d96.17119bf577f.Coremail.nus1998@yeah.net> (raw)
In-Reply-To: <VE1PR04MB6621C15CE9823CB5719271AAE2CF0@VE1PR04MB6621.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
Looks that is fixed, thanks
Nus
At 2020-03-27 04:29:05, "Tom Hochstein" <tom.hochstein@nxp.com> wrote:
>Sorry for the trouble. Lauren has fixed imx-vpuwrap and is building to make sure there are no other problems.
>
>Tom
>
>-----Original Message-----
>From: Otavio Salvador <otavio.salvador@ossystems.com.br>
>Sent: Thursday, March 26, 2020 7:37 AM
>To: nus1998 <nus1998@yeah.net>; Tom Hochstein <tom.hochstein@nxp.com>; Lauren Post <lauren.post@nxp.com>
>Cc: meta-freescale@lists.yoctoproject.org
>Subject: Re: [meta-freescale] imx-vpuwrap_4.5.4 error
>
>+ Tom and Lauren
>
>On Thu, Mar 26, 2020 at 4:20 AM nus1998 <nus1998@yeah.net> wrote:
>>
>> Hi,
>>
>> It seems that "git://github.com/NXP/vpu_wrapper.git" is broken which is the source url used by imx-vpuwrap_4.5.4.bb in zeus branch : imx-5.4.3-2.0.0.xml.
>> and FSL_MIRROR has no imx-vpuwrap-4.5.4.bin too (the newest is 4.5.3), I wonder is there a alternative URL available or workaround for this?
>>
>> Thanks
>> Nus
>
[-- Attachment #2: Type: text/html, Size: 1293 bytes --]
prev parent reply other threads:[~2020-03-27 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 7:20 imx-vpuwrap_4.5.4 error nus1998
2020-03-26 12:37 ` [meta-freescale] " Otavio Salvador
2020-03-26 20:29 ` Tom Hochstein
2020-03-27 2:08 ` nus1998 [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=3244bc9d.1f6d96.17119bf577f.Coremail.nus1998@yeah.net \
--to=nus1998@yeah.net \
--cc=lauren.post@nxp.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=tom.hochstein@nxp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).