lib/igt_fb: switch to igt_ prefix from kmstest_

Shorter and more in line with our general igt_ prefix for everything
which isn't somehow intel or i915-gem or otherwise hw specific - these
helpers here are all fully generic framebuffer handling functions
based on kms + cairo.

Well, the actual buffer alloc is done with i915 gem, but meh ;-)

Two special cases:
- bpp_depth_to_drm_format and drm_format_to_bpp completely lacked
  prefixes, so just add igt_.
- write_fb was a bit misleading given that we have gem_write for
  uploading to buffers. Rename that to write_fb_to_png to make it
  crystal clear what this thing does even without looking at docs.

Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This commit is contained in:
Daniel Vetter
2014-03-26 09:18:11 +01:00
parent 57d7db8cf8
commit 9aea7ae541
14 changed files with 153 additions and 151 deletions
+5 -5
View File
@@ -51,7 +51,7 @@ enum test_mode {
typedef struct {
struct kmstest_connector_config config;
drmModeModeInfo mode;
struct kmstest_fb fb[2];
struct igt_fb fb[2];
} connector_t;
typedef struct {
@@ -90,17 +90,17 @@ static const char *test_mode_str(enum test_mode mode)
static uint32_t create_fb(data_t *data,
int w, int h,
double r, double g, double b,
struct kmstest_fb *fb)
struct igt_fb *fb)
{
uint32_t fb_id;
cairo_t *cr;
fb_id = kmstest_create_fb(data->drm_fd, w, h,
fb_id = igt_create_fb(data->drm_fd, w, h,
DRM_FORMAT_XRGB8888, true, fb);
igt_assert(fb_id);
cr = kmstest_get_cairo_ctx(data->drm_fd, fb);
kmstest_paint_color(cr, 0, 0, w, h, r, g, b);
cr = igt_get_cairo_ctx(data->drm_fd, fb);
igt_paint_color(cr, 0, 0, w, h, r, g, b);
igt_assert(cairo_status(cr) == 0);
cairo_destroy(cr);