hi.
digging around in startx we find on the Kindle Keyboard.
Quote:
start_x()
{
# Ensure that the Framework is stopped (this will also wake the
# various input devices and the screen).
#
wait_framework_done
# Ensure that the eInk HAL is in the right state (8bpp) for X usage.
#
if [ ${SCREEN_DEPTH} -ne 8 ]; then
echo "*** Switching to byte per pixel mode ***"
${EINK_RESTART} 0 8
fi
}
|
Didn't know you could do that.
also: "/usr/bin/einkdamage" is referenced but doesn't exist, but I believe it is there on the 5 devices. (will check). Perhaps the code is out there? and could be back-ported...
Quote:
|
The X Damage Extension allows applications to track modified regions of drawables.
|
so it's some calls from X to the eink to let it know what to redraw. okay.
From the 5:
Quote:
[root@kindle root]# einkdamage --help
Unknown or invalid option '--help'
usage: einkdamage [-fbdev /dev/fb0]
-kind <#>
0:XDamageReportRawRectangles
1:XDamageReportDeltaRectangles
2:XDamageReportBoundingBox
3:XDamageReportNonEmpty
-update <#>
0:non-flashing updates
1:flashing updates
|
Much searching has not turned up any source. yet.
rxvt is the terminal it expects to run. (don't have this, could build - or swap out for a similar thing I do have) any suggestions on a native alternative. I don't see why they don't use Xterm but I recall something about rxvt being a virtual terminal, I'll have a read up on that.
and a few goofy xapps (I've got all but one)
I'll do a bit more digging - I have created all the required supporting Xapps and libs now
I think for the 3.
Will keep plugging on and see if I can get the X server up at least.
but yeah. my question. restart the 3 in 8 bit mode? you can do that?
and X on the 3 (I know someone who REALLY wants it, despite likely performance) thoughts? examples? I'm searching.
Thanks and Cheers.