From: Chunrong Guo <chunrong.guo@...> *update to lsdk 1903 tag include the following changes de8834d - binaries: update to LSDK-1903-TC1 Signed-off-by: Chunrong Guo <chunrong.guo@...> ---

From: Chunrong Guo <chunrong.guo@...> *update to lsdk 1903 tag include the following changes 80b2d2b - include: configs: lx2160a: update copyright info 7d323d4 - board: fsl: ls2080rdb: update

From: Chunrong Guo <chunrong.guo@...> *update to lsdk 1903 tag include the following changes f137787 - ls2088a: Removed the manually calculated PBI_LENGTH bac41de - ls1088a: Removed the manually

From: Chunrong Guo <chunrong.guo@...> *update to lsdk 1903 tag include the following changes eeb8972 - api: add symlink for MC 10.14.1, 10.14.2, 10.14.3 2f51b5a - config: lx2160a: Backplane

From: Chunrong Guo <chunrong.guo@...> *update to lsdk 1903 tag include the following changes 7e34aeb - Fix 2088 sleep hang dc16e35 - SDEI: Ensure SDEI handler executes with CVE-2018-3639

Hi All, Apologies if this is a known issue… but given that apparently SSL support for 1.0.2 is ending at the end of 2019 and support for 1.1.0 ends even before then, are there any plans to add

I'm confused. My nightly builds have been failing for a while, I look into it, create this patch, send it in, then Fabio's patch from 2 weeks ago gets applied... but I don't see it on the list

Hi All, Apologies if this is a known issue but given that apparently SSL support for 1.0.2 is ending at the end of 2019 and support for 1.1.0 ends even before then, are there any plans to add support

According to this commit: https://lists.freedesktop.org/archives/mesa-dev/2019-January/214067.html The imx gallium driver has been switched to use "KMS readonly". I realize the "vc4" looks

I applied it myself. Please send one for it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854

OK, I will try it tomorrow. By the way, has the problem what i said aleady fixed?what's the root cause? After that , I can fix it in the version i am using. Thanks a lot. sung_zhao@...

Kernel 4.1 is no longer supported. Could you try a more recent kernel and see if the problem has been solved?

Hi all: Recently, i get the problem in imx6q, under running in linux v4.1.6, the board cannot receive any packet but can send arp packet to network. I find the same problem in web

Hello, <jean-michael.celerier@...> wrote: Is this being used on sabresd board? or a custom board? -- Otavio Salvador O.S. Systems http://www.ossystems.com.br

Hi Matt, Your understanding is right. Best Regards, Zhenhua

Hi Otavio Am Montag, 18. März 2019 schrieb Otavio Salvador <otavio.salvador@...>: > Hello Max, > > On Thu, Mar 7, 2019 at 7:34 AM Max Krummenacher <max.oss.09@...> wrote: >> >> gstreamer and its

Hi Zhenhua, Thank you for the answer. So the -m options generated by Yocto SDK below is for e500v2, correct? If not, could you please explain? CC="powerpc-poky-linux-gnuspe-gcc -m32 -mcpu=8548

Hi Matt, The cross-build gcc is shared by different PPC architecture, including e500v2, e500mc, e5500 and e6500, those -m parameters are necessary for cross-compiling of specific core type. The

Hi all, I have built the standard Yocto SDK using the “bitbake <image> -c populate_sdk” command. I have some questions related to the generated toolchain. I wonder if I can get my doubts

Hello Otavlo, I have done . https://github.com/Freescale/meta-freescale/pull/64 Thanks Chunrong