Return-Path: Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 074B2E0052E for ; Wed, 7 Aug 2013 09:31:40 -0700 (PDT) Received: by mail-la0-f51.google.com with SMTP id fp13so1354092lab.38 for ; Wed, 07 Aug 2013 09:31:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=tMrb89fRmwFdezsEqFrCue+TEs+mGIvDV+6rT03ZDW0=; b=te2NCGIqwavrAfapZ+HjS4BHWugu4PkcpHjJQLg1GVT0IgHoz2mWpI8QlPVN5Atnse PNPcwPM+XuPR3+OfPuqSfwV1R5uBkwsaw8xWXjku912fFOWB6y/wVuZ7dmA2biyeo7Sr /22Ysu2pNmbKAdzlJO65fdcN7zx8dCFXZeiP6FGTreb5g9cDKlHdIlkSLY6y4BdM2KI6 aJyi5+ze1QMshugTH5YdNS7R4Z4J+SLz1ZZ063/oGonOH3+0AY8alM6rudbCxtGzEvuI tNd8kBomLclMjo6q2CpegIQjvmcwWOT47CRWrZ1pfgtPh/jyczQ3DUh4GKM6SpqrC1dn 2veQ== X-Received: by 10.152.26.104 with SMTP id k8mr1706569lag.85.1375893099294; Wed, 07 Aug 2013 09:31:39 -0700 (PDT) Received: from [192.168.1.140] (59.37-191-128.fiber.lynet.no. [37.191.128.59]) by mx.google.com with ESMTPSA id gh5sm3495365lbc.12.2013.08.07.09.31.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 Aug 2013 09:31:38 -0700 (PDT) References: <51F8BAE8.3090805@gmail.com> <51F8EDB2.4020001@gmail.com> <8FA37C33-DF65-4B96-BD90-4D3B784E4A57@gmail.com> <51FF1602.8040805@windriver.com> Mime-Version: 1.0 (1.0) In-Reply-To: <51FF1602.8040805@windriver.com> Message-Id: X-Mailer: iPad Mail (10B329) From: martiert@gmail.com Date: Wed, 7 Aug 2013 18:31:38 +0200 To: Bruce Ashfield Cc: "yocto@yoctoproject.org" Subject: Re: Building linux-yocto kernel in own bsp layer X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Aug 2013 16:31:42 -0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Bruce, have you had the opportunity to look at this yet? - Martin On 5. aug. 2013, at 05:03, Bruce Ashfield wro= te: > On 13-08-04 5:23 PM, martiert@gmail.com wrote: >>=20 >>=20 >> On 31. juli 2013, at 14:42, Bruce Ashfield wro= te: >>=20 >>> On Wed, Jul 31, 2013 at 6:57 AM, Martin Ertsaas wro= te: >>>> On 07/31/13 10:57, Andrea Adami wrote: >>>>> On Wed, Jul 31, 2013 at 9:21 AM, Martin Ertsaas w= rote: >>>>>> Hi. >>>>>>=20 >>>>>> I'm creating my own bsp layer for omap4 chips (Yes, I know of meta-ti= , >>>>>> but I want to learn how to do this myself :)). I'm trying to use the >>>>>> linux-yocto 3.4 kernel, >>>>>> and have gotten it to work locally. I then made a >>>>>> linux-yocto_3.4.bbappend which contains the following: >>>>>>=20 >>>>>> COMPATIBLE_MACHINE_pandaboard =3D "pandaboard" >>>>>>=20 >>>>>> SRCREV_machine_pandaboard ?=3D "7eb5fbf903d9db90c3cf371b65e1f2a68d567= 6d7" >>>>>>=20 >>>>>> THISDIR :=3D "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" >>>>>> FILESEXTRAPATHS_prepend :=3D "${THISDIR}/${PN}-3.4" >>>>=20 >>>> The defconfig is found. I can see a defconfig in ${WORKDIR} with zero >>>> diff to my defconfig. It is, however, not copied from there into >>>> ${WORKDIR}/linux. >>>=20 >>> If you are looking in ${WORKDIR}/linux, you'll never see the defconfig. E= ven >>> in the base kernel class it is copied to the build directory, which is >>> linux-$MACHINE-build. >>>=20 >>> Even after the copy, it is pulled into a secondary set of >>> configuration steps that >>> allow configuration fragments to be processed and layered on top of >>> that baseline >>> configuration. >>>=20 >>> Are you determining that it isn't being used by the existence or non >>> existence of a >>> file, or are you seeing other issues with the resulting .config ? >>=20 >> What I see is that I have a ${WORKDIR}/defconfig. The .config in linux-${= MACHINE}-build is for a different architecture (x86) than my defconfig, the s= ame holds for the .config.old in the same place. Tried adding B=3D${WORKDIR}= /linux-${MACHINE}-build to my append, but no difference. >=20 > Can you make your BSP layer available to me ? I need to see this > happening on my machines, since all my tests worked here :( >=20 > B=3D${WORKDIR}/linux-${MACHINE}-build would already be set by the > base classes, so I wouldn't have expected it to make much of a > difference. >=20 > Bruce >=20 >>>=20 >>> Technically you don't even need a defconfig, you can just use a .cfg >>> with h/w options >>> for the board, but that's a different topic. >>>=20 >>> Cheers, >>>=20 >>> Bruce >>>=20 >>>>=20 >>>> I changed it so it uses the colon though, and removed THISDIR as >>>> suggested by Paul, but didn't help. I still don't get the config copied= >>>> in, and if I add the do_configure_prepend myself to do this, I get a >>>> message from the kernel building saying my folder is unclean. >>>>=20 >>>> - Martin >>>>=20 >>>>> Martin, >>>>>=20 >>>>> the code in kernel.bbclass does already copy defonfig to .config, see >>>>> http://cgit.openembedded.org/openembedded-core/tree/meta/classes/kerne= l.bbclass#n216 >>>>>=20 >>>>> I think your problem is the deconfig is not found, you miss a colon a= t the end. >>>>> Use something like >>>>>=20 >>>>> FILESEXTRAPATHS_prepend :=3D >>>>> "${THISDIR}/${PN}-3.4:${THISDIR}/${PN}:${THISDIR}/files:" >>>>>=20 >>>>> Cheers >>>>>=20 >>>>> Andrea >>>>>=20 >>>>>=20 >>>>>> SRC_URI +=3D "file://defconfig" >>>>>>=20 >>>>>> do_configure_prepend() { >>>>>> cp ${WORKDIR}/defconfig ${S}/.config >>>>>> } >>>>>>=20 >>>>>> Problem I get is, without this configure_prepend, my defconfig is not= >>>>>> copied into .config the kernel folder. With this however, I get a >>>>>> complaint from the kernel that the kernel directory is not clean and I= >>>>>> have to run make mrproper. >>>>>>=20 >>>>>> I would greatly appreciate any pointer/help/explanations as to what I= >>>>>> have done wrong here, and how to fix it. Have been struggling for thi= s >>>>>> for a while now, and have no idea what I have done wrong. >>>>>>=20 >>>>>> Best regards >>>>>> Martin Ertsaas >>>>>> _______________________________________________ >>>>>> yocto mailing list >>>>>> yocto@yoctoproject.org >>>>>> https://lists.yoctoproject.org/listinfo/yocto >>>>=20 >>>> _______________________________________________ >>>> yocto mailing list >>>> yocto@yoctoproject.org >>>> https://lists.yoctoproject.org/listinfo/yocto >>>=20 >>>=20 >>>=20 >>> -- >>> "Thou shalt not follow the NULL pointer, for chaos and madness await >>> thee at its end" >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >=20