Hey nerd, 
Can't tell, but I think you need to run 'bitbake linux-omap -c patch' first to apply the patch. 
Let me know


On Wed, Jul 18, 2012 at 4:42 PM, Nerd Cube <nerdcube314@yahoo.com> wrote:
Oh sorry, I forgot to mention in my first post that I also modified the bitbake recipe to specify the names of my added patches, like this:
SRC_URI = "git://www.sakoman.com/git/linux-omap-2.6.git;branch=omap-3.0-pm;protocol=git \
           file://defconfig \
           file://${BOOT_SPLASH} \
           file://my_patch.patch \
           file://patch-3.0.36-rt57 \

Do I need to add another SRC_URI line to explicitly define the new patches' location? I've noticed in a few recipe files there is a line like:
SRC_URI_append =" [...]
What is this for?

Sorry for the silly questions!

Thanks so much!

From: Adam Lee <adam.yh.lee@gmail.com>
To: Nerd Cube <nerdcube314@yahoo.com>
Sent: Wednesday, July 18, 2012 4:26 PM

Subject: Re: [Gumstix-users] Problems patching the kernel with bitbake

Hey Nerd, 

In Scott's wiki, to apply the patch with bitbake, you should add a line something like this:

SRC_URI = "git://www.sakoman.com/git/linux-omap-2.6.git;branch=omap3-2.6.34;protocol=git \
file://defconfig \
+ file://my-board-overo.patch \
So in your recipe file, I think you should have a line that locates your patch file. From what you described in the first email, it seems like you simply grabbed the patch and dropped in the kernel recipe directory?


On Wed, Jul 18, 2012 at 4:21 PM, Nerd Cube <nerdcube314@yahoo.com> wrote:
Hi Adam,

I was looking at these two in particular, though I gleaned some information from several places.

I'm very new to kernel development, so I may have misread/misunderstood something.


From: Adam Lee <adam.yh.lee@gmail.com>
To: Nerd Cube <nerdcube314@yahoo.com>
Sent: Wednesday, July 18, 2012 4:13 PM
Subject: Re: [Gumstix-users] Problems patching the kernel with bitbake

Hi Nerd, can you point me to the tutorials that you used to patch your kernel?

Not sure if it's as easy as just dropping the patch into the directory.



On Wed, Jul 18, 2012 at 4:06 PM, Nerd Cube <nerdcube314@yahoo.com> wrote:

I got my build problem figured out, but now I want to add patches to my kernel.
I've read several tutorials on how to do this in bitbake, and from what I gather, once simply makes and/or downloads the desired patches, adds them to where bitbake can find them (i.e ${OVEROTOP}/org.openembedded.dev/recipies/linux/linux-omap3/ for 3.0.x kernels), and rebuilds (clean and recompile). I have done this and everything recompiles, but I am not seeing the effects of my patches when it boots.

In particular, I have downloaded the 3.0.36-rt57 patch from http://www.kernel.org/pub/linux/kernel/projects/rt/3.0/ and bitbake successfully applied it, but the -rt57 suffix was not added to the kernel name, and I am not seeing the typical signs of RT linux when I boot. As for configuration, I followed the instructions on https://rt.wiki.kernel.org/index.php/RT_PREEMPT_HOWTO, enabling CONFIG_PREEMPT_RT and the high-res timer.

I have also written my own patch that modifies the VDBG function in the storage_common.c file to add timestamps to the entires in var/log/syslog. I am not seeing these modifications either.

Bitbake seems to be accepting and applying my patches, as it does not tell me otherwise. Am I missing an essential step somewhere? 


Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
gumstix-users mailing list