- Now, when I re-run bitbake commands in the same directory with the patch files added, they're not getting added in incrementally, so I no longer see the errors. Perhaps that's my problem; I'm going to rerun bitbake after clearing out my tmp directory with the current patch files attached (which have their paths fixed I believe) and see how it goes.
There is one easy way to see if your new patches get applied or not because of some build cache issue: forcibly break them again somehow and run "bitbake" again: bitbake must then complain. If it does not then you have a build problem. Forcibly breaking something is always a very simple and effective way to make sure a change is actually taken into account.
I thought my issues was because I'm not using the git command to pull in the right file to diff during the bitbake, but you mention that other diff/patch methods work as well. Can you look at the above process and patch files and let me know if there's something I'm missing?
Patches have existed long before git was born; git is certainly not the only way to generate a patch. A plain "diff" command is the simplest. The patches you attached look correct.