Hi, 
  I am a recent addition to Google's ChromeOS gfx team.   I am currently working on display testing and reporting.   An important part of this is our screen capture tool, which works by querying drm for crtcs, planes, and fbs.  Unfortunately, there is only limited information available via drmModeGetFB(), which often wrong information when drmModeAddFB2() was used to create the fbs.   For example, if the pixel format is NV12 or YUV420, the fb returned knows nothing about the additional buffer planes required by these formats.   Ideally, we would like a function (e.g. drmModeGetFB2) to return information symmetric with drmModeAddFB2 including the pixel format id, buffer plane information etc.   

I am curious what would be the best way to make this work.  I'm happy to create the patch, but need some guidance first.

cheers,
-j

--
Dr. Joe Michael Kniss | Google ChromeOS | djmk@google.com  | 1-801-898-7977