* Building custom Linux kernel with own layer @ 2013-03-20 15:59 Bryan Evenson 2013-03-20 17:02 ` Bruce Ashfield 0 siblings, 1 reply; 4+ messages in thread From: Bryan Evenson @ 2013-03-20 15:59 UTC (permalink / raw) To: poky@yoctoproject.org I have an Atmel AT91SAM9G25 based board and have been using the Classic OpenEmbedded development tree for my device. I am working on switching to using the Poky distribution. I found a Yocto layer that someone else had started here: https://github.com/baseapp/meta-atmel/tree/yocto. I would like to use this layer as a starting point and go from there. The layer looks to be setup to build kernel 2.6.39 (as that is the kernel I am currently using), but that's not what's happening on my system. I would like some help in figuring out what needs to change with the layer or my setup to build the 2.6.39 kernel. I am using the stable poky-danny-8.0 release (downloaded tarball). Under the poky-danny-8.0 folder, I cloned the meta-atmel layer that I referred to above. I changed my bblayers.conf to include the meta-atmel layer. When I bitbake linux-yocto, here's what I see for my build configuration: Build Configuration: BB_VERSION = "1.16.0" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "qemuarm" DISTRO = "poky" DISTRO_VERSION = "1.3" TUNE_FEATURES = "armv5 dsp thumb arm926ejs" TARGET_FPU = "soft" meta meta-yocto meta-yocto-bsp = "<unknown>:<unknown>" meta-atmel = "yocto:80336b72180283bfd5cf5f674e8c1081deede72a" and it builds 3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+8ee53c3b82ada3cdfd7d25f07d3975834ac9a9b2-r4.3. From looking at the meta-atmel layer, I think it should be overriding the linux-yocto settings from the other layers. What am I missing? Thanks, Bryan ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Building custom Linux kernel with own layer 2013-03-20 15:59 Building custom Linux kernel with own layer Bryan Evenson @ 2013-03-20 17:02 ` Bruce Ashfield 2013-03-20 19:35 ` Bryan Evenson 0 siblings, 1 reply; 4+ messages in thread From: Bruce Ashfield @ 2013-03-20 17:02 UTC (permalink / raw) To: Bryan Evenson; +Cc: poky@yoctoproject.org On Wed, Mar 20, 2013 at 11:59 AM, Bryan Evenson <bevenson@melinkcorp.com> wrote: > I have an Atmel AT91SAM9G25 based board and have been using the Classic OpenEmbedded development tree for my device. I am working on switching to using the Poky distribution. I found a Yocto layer that someone else had started here: https://github.com/baseapp/meta-atmel/tree/yocto. I would like to use this layer as a starting point and go from there. The layer looks to be setup to build kernel 2.6.39 (as that is the kernel I am currently using), but that's not what's happening on my system. I would like some help in figuring out what needs to change with the layer or my setup to build the 2.6.39 kernel. > > I am using the stable poky-danny-8.0 release (downloaded tarball). Under the poky-danny-8.0 folder, I cloned the meta-atmel layer that I referred to above. I changed my bblayers.conf to include the meta-atmel layer. When I bitbake linux-yocto, here's what I see for my build configuration: > > Build Configuration: > BB_VERSION = "1.16.0" > TARGET_ARCH = "arm" > TARGET_OS = "linux-gnueabi" > MACHINE = "qemuarm" > DISTRO = "poky" > DISTRO_VERSION = "1.3" > TUNE_FEATURES = "armv5 dsp thumb arm926ejs" > TARGET_FPU = "soft" > meta > meta-yocto > meta-yocto-bsp = "<unknown>:<unknown>" > meta-atmel = "yocto:80336b72180283bfd5cf5f674e8c1081deede72a" > > and it builds 3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+8ee53c3b82ada3cdfd7d25f07d3975834ac9a9b2-r4.3. From looking at the meta-atmel layer, I think it should be overriding the linux-yocto settings from the other layers. What am I missing? You need to set the preferred provider for your BSP to be your linux-custom recipe (or whatever you call it, you don't need to leave it called 'linux-yocto-custom'). If you've done that, and are still seeing 3.4.x in the version number, chances are the recipe simply isn't overriding the right variables .. and a peek at the recipe would figure that out quickly. Bruce > > Thanks, > Bryan > _______________________________________________ > poky mailing list > poky@yoctoproject.org > https://lists.yoctoproject.org/listinfo/poky -- "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Building custom Linux kernel with own layer 2013-03-20 17:02 ` Bruce Ashfield @ 2013-03-20 19:35 ` Bryan Evenson 2013-03-20 19:40 ` Bruce Ashfield 0 siblings, 1 reply; 4+ messages in thread From: Bryan Evenson @ 2013-03-20 19:35 UTC (permalink / raw) To: Bruce Ashfield; +Cc: poky@yoctoproject.org > -----Original Message----- > From: Bruce Ashfield [mailto:bruce.ashfield@gmail.com] > Sent: Wednesday, March 20, 2013 1:02 PM > To: Bryan Evenson > Cc: poky@yoctoproject.org > Subject: Re: [poky] Building custom Linux kernel with own layer > > On Wed, Mar 20, 2013 at 11:59 AM, Bryan Evenson > <bevenson@melinkcorp.com> wrote: > > I have an Atmel AT91SAM9G25 based board and have been using the > Classic OpenEmbedded development tree for my device. I am working on > switching to using the Poky distribution. I found a Yocto layer that > someone else had started here: https://github.com/baseapp/meta- > atmel/tree/yocto. I would like to use this layer as a starting point > and go from there. The layer looks to be setup to build kernel 2.6.39 > (as that is the kernel I am currently using), but that's not what's > happening on my system. I would like some help in figuring out what > needs to change with the layer or my setup to build the 2.6.39 kernel. > > > > I am using the stable poky-danny-8.0 release (downloaded tarball). > Under the poky-danny-8.0 folder, I cloned the meta-atmel layer that I > referred to above. I changed my bblayers.conf to include the meta- > atmel layer. When I bitbake linux-yocto, here's what I see for my > build configuration: > > > > Build Configuration: > > BB_VERSION = "1.16.0" > > TARGET_ARCH = "arm" > > TARGET_OS = "linux-gnueabi" > > MACHINE = "qemuarm" > > DISTRO = "poky" > > DISTRO_VERSION = "1.3" > > TUNE_FEATURES = "armv5 dsp thumb arm926ejs" > > TARGET_FPU = "soft" > > meta > > meta-yocto > > meta-yocto-bsp = "<unknown>:<unknown>" > > meta-atmel = "yocto:80336b72180283bfd5cf5f674e8c1081deede72a" > > > > and it builds > 3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+8ee53c3b82ada3cd > fd7d25f07d3975834ac9a9b2-r4.3. From looking at the meta-atmel layer, I > think it should be overriding the linux-yocto settings from the other > layers. What am I missing? > > You need to set the preferred provider for your BSP to be your linux- > custom recipe (or whatever you call it, you don't need to leave it > called 'linux-yocto-custom'). > If you've done that, and are still seeing 3.4.x in the version number, > chances are the recipe simply isn't overriding the right variables .. > and a peek at the recipe would figure that out quickly. > > Bruce Bruce, The preferred provider was setup for the BSP already. But, with the pointers I tracked down the problems. First, with the way everything was named in the layer I needed to call "bitbake linux-yocto-custom", not "bitbake linux-yocto". Then I'd made a mistake in specifying the MACHINE in my local.conf file. The machine I'm using from the meta-atmel layer is the at91sam9g25ek machine. I'd correctly put the line "MACHINE ?= at91sam9g25ek" in my local.conf file. However, I forgot to comment out the line earlier in the file that was setting the machine to qemuarm. Once I got those two fixes sorted out, it's now building a 2.6.39 kernel like I wanted. Thanks, Bryan > > > > > Thanks, > > Bryan > > _______________________________________________ > > poky mailing list > > poky@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/poky > > > > -- > "Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end" ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Building custom Linux kernel with own layer 2013-03-20 19:35 ` Bryan Evenson @ 2013-03-20 19:40 ` Bruce Ashfield 0 siblings, 0 replies; 4+ messages in thread From: Bruce Ashfield @ 2013-03-20 19:40 UTC (permalink / raw) To: Bryan Evenson; +Cc: poky@yoctoproject.org On 13-03-20 03:35 PM, Bryan Evenson wrote: > > >> -----Original Message----- >> From: Bruce Ashfield [mailto:bruce.ashfield@gmail.com] >> Sent: Wednesday, March 20, 2013 1:02 PM >> To: Bryan Evenson >> Cc: poky@yoctoproject.org >> Subject: Re: [poky] Building custom Linux kernel with own layer >> >> On Wed, Mar 20, 2013 at 11:59 AM, Bryan Evenson >> <bevenson@melinkcorp.com> wrote: >>> I have an Atmel AT91SAM9G25 based board and have been using the >> Classic OpenEmbedded development tree for my device. I am working on >> switching to using the Poky distribution. I found a Yocto layer that >> someone else had started here: https://github.com/baseapp/meta- >> atmel/tree/yocto. I would like to use this layer as a starting point >> and go from there. The layer looks to be setup to build kernel 2.6.39 >> (as that is the kernel I am currently using), but that's not what's >> happening on my system. I would like some help in figuring out what >> needs to change with the layer or my setup to build the 2.6.39 kernel. >>> >>> I am using the stable poky-danny-8.0 release (downloaded tarball). >> Under the poky-danny-8.0 folder, I cloned the meta-atmel layer that I >> referred to above. I changed my bblayers.conf to include the meta- >> atmel layer. When I bitbake linux-yocto, here's what I see for my >> build configuration: >>> >>> Build Configuration: >>> BB_VERSION = "1.16.0" >>> TARGET_ARCH = "arm" >>> TARGET_OS = "linux-gnueabi" >>> MACHINE = "qemuarm" >>> DISTRO = "poky" >>> DISTRO_VERSION = "1.3" >>> TUNE_FEATURES = "armv5 dsp thumb arm926ejs" >>> TARGET_FPU = "soft" >>> meta >>> meta-yocto >>> meta-yocto-bsp = "<unknown>:<unknown>" >>> meta-atmel = "yocto:80336b72180283bfd5cf5f674e8c1081deede72a" >>> >>> and it builds >> 3.4.11+git1+a201268353c030d9fafe00f2041976f7437d9386_1+8ee53c3b82ada3cd >> fd7d25f07d3975834ac9a9b2-r4.3. From looking at the meta-atmel layer, I >> think it should be overriding the linux-yocto settings from the other >> layers. What am I missing? >> >> You need to set the preferred provider for your BSP to be your linux- >> custom recipe (or whatever you call it, you don't need to leave it >> called 'linux-yocto-custom'). >> If you've done that, and are still seeing 3.4.x in the version number, >> chances are the recipe simply isn't overriding the right variables .. >> and a peek at the recipe would figure that out quickly. >> >> Bruce > > Bruce, > > The preferred provider was setup for the BSP already. But, with the pointers I tracked down the problems. First, with the way everything was named in the layer I needed to call "bitbake linux-yocto-custom", not "bitbake linux-yocto". Then I'd made a mistake in specifying the MACHINE in my local.conf file. The machine I'm using from the meta-atmel layer is the at91sam9g25ek machine. I'd correctly put the line "MACHINE ?= at91sam9g25ek" in my local.conf file. However, I forgot to comment out the line earlier in the file that was setting the machine to qemuarm. Once I got those two fixes sorted out, it's now building a 2.6.39 kernel like I wanted. Good news. Glad to hear it is up and running. Cheers, Bruce > > Thanks, > Bryan > >> >>> >>> Thanks, >>> Bryan >>> _______________________________________________ >>> poky mailing list >>> poky@yoctoproject.org >>> https://lists.yoctoproject.org/listinfo/poky >> >> >> >> -- >> "Thou shalt not follow the NULL pointer, for chaos and madness await >> thee at its end" > _______________________________________________ > poky mailing list > poky@yoctoproject.org > https://lists.yoctoproject.org/listinfo/poky > ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-03-20 19:40 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-03-20 15:59 Building custom Linux kernel with own layer Bryan Evenson 2013-03-20 17:02 ` Bruce Ashfield 2013-03-20 19:35 ` Bryan Evenson 2013-03-20 19:40 ` Bruce Ashfield
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.