View Single Post
Old 11-17-2013, 02:31 PM   #795
sergeyvl12
ebook fan
sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.sergeyvl12 ought to be getting tired of karma fortunes by now.
 
Posts: 735
Karma: 2528718
Join Date: Dec 2010
Device: PocketBook 301+, Kindle 3 Wi-Fi, Onyx Boox A62, Kindle Touch
Quote:
Originally Posted by giorgio130 View Post
Hmm, I know that code
I've tried to fix that, but just putting back the original values seems not to be enough. Probably there's some other field that gets changed automatically and doesn't get changed back when the original values are written.
I'd say that your results are already an improvement!
Better of all would be to implement normal blit function for 16 bpp. In this case we don't need to reboot. We can run koreader from KoboLauncher or standalone.

Quote:
Originally Posted by hawhill View Post
I think we should not reset the framebuffer upon starting, so that would get done with the problem. We don't use fbset in koreader but are using the Kernel API directly. But I have a modification in the works that would allow Koreader to handle the 16bpp framebuffer directly (in addition to 8bpp and 4bpp framebuffers, even RGB24/32 framebuffers will be possible). I guess it needs about a week to get polished.
Nice idea. Any results?
sergeyvl12 is offline   Reply With Quote