From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pz0-f41.google.com (mail-pz0-f41.google.com [209.85.210.41]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E68A4E0137A for ; Mon, 7 May 2012 12:29:14 -0700 (PDT) Received: by dakp5 with SMTP id p5so20015719dak.28 for ; Mon, 07 May 2012 12:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zcrJ3lPuybUrKXIpyB4egTonlFmlRXigqp+WIaJquRQ=; b=bB3raNiaN8w0i+lJs54BtmC17Y7IMPuPiQQ0mZu1yvWpGCD+pB0OVcfmEnrTqCJHnS MqUhbkmsnAxs9OqBlIcIQ9B9+aT6RlP8pT4tAXMUe0HUH3FamvmA7vLxla9oWDq1tJnx YKTUGHMPVm2ii/y/nBJVMTaNY1TaZgOS8iwM6nRkPncxpOs/pDs9YsiTd93RUMDqI2Iw c9r/BSgZg1QsDWyIsBiuMBvuImIYz+9/AnPPqs0bFGihwjKxvbYaMNfdNltzXUm00ZG9 SowjKd2LVtXagDskkAABxKC81UYscXEcIC9dgC2VxkJ2dBheXpC88ONknHZ861Za30RE AGUw== MIME-Version: 1.0 Received: by 10.68.221.35 with SMTP id qb3mr29571952pbc.136.1336418954681; Mon, 07 May 2012 12:29:14 -0700 (PDT) Received: by 10.68.48.164 with HTTP; Mon, 7 May 2012 12:29:14 -0700 (PDT) In-Reply-To: <4FA7E0DB.7050508@windriver.com> References: <4FA7E0DB.7050508@windriver.com> Date: Mon, 7 May 2012 21:29:14 +0200 Message-ID: From: Frans Meulenbroeks To: Bruce Ashfield Cc: yocto@yoctoproject.org Subject: Re: modify a kernel patch 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: Mon, 07 May 2012 19:29:15 -0000 Content-Type: text/plain; charset=ISO-8859-1 2012/5/7 Bruce Ashfield : > On 12-05-07 10:41 AM, Frans Meulenbroeks wrote: >> >> Hi all, >> >> Not sure what the best place is to mail this (the YP list or oe-core >> or oe-devel or ...) >> Apologies if this is the wrong place. >> >> The problem I'm facing is the following: >> I have a kernel with some additional drivers that are not upstreamed >> because they are very specifc. >> I'm moving from oe-classic to denzil and from 2.6.38 to 3.2. >> Now some of the patches do not apply any more. >> In oe-classic I would have gone to the kernel work dir, fix the issue, >> do a quilt refresh and copy the patch back (there is a patch that >> contains our driver) >> However, denzil uses guilt instead of quilt >> >> If I do a devshell of virtual/kernel and want to do with guilt what I >> used to do with quilt I run into a problem. >> guilt status says: Patches directory does not exist, try guilt-init >> and indeed there is no patches dir like there was in oe-classic > > > Do you have guilt installed locally ? You are likely using the > native guilt. To keep patch lists separate on a per-branch basis > and to be able to capture them on th meta-branch, there are some > patches to guilt that move the patch directory location. Guilt natively complained about a mismatch with the git version (my work system is still ubuntu 10.04). If I do a bitbake -c devshell virtual/kernel and use guilt there, I get the error on the patches directory that I mentioned above. It was my idea that I then would get the oe version in my path but I did not really verify that. Then again under devshell I did not get complaints about the git version. Will verify this tomorrow (I have no access to the build system from here). > > Are you working on top of linux-yocto-3.2 ? Or some other 3.2 tree ? I downloaded the denzil tarball from yoctoproject.com. I made some config changed and added a few local patches (bringing things over from my 2.6.38 oe-classic kernel). Should I have gotten a patches dir in my tmp/work/mymachine/linux* dir (I have my own machine mpc8313e based) > > >> >> Hence my question: >> What is a good workflow to modify a kernel patch. >> Or, what magic incantation do I need to give to guilt to make it working. > > > See above. > > Bruce > Thanks! Frans