View Single Post
Old 10-05-2016, 08:41 AM   #122
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by zxczxc View Post
Ok this makes perfect sense, thank you.
Would it be as simple as compiling the compiler, just as you instructed and I did for PW3, but this time from the sources for KT3?

I assume I will also have to put the kernel module source on github with KindleLazy? I'll try to do it soon.
It is not explicitly stated in the GPLv2, but common practice seems to indicate that just a hyperlink to where the sources can be found is sufficient.

Unless you made changes to the sources.

I now understand that you have not made changes to the kernel sources (as posted by Amazon @ https://www.amazon.com/gp/help/custo...deId=200203720 ) but only building some modules that Amazon does not normally ship.

I think that is what I did when I last built all modules for all (at the time) existing Kindle models / Kernel version in use. (It's posted here, somewhere.)
But I did include the build scripting I used to do it.

It is actually easier to use the 'allmodules' makefile target than to pick and choose just a few selected modules.
(Plus, the output of moddep will be complete to support the module auto-loader.)

Last edited by knc1; 10-05-2016 at 08:46 AM.
knc1 is offline   Reply With Quote