From: Sven L. <lu...@dp...> - 2001-03-12 10:44:57
|
On Sat, Mar 10, 2001 at 02:02:10AM -0800, James Simmons wrote: > > > That's a more generalized _clear + _clear_margins ? > > Yes. Also you can use different ROP with rectfill. Right now XOR and COPY > are supported. XOR is used for fbcon_recv. > > > better _bmove ? (if only I could get _that_ one to work > > reliably) > > Yep. > > > > The last function is fb_imageblit > > > which transfers data from host memory to screen memory. > > > > Thats seems new to me (I only know 2.2 and 2.4, as I only grep'ped > > through Ruby). Could be useful... > > Yes it is a ruby thing. > > >I calculated that for small fonts, just sending the font data may require > >less register writes than seting up a blit). This is naturally not true > >for bigger fonts (like 32x32 fonts, but do we use that ?) > > Well if we want to draw the penguin (80x80) then yes. Image draw and > except any size image. This is a strenght. We don't have to say you can > only use 8,16,32 fonts. You can use any size. This is much more powerful. I think we should differentiate between pattern expansion fills and image writes (as said before). Also some card offer both a limited size pattern fill (mostly 32x32 i guess), but also a more generic patterned rendering, where anykind of bitmap can be expanded. (well a rectangular area of anysize). This would be faster by a factor of (depth of framebuffer) that using image writed for monochrome fonts. Friendly, Svne Luther |