From: Thomas Thorne <Thomas.Thorne@net2edge.com>
To: Zhenhua Luo <zhenhua.luo@nxp.com>,
srikanth krishnakar <skrishnakar@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Build issue in Qoriq SDK-v2.0 for TWR-LS1021A-PB (meta-freescale)
Date: Thu, 6 Oct 2016 09:53:49 +0000 [thread overview]
Message-ID: <DB6PR0701MB1879C3E95636CB178B0AABFFD3C70@DB6PR0701MB1879.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <DB6PR0401MB263070D01FF3AB91E8996FB1EEC70@DB6PR0401MB2630.eurprd04.prod.outlook.com>
>> Is there any official announcement on release of stable qoriq SDK fsl-sdk-v2.0-1609 ? If yes then, can we switch to this kernel from sdk-v2.0 kernel (4.1.8-rt8) ?
> [Zhenhua Luo] The SDK-v2.0-1609 is released in the end of Sep, we will upstream the recipes to meta-freescale layer in Oct.
This is good news for me. I will make a note of it on our development timelines.
Thank you for the info.
> Can anyone confirm that If we can still build Qoriq SDK-v2.0 for TWR-LS1021A-PB
If the TWR-LS1021A-PB, TWR-LS1021A or LS1021A-TWR are all the same thing then I am sure I build for the tower board last month. I am currently trying to use the fsl community edition as a base instead though, rather than the freescale issued SDK from the nxp.com website. If I switch back I will be very pleased to know about the patch.
next prev parent reply other threads:[~2016-10-06 10:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 14:55 Build issue in Qoriq SDK-v2.0 for TWR-LS1021A-PB (meta-freescale) srikanth krishnakar
2016-10-06 3:55 ` Zhenhua Luo
2016-10-06 9:53 ` Thomas Thorne [this message]
2016-10-06 13:14 ` srikanth krishnakar
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=DB6PR0701MB1879C3E95636CB178B0AABFFD3C70@DB6PR0701MB1879.eurprd07.prod.outlook.com \
--to=thomas.thorne@net2edge.com \
--cc=meta-freescale@yoctoproject.org \
--cc=skrishnakar@gmail.com \
--cc=zhenhua.luo@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 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.