Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
Hi Brian Hutchinson, So if you are like me and have a product that needs new kernels and filesystem images to keep up with security threats etc., ... you're going to have a hard life for a while (ask me how I know). Thank you for saying like this ^^; My situation is that maybe none of my company is interested in those toolchain issue. People are just don't care for toolchains. They only think general arm tool chain is always enough. You have done professional works with kernel and toolchains,.. with limited env. given to you. I will try my best but it will be only very much limited because of I don't know about kernel and toolchains.. Thank you again^^; Sincerely Journeyer Seoul Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m 2014-04-17 10:28 GMT+09:00 Brian Hutchinson b.hutch...@gmail.com: On Wed, Apr 16, 2014 at 7:51 PM, Journeyer J. Joh oosaprogram...@gmail.comwrote: Hi Denys Dmytriyenko, I would recommend you to talk to someone from your company who's more familiar with the code base that you are trying to look at and how it is derived and/or relates to OpenEmbedded and the Yocto Project. This is what exactly I am sorry for.. I, in my team, the only one who works with linux. There are people who works with linux but, until now, I cannot meet them easily. I feel mail-list more kindly than them.. And I am new to this company... Telling this story doesn't look fit to the purpose of this maillist but, this is just my story.. And this is the reason why I thank you for your kindness.. But I agree I should try to talk with people in my company. I don't know what OE for MSM is, that you keep referring, probably your company's product based on OE. I think this might be the OE for MSM: https://www.codeaurora.org/xwiki/bin/QLBEP/WebHome Thank you ... Sincerely Journeyer Hi Journeyer, After paying more attention to the platform you are using ... I'm doubtful that the sdk instructions we mentioned to you before will actually work for you especially seeing that the snapshot of OE at the links you provided are 2011/2012 vintage. You may want to investigate the older bitbake meta-toolchain recipes (meta-toolchain-sdk too). So if the sdk instructions don't work, but you need to work with the latest OE/Yocto releases ... you may have to do things like I've had to do in the past for some platforms that aren't directly supported by OE, Yocto etc. I've had to use the kernel/u-boot that came from the silicon vendor (never mainlined and probably never will and are frozen in time) and I build u-boot and kernel source from vendor outside of bitbake (standalone). You can use the toolchain that is probably provided with the MDM and setup OE or Yocto to use that toolchain as an external toolchain to build current released filesystem images and packages. This way you have new applications in the rootfs but may be stuck (if it isn't mainlined) with old kernel. Your mileage will vary if you decide to go down this road as there can be land mines ... It is always best to keep toolchain, kernel, and root filesystem moving forward (not necessarily using the latest but not lagging too far behind it) and not let one of them get pinned being static but some times you don't have much of a choice (I've been there). Sometimes when you try to build new filesystem images with old toolchains you run into problems. Building old kernels with new toolchains also causes problems. So if you are like me and have a product that needs new kernels and filesystem images to keep up with security threats etc., ... you're going to have a hard life for a while (ask me how I know). You can also study the platform specific differences between what codeaurora (the working example that supports your platform) provided and what the latest releases of OE/yocto provide and make new recipies and bsp's in the latest releases of OE or Yocto to support your platform which is the right thing to do ... but requires the most knowledge of the build system to do. I hope I'm not confusing you ... just trying to give you ideas of what options you have so you can best pick a solution that fits with what you are trying to do. You may have to pick a less than ideal solution to start with and as you learn more move toward adding platform/BSP support for your hardware to the latest version of OE, Yocto etc. Regards, Brian -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] What is the relationship between Open Embedded for MSM and Yocto Project?
Hello, First of all I thank Nicolas Dechesne and Brian Hutchinson, for the previous kind replies. While I was reading documents from Yocto Project, I found my source code in use in my company is of Open Embedded for MSM. I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core And the one of Yocto project is git://git.yoctoproject.org/poky From the git log prints poky is actively developped now but openembedded-core is not. In a nutshell(I learned this expression today^^), - What is the relationship between those two? Any differences? Commons? - Can I refer to the documents about poky for my openembedded-core? Thank you very much in advance. Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
2014-04-16 8:49 GMT+02:00 Journeyer J. Joh oosaprogram...@gmail.com: Hello, First of all I thank Nicolas Dechesne and Brian Hutchinson, for the previous kind replies. While I was reading documents from Yocto Project, I found my source code in use in my company is of Open Embedded for MSM. I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core And the one of Yocto project is git://git.yoctoproject.org/poky From the git log prints poky is actively developped now but openembedded-core is not. In a nutshell(I learned this expression today^^), - What is the relationship between those two? Any differences? Commons? - Can I refer to the documents about poky for my openembedded-core? Hi, the relationship between OpenEmbedded and Yocto Project is summed at http://en.wikipedia.org/wiki/Yocto_Project You may want to use the up to date layer list (with links to the official git repositories) here: http://layers.openembedded.org/layerindex/branch/master/layers/ -- Regards Samuel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
On Tue, Apr 15, 2014 at 11:49 PM, Journeyer J. Joh oosaprogram...@gmail.com wrote: From the git log prints poky is actively developped now but openembedded-core is not. OpenEmbedded-core is very much active and is at heart of everything around OE poky is a distribution based on OpenEmbedded and it also serves as default reference distribution of Yocto Project and there are many other distributions which use OE technology for build system, poky uses combo layer tools to merge the layers it uses into a single git repository thats why you see different commit SHAs, some other distros e.g. SHR or Angstrom uses different mechanisms than poky for creating the sandbox out of many layers, where the individual layers are clones and consumed as it is. -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
On 04/16/2014 02:49 AM, Journeyer J. Joh wrote: Hello, First of all I thank Nicolas Dechesne and Brian Hutchinson, for the previous kind replies. While I was reading documents from Yocto Project, I found my source code in use in my company is of Open Embedded for MSM. I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core And the one of Yocto project is git://git.yoctoproject.org/poky From the git log prints poky is actively developped now but openembedded-core is not. In a nutshell(I learned this expression today^^), - What is the relationship between those two? Any differences? Commons? - Can I refer to the documents about poky for my openembedded-core? OpenEmbedded is the build system and has been actively developed since 2004 or so (give or take a few years) Poky is the reference distribution from the Yocto Project. The Yocto Project is working to make embedded development easier. You should check the OpenEmbedded git server for activity; http://cgit.openembedded.org/openembedded-core/ I'm guessing (without looking) the codeaurora git is based of a release bench. Philip Thank you very much in advance. Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
Hi, Samuel Stirtzel, Khem Raj and Philip Balister, Thank you for the kind answers!! I understood what are those. - What is the relationship between those two? Any differences? Commons? OE for MSM is one instance of Yocto Project - OE-core. And It's like Poky - An reference instance of Yocto Project. - Can I refer to the documents about poky for my openembedded-core? I think I can refer to the poky's documentations but must make sure that poky and OE for MSM are siblings from the same framework - Yocto Prooject - OE-core Thank you very much for the kindness!! Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m 2014-04-16 21:02 GMT+09:00 Philip Balister phi...@balister.org: On 04/16/2014 02:49 AM, Journeyer J. Joh wrote: Hello, First of all I thank Nicolas Dechesne and Brian Hutchinson, for the previous kind replies. While I was reading documents from Yocto Project, I found my source code in use in my company is of Open Embedded for MSM. I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core And the one of Yocto project is git://git.yoctoproject.org/poky From the git log prints poky is actively developped now but openembedded-core is not. In a nutshell(I learned this expression today^^), - What is the relationship between those two? Any differences? Commons? - Can I refer to the documents about poky for my openembedded-core? OpenEmbedded is the build system and has been actively developed since 2004 or so (give or take a few years) Poky is the reference distribution from the Yocto Project. The Yocto Project is working to make embedded development easier. You should check the OpenEmbedded git server for activity; http://cgit.openembedded.org/openembedded-core/ I'm guessing (without looking) the codeaurora git is based of a release bench. Philip Thank you very much in advance. Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
I don't know what OE for MSM is, that you keep referring, probably your company's product based on OE. OE stands for OpenEmbedded and is the underlying technology for the Yocto Project and other things around it... I would recommend you to talk to someone from your company who's more familiar with the code base that you are trying to look at and how it is derived and/or relates to OpenEmbedded and the Yocto Project. -- Denys On Wed, Apr 16, 2014 at 09:37:49PM +0900, Journeyer J. Joh wrote: Hi, Samuel Stirtzel, Khem Raj and Philip Balister, Thank you for the kind answers!! I understood what are those. - What is the relationship between those two? Any differences? Commons? OE for MSM is one instance of Yocto Project - OE-core. And It's like Poky - An reference instance of Yocto Project. - Can I refer to the documents about poky for my openembedded-core? I think I can refer to the poky's documentations but must make sure that poky and OE for MSM are siblings from the same framework - Yocto Prooject - OE-core Thank you very much for the kindness!! Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m 2014-04-16 21:02 GMT+09:00 Philip Balister phi...@balister.org: On 04/16/2014 02:49 AM, Journeyer J. Joh wrote: Hello, First of all I thank Nicolas Dechesne and Brian Hutchinson, for the previous kind replies. While I was reading documents from Yocto Project, I found my source code in use in my company is of Open Embedded for MSM. I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core And the one of Yocto project is git://git.yoctoproject.org/poky From the git log prints poky is actively developped now but openembedded-core is not. In a nutshell(I learned this expression today^^), - What is the relationship between those two? Any differences? Commons? - Can I refer to the documents about poky for my openembedded-core? OpenEmbedded is the build system and has been actively developed since 2004 or so (give or take a few years) Poky is the reference distribution from the Yocto Project. The Yocto Project is working to make embedded development easier. You should check the OpenEmbedded git server for activity; http://cgit.openembedded.org/openembedded-core/ I'm guessing (without looking) the codeaurora git is based of a release bench. Philip Thank you very much in advance. Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
On Wed, Apr 16, 2014 at 2:02 PM, Philip Balister phi...@balister.org wrote: I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core this tree is just a fork of oe-core (upstream) which is stuck at a 2-year old commit. if this is what you are calling OE for MSM well then it's just a 2-year old OE. You might be calling that for MSM because it comes from QCOM Code Aurora git tree.. but there is no vendor change in [1] [1] https://www.codeaurora.org/cgit/quic/le/openembedded/openembedded-core/ -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
Hi Denys Dmytriyenko, I would recommend you to talk to someone from your company who's more familiar with the code base that you are trying to look at and how it is derived and/or relates to OpenEmbedded and the Yocto Project. This is what exactly I am sorry for.. I, in my team, the only one who works with linux. There are people who works with linux but, until now, I cannot meet them easily. I feel mail-list more kindly than them.. And I am new to this company... Telling this story doesn't look fit to the purpose of this maillist but, this is just my story.. And this is the reason why I thank you for your kindness.. But I agree I should try to talk with people in my company. I don't know what OE for MSM is, that you keep referring, probably your company's product based on OE. I think this might be the OE for MSM: https://www.codeaurora.org/xwiki/bin/QLBEP/WebHome Thank you ... Sincerely Journeyer Journeyer J. Joh o o s a p r o g r a m m e r a t g m a i l d o t c o m 2014-04-16 23:42 GMT+09:00 Nicolas Dechesne nicolas.deche...@linaro.org: On Wed, Apr 16, 2014 at 2:02 PM, Philip Balister phi...@balister.org wrote: I found this from the git remote url of my surce code. It is git://codeaurora.org/quic/le/openembedded/openembedded-core this tree is just a fork of oe-core (upstream) which is stuck at a 2-year old commit. if this is what you are calling OE for MSM well then it's just a 2-year old OE. You might be calling that for MSM because it comes from QCOM Code Aurora git tree.. but there is no vendor change in [1] [1] https://www.codeaurora.org/cgit/quic/le/openembedded/openembedded-core/ -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] What is the relationship between Open Embedded for MSM and Yocto Project?
On Wed, Apr 16, 2014 at 7:51 PM, Journeyer J. Joh oosaprogram...@gmail.comwrote: Hi Denys Dmytriyenko, I would recommend you to talk to someone from your company who's more familiar with the code base that you are trying to look at and how it is derived and/or relates to OpenEmbedded and the Yocto Project. This is what exactly I am sorry for.. I, in my team, the only one who works with linux. There are people who works with linux but, until now, I cannot meet them easily. I feel mail-list more kindly than them.. And I am new to this company... Telling this story doesn't look fit to the purpose of this maillist but, this is just my story.. And this is the reason why I thank you for your kindness.. But I agree I should try to talk with people in my company. I don't know what OE for MSM is, that you keep referring, probably your company's product based on OE. I think this might be the OE for MSM: https://www.codeaurora.org/xwiki/bin/QLBEP/WebHome Thank you ... Sincerely Journeyer Hi Journeyer, After paying more attention to the platform you are using ... I'm doubtful that the sdk instructions we mentioned to you before will actually work for you especially seeing that the snapshot of OE at the links you provided are 2011/2012 vintage. You may want to investigate the older bitbake meta-toolchain recipes (meta-toolchain-sdk too). So if the sdk instructions don't work, but you need to work with the latest OE/Yocto releases ... you may have to do things like I've had to do in the past for some platforms that aren't directly supported by OE, Yocto etc. I've had to use the kernel/u-boot that came from the silicon vendor (never mainlined and probably never will and are frozen in time) and I build u-boot and kernel source from vendor outside of bitbake (standalone). You can use the toolchain that is probably provided with the MDM and setup OE or Yocto to use that toolchain as an external toolchain to build current released filesystem images and packages. This way you have new applications in the rootfs but may be stuck (if it isn't mainlined) with old kernel. Your mileage will vary if you decide to go down this road as there can be land mines ... It is always best to keep toolchain, kernel, and root filesystem moving forward (not necessarily using the latest but not lagging too far behind it) and not let one of them get pinned being static but some times you don't have much of a choice (I've been there). Sometimes when you try to build new filesystem images with old toolchains you run into problems. Building old kernels with new toolchains also causes problems. So if you are like me and have a product that needs new kernels and filesystem images to keep up with security threats etc., ... you're going to have a hard life for a while (ask me how I know). You can also study the platform specific differences between what codeaurora (the working example that supports your platform) provided and what the latest releases of OE/yocto provide and make new recipies and bsp's in the latest releases of OE or Yocto to support your platform which is the right thing to do ... but requires the most knowledge of the build system to do. I hope I'm not confusing you ... just trying to give you ideas of what options you have so you can best pick a solution that fits with what you are trying to do. You may have to pick a less than ideal solution to start with and as you learn more move toward adding platform/BSP support for your hardware to the latest version of OE, Yocto etc. Regards, Brian -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel