01-27-2024, 12:12 PM | #1 |
Junior Member
Posts: 4
Karma: 10
Join Date: Jan 2024
Device: Pocketbook
|
Running koreader on the Raspberry Pi + Eink display
Hello,
As I understand from the following documentation: https://github.com/koreader/koreader...doc/Porting.md The koreader requires the framebuffer driver to be present on the system, is it right? I'm planning to use raspberry pi for my project + eink display. However, I couldn't find any eink display that is already supported by the kernel or any out of tree drivers for it. The display that I'm planning to use: https://www.good-display.com/product/386.html So, the steps are: 1. Implement framebuffer eink driver (SPI) 2. Point koreader to use the framebuffer device 3. Enjoy Are the steps correct, or I'm missing something? Maybe someone has already done it? |
01-27-2024, 05:13 PM | #2 |
cosiñeiro
Posts: 1,288
Karma: 2200073
Join Date: Apr 2014
Device: BQ Cervantes 4
|
It sounds like a very bad idea. For much less money you could get a real device that has:
a 10x better screen (I would say 1000% better ) with frontlight and touchscreen a PMIC and battery linux kernel support for all those things. it is already supported in KOReader Buuut if it is just for the fun and you want to waste a little money and much time, you'll need a bunch of things missing on your steps, including - write a new device abstraction for your particular device (sdl works on computers with a desktop environment or on EGL surfaces, both work on the pi, but not your thing) - write the output module that interfaces with your kernel driver) - create some sort of input, write the input module And a bunch of other things. If you want to play with a Pi it is better to skip those sh***y eink screens and get yourself a 7" touchscreen display, where both input and output should work almost out of the box with the SDL version of KOReader (arm64, if possible) even without Wayland/X Last edited by pazos; 01-27-2024 at 05:23 PM. |
01-28-2024, 02:07 AM | #3 |
Junior Member
Posts: 4
Karma: 10
Join Date: Jan 2024
Device: Pocketbook
|
Hello Pazos,
Thanks for the reply. Yes, I'm totally agree with all of your points. However, I want to build the reader as a hobby. I have some experience with linux, and want to learn PCB design. I like this project: https://hackaday.io/project/192688-the-open-book However, it's not a linux device, so it not easy to use existing tools. I want to do the similar project, but on linux. I see that there is a generic framebuffer support, can I use it in my case? https://github.com/koreader/koreader...fer_einkfb.lua Regarding the SDL, I dont have much experience with it, but of course I can learn it. The SDL module should be written as part of the koreader or as part of the linux in general. This part I dont really understand clearly. Do you have some examples maybe? Thanks! |
01-30-2024, 03:36 AM | #4 | |
Junior Member
Posts: 4
Karma: 10
Join Date: Jan 2024
Device: Pocketbook
|
Quote:
|
|
01-30-2024, 08:15 AM | #5 |
cosiñeiro
Posts: 1,288
Karma: 2200073
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Hi. It is still a very bad idea.
If you want to play with PCB design just replicate the openbook device/firmware. It should be way easier and more fun. If you want to play with KOReader just get a device where it works for the most part and fix the platform bugs that still remain (ie: pocketbook). If you want to play with a RPI and a shitty Eink display just get them and play with easy stuff: learn to draw text and images to screen, the different refresh modes. Figure out a proper way to use the thing without KOReader as the main purpose. Then, once you master your "device" you can write a proper port to KOReader. It will suck because KO is meant to be used with a touchscreen or a pointer device. It will suck because KO wasn't never actively tested with resolutions below 800x600 It will suck for many, many reasons. And, on top of that, you won't get any kind of support during the port. Even if/when the port is done it is unlikely to be maintained upstream because there's no device to maintain. |
01-30-2024, 08:25 AM | #6 | |
cosiñeiro
Posts: 1,288
Karma: 2200073
Join Date: Apr 2014
Device: BQ Cervantes 4
|
Quote:
You'll need to write your own input/output modules for your device. So, nope you cannot repurpose the HAL of other devices as is. You can read it and understand it to be able to figure out the things expected to be done by those modules, so you can implement the things for your own. Google is your friend, generic questions not welcome |
|
02-01-2024, 05:14 PM | #7 |
the rook, bossing Never.
Posts: 11,609
Karma: 87456643
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper11
|
Yes, it's a panel used for retail labels.
Unless you are developing a new retail label this is pointless, and if you are the Raspberry Pi is the wrong platform. What @pazos writes is a 100% true. Last edited by Quoth; 02-01-2024 at 05:17 PM. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Running latest Calibre on a Raspberry Pi 4 | ostiniatoze | Calibre | 2 | 09-16-2022 12:14 PM |
Starting KOReader from CC works only if KOReader was not running before | Norbi24 | KOReader | 7 | 09-24-2020 12:10 PM |
kobo as raspberry pi display | pascal jakobs | Kobo Developer's Corner | 7 | 07-24-2019 04:02 AM |
How to get Calibre 3 running on Raspberry Pi 3 running Raspbian Jessie? | fivestones | Calibre | 6 | 01-25-2018 09:41 PM |
Eink Display's (Sony PRS505) vs. Nokia N800's LCD Display | brecklundin | Which one should I buy? | 23 | 05-15-2008 04:15 AM |