View Single Post
Old 01-28-2013, 01:11 PM   #38
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 711
Karma: 2290994
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
Quote:
Originally Posted by giorgio130 View Post
- The Kobos use kernel code that manages the eink panel that is almost identical to the one used by amazon until firmware 5.0.x. Since 5.1.x amazon modified a struct in the ioctl that is used to update the panel, and compatibility is lost. We need either to intercept those calls and translate them to the amazon equivalent, or create a custom kernel that won't be compatible with kobo software.
Pre-5.1.0 E Ink framebuffer support was deliberately dropped from KPV. However, it's not hard to add it, you should just provide the way for KPV to detect Kobo's framebuffer (relevant code).

EDIT: OK, I see you already did it. Nice.

Last edited by eureka; 01-28-2013 at 01:16 PM.
eureka is offline   Reply With Quote