4 ms·
A n00b-level hardware question. I have an old Sony PRS-T1 e-reader with a Freescale i.MX508 SoC (32-bit Cortex-A8, ARMv7-A architecture). If I am not mistaken,
by marttt 4y ago
A n00b-level hardware question. I have an old Sony PRS-T1 e-reader with a Freescale i.MX508 SoC (32-bit Cortex-A8, ARMv7-A architecture). If I am not mistaken, this processor might be supported by NetBSD since 7.0? There is a port for the Kobo reader, which has a similar one [0, 1].
Has anybody here maybe used the Kobo-NetBSD port? How much of an effort would it be to get it booting on the Sony T1? Or would it be a definite way to brick the device for good.
I was thinking it would be awesome to have the PRS-T1 as a NetBSD-based "single textfile viewer". No wireless or other goodies, no touchscreen, just a dumb pager, scrolling up and down on a plain text document using the device's physical buttons. For starters, it could, indeed, display just one document, which would be loaded into the device via USB.
In addition to USB access, one would have to map the T1's physical buttons to scrolling commands. Later on, multi-file support could be added (woah!), via some sort of simple terminal-based menu, again navigable with the hardware buttons. The T1 has 5 buttons + power on/off + reset.
Usually, the mods for various e-readers seem to focus on hacking the original, e.g. Android-based OS into something "more complete", that is, adding features. I would rather go the opposite direction -- turn the T1 into an ultra-barebones device. For, as an avid ereader user, I've come to realize that I would actually survive quite happily with just text files. PDFs are somewhat an issue, but ebooks can be converted to plain text incredibly nicely with a text-only web browser. Unzip the epub, navigate to HTML files, convert and merge them into a single .txt via 'links -dump'. For me, images or drawings in ebooks can mostly be skipped without much of an issue.
So yeah, maybe a toaster-running OS would be a good fit for such a project? Has there been any other porting efforts, with different ereaders -- and if not, then what are the main obstacles? (I am definitely not competent, but "ARM is messy", even for BSD wizards?) I couldn't find much examples. NetBSD guys seem to prefer toasters, I guess :).
0: https://mail-index.netbsd.org/netbsd-bugs/2013/08/29/msg034018.html https://mail-index.netbsd.org/netbsd-bugs/2013/08/29/msg0340...
1: https://wiki.netbsd.org/users/jun/kobo/ https://wiki.netbsd.org/users/jun/kobo/
- rjsw 4y agoJust from looking at what needed to be done to get the Pine64 PineNote to work with Linux, eInk displays need special drivers and each one is different. There isn't an eInk driver of any kind in NetBSD.