Quote:
Originally Posted by PoP
Since then, on v1.6.2 fbink -c '' (with null string, not even a single space) works fine on the K3, and it looks more logical to me. +1 Thanks.
|
Quote:
Originally Posted by NiLuJe
Turns out that was an actual side-effect of clear being essentially broken on einkfb devices before that  .
(I was slightly confused because without a clear, '' *will* get you shouted at, but the clear makes it safe). |
In the mean time between 1.6.2 and 1.10.3, somewhere in the twilight zone...
Code:
[root@kindle us]# fbink -c ''
[FBInk] Enabled Legacy einkfb Kindle quirks
[FBInk] Clock tick frequency appears to be 100 Hz
[FBInk] Screen density set to 167 dpi
[FBInk] Variable fb info: 600x800, 4bpp @ rotation: 0 (Upright, 0°)
[FBInk] Fontsize set to 16x16 (IBM base glyph size: 8x8)
[FBInk] Line length: 37 cols, Page size: 50 rows
[FBInk] Fixed fb info: ID is "eink_fb", length of fb mem: 483328 bytes & line length: 300 bytes
[FBInk] Pen colors set to #000000 -> #FFFFFF for the foreground and #FFFFFF -> #000000 for the background
Printing string '' @ column 0 + 0px, row 0 + 0px (overlay: N, no BG: N, no FG: N, inverted: N, flashing: N, centered: N, halfway: N, left padded: N, right padded: N, clear screen: Y, dithered: N, skip refresh: N, font: 0, font scaling: x0)
[FBInk] Cannot print an empty string!
Failed to print that string!
...broken again?
