From: Geert U. <ge...@li...> - 2001-11-14 21:06:55
|
On Wed, 14 Nov 2001 he...@ho... wrote: > James Simmons writes: > > Hi folks. I finally hammered a newer api for framebuffer devices. I > > adapted skeletonfb.c to show it off. Feedback welcomed. > > > > /* > > * linux/drivers/video/skeletonfb.c -- Skeleton for a frame buffer device > > * > ... > > /** > > * xxxfb_imageblit - REQUIRED function. Can use generic routines if > > * non acclerated hardware and packed pixel based. > > * Copies a image from system memory to the screen. > > * > > * @info: frame buffer structure that represents a single frame buffer > > * @image: structure defining the image. > > * > > * This drawing operation draws a image on the screen. It can be a > > * mono image (needed for font handling) or a color image (needed for > > * tux). > > */ > > void xxxfb_imageblit(struct fb_info *p, struct fb_image *image) > > { > > } > > Which bit ordering will be used? Leftmost = MSb (as in console fonts) > or leftmost = LBb (as in XFree, at least in nVidia driver, which I'm > familiar with)? Kernel fonts wider than 8 pixels have always been big-endian. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |