On Saturday, July 12, 2014 09:06:44 AM Zhaotian Wang wrote: > Hi guys, > Recently I am working on a project, who uses mesa source code as its > library. It went quite well with mesa 10.1.* and older version of mesa > source code. However, it does not build successfully with the current mesa > git master branch source code. > It turns out that the project uses some struct that no long exists in the > current mesa. > > 1. In the older version of mesa source code. the struct intel_mipmap_tree > has a member of struct intel_region, which records of the width and height > and cpp and especially tiling mode of the region, however the struct > intel_region does not exist in the new mesa source code. So where should I > find those information of the mipmap_tree?
We just combined intel_mipmap_tree and intel_region. So you can use: mt->cpp mt->tiling mt->logical_width0, mt->logical_height0 are the width/height of the base level (LOD 0), without padding mt->physical_width0, mt->physical_height0 include such padding. > 2. In the older version of mesa source code, the struct intel_mipmap_level > stores the width and height of the current level of the map. However, I > cannot find the width and height of the intel_mipmap_level in the current > mesa source code. So, I'd like to ask, where should I find those > information? Instead of mt->level[LOD].width, you can do: minify(mt->logical_width0, LOD - mt->first_level) > Sorry about asking such newbie questions, maybe I should spend some time > looking deeply into the code to find the answers, but I think it is > probably ok to ask you guys first.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
