Editing Useful Development Info (section)

== Techflash's method of porting over old kernel code ==
<blockquote>
my personal process for porting over really old code like that is:<br>
start with the last commit in which your "good" code still exists, if upstream, or is known good, if not<br>
sanity check - does it actually work there?  Yes - continue.  No - figure out what's wrong (bad toolchain?), fix it, continue.<br>
jump forward a few releases<br>
add your code in<br>
Build and test.<br>
If it works out of the box, save this as the last known commit, jump to step 3.<br>
If it works after minor fixes, save that code as the new "good" code, save this as the last known good commit, and jump to step 3.<br>
If it's horribly broken, go back to the last known good commit, and jump forward by less releases this time<br><br>

eventually, you'll narrow down between 2 releases, where the "major" issues occurred, you can now scan through the git log between them, and find the commit removing / renaming whatever functions, variables, etc, your code needs. You can now look back through the previous few commits, you'll probably see some changes happening to other drivers in preparation for the removal / rename / whatever.  Apply those to your driver, rebuild, and pray<br><br>

That's my personal process anyways, just figured I would drop it here in case it may be useful
</blockquote>
[[File:Kernelport flowchart.png]]