{"comment":{"url":"https://api.github.com/repos/cubanismo/allocator/comments/19318979","html_url":"https://github.com/cubanismo/allocator/commit/c86e523fa8ce061c275a8d96c58fd8d01dcc869a#commitcomment-19318979","id":19318979,"user":{"login":"robclark","id":48820,"avatar_url":"https://avatars.githubusercontent.com/u/48820?v=3","gravatar_id":"","url":"https://api.github.com/users/robclark","html_url":"https://github.com/robclark","followers_url":"https://api.github.com/users/robclark/followers","following_url":"https://api.github.com/users/robclark/following{/other_user}","gists_url":"https://api.github.com/users/robclark/gists{/gist_id}","starred_url":"https://api.github.com/users/robclark/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robclark/subscriptions","organizations_url":"https://api.github.com/users/robclark/orgs","repos_url":"https://api.github.com/users/robclark/repos","events_url":"https://api.github.com/users/robclark/events{/privacy}","received_events_url":"https://api.github.com/users/robclark/received_events","type":"User","site_admin":false},"position":44,"line":44,"path":"allocator_common.h","commit_id":"c86e523fa8ce061c275a8d96c58fd8d01dcc869a","created_at":"2016-10-06T14:15:27Z","updated_at":"2016-10-06T14:15:27Z","body":"For drm/kms fourcc modifiers, we followed similar approach as gl extension, ie. it gets the vendor-id of the first vendor to define it.  With upstream kernel drm_fourcc.h as the \"serialization point\".  For example, drm/msm (qcom) has support on some generations for `DRM_FORMAT_MOD_SAMSUNG_64_32_TILE`.\r\n\r\nWe do require some amount of description/documentation in hopes of catching cases when two vendors introduce what happens to be the same thing.  (Where \"description\" == a para or two.. not quite as extensive as a gl spec.)\r\n\r\nAnyways, I guess there is enough of a precedent for this approach.  I don't think we need `VENDOR_MULTI`."}}
{"actor":{"display_login":"robclark"}}