-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion]: add support for bq cervantes devices. #16
Comments
More details later when I have access to a computer, but basically, device identification is done in fbink_device_id.c, with device-specific functions hidden behind ifdefs, and that's simply called from fbink_init. It'll probably need a copy of the mxcfb header, and a dedicated refresh function, too. That stuff lives in fbink.c ;). |
If there's nothing fancy in terms of model specific quirks, the whole device_id part may be completely unneeded, and only the refresh matters. If it's ntx hardware, we might even be able to simply recycle the Kobo functions... |
That's assuming the framebuffer doesn't lie about what it reports to userspace, which should hold true, with a bit of luck. Ntx is generally sane-ish in that respect, unlike pocketbook crap^Wstuff... |
@NiLuJe thanks for the feedback! Do I need to hardcore device resolution somewhere? here is the code I'm using to differenciate between bq readers
Not sure if we need (part of) that for FBInk |
Closing in favor of #17 |
Since the device is based on Freescale I.Mx6 sololite processor is similar to kobos, but without hardfloat support (a-la kindle).
As kobos, cervantes devices rely on /dev/ntx_io to read chunks of HWCONFIG from the unpartitioned space at the top of internal storage.
There are mainly three kind of devices to support, which differ on resolution, frontlight and "optimalight". But as long as FBInk doesn't need to know if a device has light capabilities we can just read resolution.
framebuffer seems pretty standard too.
Need some help to figure out how to do device identification. Any hint?
The text was updated successfully, but these errors were encountered: