linuxconsole-dev

imageblit, fb_image, weird size

[Romain D. <do...@ir...>]

Hello,

Another question: how are organized the data in fb_image->data,
in particular for weird size and small depth ?

i.e. for a 6x11 font, each char is width == 6, height == 11,
depth == 1. how are the 66 bytes put in data ? I assume
byte-padded (i.e. 11 bytes for a char, with a two-bits-wide
left column for padding), is it a valid assumption for _all_
fb_image ?

TIA

-- 
DOLBEAU Romain               | l'histoire est entierement vraie, puisque
ENS Cachan / Ker Lann        |     je l'ai imaginee d'un bout a l'autre
do...@ir...             |           -- Boris Vian

Re: imageblit, fb_image, weird size

[James S. <jsi...@tr...>]

> Another question: how are organized the data in fb_image->data,
> in particular for weird size and small depth ?
> 
> i.e. for a 6x11 font, each char is width == 6, height == 11,
> depth == 1. how are the 66 bytes put in data ? I assume
> byte-padded (i.e. 11 bytes for a char, with a two-bits-wide
> left column for padding), is it a valid assumption for _all_
> fb_image ?

Yes. Whatever the width of the image is it the last bits of data for each
row of data is byte padded. Even most accel engines require this. For
example the SUN 12x22 font whould have be formated as, where d represents 
data:

0123456789012345 

dddddddddddd0000
dddddddddddd0000
dddddddddddd0000
....
[22 times total]
dddddddddddd0000


BTW. The generic image drawing code doesn't suppor this. Also I haven't
restored the penguin drawing code. So if you don't see it don't think it
didn't boot.