I refrained from saying it the first time around to see if that was just a quick PoC hack that would later be cleaned up, but: that's *really* not how you should be using FBInk
.
You can simply use it as it was meant to (i.e., a library), passing fbpad's open fb fd to fbink_init() at init, and then using fbink_refresh().
If you were worried it would be making a (in this instance) useless mmap, rejoice: it won't (it's only setup on-demand by stuff that actually requires writing the the fb, which _init & _refresh don't). Which means you won't have to use fbink_close() on teardown, either.
Also, honoring credits, licenses, and all that jazz, that'd be a plus, too
.