From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 551EEE0044D for ; Wed, 11 Apr 2012 08:56:35 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q3BFuTZx013269 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Apr 2012 08:56:29 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Wed, 11 Apr 2012 08:56:29 -0700 Message-ID: <4F85A9A5.8080206@windriver.com> Date: Wed, 11 Apr 2012 11:56:21 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: Om Prakash PAL References: <3ED83A9DB3B6D94CA68BF7C03F2981D35A844F357F@EXDCVYMBSTM006.EQ1STM.local> <4F7C42E5.8000301@windriver.com> <3ED83A9DB3B6D94CA68BF7C03F2981D35AE63C1B66@EXDCVYMBSTM006.EQ1STM.local> <4F825F65.4040706@windriver.com> <3ED83A9DB3B6D94CA68BF7C03F2981D35AE63C1B69@EXDCVYMBSTM006.EQ1STM.local> <3ED83A9DB3B6D94CA68BF7C03F2981D35AE65C8E92@EXDCVYMBSTM006.EQ1STM.local> In-Reply-To: <3ED83A9DB3B6D94CA68BF7C03F2981D35AE65C8E92@EXDCVYMBSTM006.EQ1STM.local> Cc: "yocto@yoctoproject.org" Subject: Re: Porting of specific Kernel/Driver into yocto. X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2012 15:56:35 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 12-04-11 11:34 AM, Om Prakash PAL wrote: > Hi Bruce, > I need some more info > > [1].I want to add kernel dir path into SRC_URI(in meta-/recipe-kernel/linux/linux_3.0.bb), how can we add it ? i.e. lets imagine that my kernel is located in dir /local/kernel/* > How we can add this kernel into SRC_URI?.(imagine that we don't have git:// and http: path, we have just dir where my kernel is located) I do it this way in meta-kernel-dev: http://git.yoctoproject.org/cgit/cgit.cgi/poky-extras/plain/meta-kernel-dev/recipes-kernel/linux/linux-yocto-dev.bbappend In particular the protocol=file should be noticed. > > [2] we want to create BSP for our board that is based on arm-cortex-A9 but we don't have meta/conf/machine/include/tune-armcortexa9.inc file in current yocto. > How can we create it?. Answered this one previously. Cheers, Bruce > > Thanks, > > Best Regards, > Om Prakash Pal > > -----Original Message----- > From: Bruce Ashfield [mailto:bruce.ashfield@gmail.com] > Sent: Monday, April 09, 2012 11:04 PM > To: Om Prakash PAL > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto. > > On Mon, Apr 9, 2012 at 12:31 PM, Om Prakash PAL > wrote: >> Hi Bruce, >> Thanks for you help. >> As you have mentioned, its working properly. >> I want to know that is there any better way of doing same thing for my scenario ?: >> here is my scenario: >> We have development branch where we write/modify our kernel/driver code i.e. thats our local kernel repository(git rep) >> and lots of driver/files being modified everyday-->so I have to take the same effect into yocto kernel also----> so except creating patches for all modified drivers and creating .bbappend files, is there any better way of doing same thing . > > Aha. Missed that. > > Just create a simple recipe that points at your git repository in the SRC_URI. > If all the changes are in the tree, and you have a defconfig and you > are building > the master branch. Then pretty much everything you need can be specified in > the SRC_URI .. and that's the entire recipe. > > If you look in oe-classic, meta-ti or any one of a number of other > layers, you'll > find recipes that do just that. > > The meta-kernel-dev (in the poky extras) layer has an example of using the > kernel.org tree with the yocto kern tools, and once yocto 1.3 opens up for > submissions, I have a set of changes prep'd that make it relatively simple to > use the yocto kern tools against different types of repository. > > So the summary is: Depending on the type of tooling you need, and what baseline > you need for your work .. there are a number of ways to do things. > >> >> Is there anyway that instead of using yocto-kernel tree, can we use our local kernel-tree for building images?. (should I create separate BSP ?) > > You should definitely create a BSP, that way you can tune the system specific > to your board, > > Cheers, > > Bruce > >> >> Thanks in advance. >> Best Regards, >> Om Prakash Pal >> ________________________________________ >> From: Bruce Ashfield [bruce.ashfield@windriver.com] >> Sent: Monday, April 09, 2012 9:32 AM >> To: Om Prakash PAL >> Cc: yocto@yoctoproject.org >> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto. >> >> On 12-04-08 10:04 AM, Om Prakash PAL wrote: >>> Hi Bruce, >>> Thanks for your reply. >>> I am totally new to Yocto. >>> I have gone through the section BSP/Linux kernel configuration and if I am not wrong then it explains how can we configure the kernel, not the how we can add/replace a component(driver etc). >>> lets take the example of UART driver, I want to add my own UART driver code. >>> Should I write a separate recipe file (.bb) for UART Driver?. >>> if yes then I have to write the recipe files for all my drivers that will be very time consuming. >>> Is there any other way that I can port all my desired drivers into Yocto kernel?. >> >> No recipes are required per-driver, unless you are building them all >> as out of tree modules. >> >> The typical way this is done is to simply work in the extracted linux >> src tree (build/tmp/work//linux-yocto-/linux), manually >> patch, or copy your drivers into the tree. At this point, you'll port >> the drivers, doing test builds (bitbake -f -c compile linux-yocto) to >> ensure that your port is working. When you've completed the build phase, >> boot tests would be in order. (Do not do a 'clean' or you'll lose in >> progress changes). >> >> When you are happy with the changes, the directory where you were working >> is with the kernel git repository. So you can simply commit your >> changes, and generate patches. >> >> git format-patch -o HEAD^ (or however many commits >> you have) >> >> Take those patches, create a layer with a bbappend and add them like >> any other patch to any package. They'll be applied to subsequent builds >> of the kernel. >> >> I'm skipping a lot of detail there, but it is all found in the various >> manuals, and I don't want to repeat it here. >> >> Cheers, >> >> Bruce >> >>> Please help me. >>> Thanks a lot in advance. >>> >>> Best Regards, >>> Om Prakash Pal >>> ________________________________________ >>> From: Bruce Ashfield [bruce.ashfield@windriver.com] >>> Sent: Wednesday, April 04, 2012 6:17 PM >>> To: Om Prakash PAL >>> Cc: yocto@yoctoproject.org >>> Subject: Re: [yocto] Porting of specific Kernel/Driver into yocto. >>> >>> On 12-04-04 04:46 AM, Om Prakash PAL wrote: >>>> Hi, >>>> I want to build my local kernel/Driver code, not the default one. >>>> please help how can i do it ?. >>>> any wiki/docs on this?. >>> >>> The BSP developer guides show how to extend the yocto kernels, and >>> also have sections on custom/different kernel versions. Have you >>> seen that doc yet ? Or have you seen it, and have specific questions ? >>> >>> Bruce >>> >>>> >>>> Best Regards, >>>> Om Prakash Pal >>>> _______________________________________________ >>>> yocto mailing list >>>> yocto@yoctoproject.org >>>> https://lists.yoctoproject.org/listinfo/yocto >>> >> >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > >