From: Bob Cochran <yocto@mindchasers.com>
To: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Cc: "razvan.stefanescu@freescale.com"
<razvan.stefanescu@freescale.com>,
Richard Schmitt <richard.schmitt@freescale.com>
Subject: Re: [meta-fsl-ppc] Can I get an update on l2switch?
Date: Fri, 29 Aug 2014 00:24:32 -0400 [thread overview]
Message-ID: <54000080.30803@mindchasers.com> (raw)
In-Reply-To: <fb7374e8eb8040a9a8e030e190fe8629@CY1PR0301MB0715.namprd03.prod.outlook.com>
Thank you Zhenhua for the information.
FYI - my thought has been to develop a basic driver for the switch from
scratch that supports core switching operations and doesn't use the 3rd
party binary library. I'm not sure how far this plan will get us
though. Hope to start the work soon.
Please provide an update if Freescale decides to do something similar.
The closed license binary really throws a monkey wrench in what could
otherwise be a sweet open source story built around your SoC.
Thanks again,
Bob
On 08/28/2014 11:45 PM, zhenhua.luo@freescale.com wrote:
> Hi Bob,
>
> Due to license constraint, the l2switch-util source can't be published via FSL external git(git.freescale.com), you might be aware that the source has been removed in ls2switch-util git tree(http://git.freescale.com/git/cgit.cgi/ppc/sdk/l2switch-util.git/), accordingly Yocto recipe can't be merged in meta-fsl-ppc layer.
>
> Currently the SDK ISO is the channel for l2switch usage. http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=SDKLINUX
>
>
> Best Regards,
>
> Zhenhua
>
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Bob Cochran
>> Sent: Friday, August 29, 2014 2:10 AM
>> To: meta-freescale@yoctoproject.org
>> Subject: [meta-freescale] [meta-fsl-ppc] Can I get an update on l2switch?
>>
>> Hi,
>>
>> A patch had been submitted to put the L2switch recipe (from sdk1.6) into
>> meta-fsl-ppc, but it was never committed.
>>
>> Will we see (a modified version) put back in? If so, please let us know
>> when.
>>
>> Thanks,
>>
>> Bob
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>
prev parent reply other threads:[~2014-08-29 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 18:10 [meta-fsl-ppc] Can I get an update on l2switch? Bob Cochran
2014-08-29 3:45 ` zhenhua.luo
2014-08-29 4:24 ` Bob Cochran [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=54000080.30803@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=meta-freescale@yoctoproject.org \
--cc=razvan.stefanescu@freescale.com \
--cc=richard.schmitt@freescale.com \
--cc=zhenhua.luo@freescale.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.