Totally untested - at least until someone tests a few of these and reports back here.
This first attempt was a brute force, if it stood still long enough to build, wasn't already there, then build it as a module approach.
Probably a lot of useless stuff here for a Kindle, but then again, maybe a few hidden nuggets of gold.
Like: NBD driver, NFS-3 driver, CIFS driver, OSS driver, .....
Plan9 resource sharing, tipc distributed resources, ad-hock (peer-to-peer) wifi . . . .
You will need knowledge of how to manually determine dependencies (modinfo), manually insert (insmod) and manually remove (rmmod) modules from a running kernel.
Tar-ball has a base directory of 'lib/modules/version' (just like your work station would have).
You **must** be 'root' to get these things properly un-packed.
The lib/firmware sub-tree is not included in the tar-ball.
For the curious, there are 306 of them in the tar-ball: