View Single Post
Old 08-16-2012, 06:24 PM   #31
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
Quote:
Originally Posted by knc1 View Post
Here is another module to build:
Code:
# CONFIG_BLK_DEV_NBD is not set
Both Hawhill and GM have mentioned using that device, maybe they would like to let the Kindle kernel be the NBD server.
Nah, that's the "client side", i.e. the part that lets the kernel speak over network and present a block device. But thanks for noticing :-) On the Kindle, I do not see low-hanging fruits yet which would involve it. Servers can be (and usually are) userland programs. After all, they are just network servers.

(Short background: The k3flasher tool has a mode in which it presents the flash storage of a connected Kindle 3 via an NBD server. I used that because it is a dead-simple API to create a block device in userspace. Kind of a BUSE - block device in userspace, see FUSE for how I made that acronym up).

Though great progress here. I was thinking about creating a pure "open" Kindle OS, too (involving kindlepdfreader, simply since I know it well). But then, time...
hawhill is offline   Reply With Quote