Also what would be the ideal fields we should provide per register?
I guess it would help if we would add some table columns and other subsections for each register.
(also the alignment of columns)
I already tried to get it into a format that is already similar to the Periphery document - or at least as far as we go.

That way we would minimize the manual post-processing and have a framework ready where people would fill in the
essential data.

Thanks so much for your work in providing a neat list of Raspberry Pi registers, this is helping me and others out loads, and is what I wanted on day 1 of getting my R-Pi =D

I also found something else in my quest of getting the V3D registers to work in bare metal, that might help other people trying to work there way thru the new sources...
I found a website that links up all the functions etc. from the Brcm Android ICS Graphics Stack source in a web based viewer: http://www.fangfufu.co.uk/~fangfufu/brc ... unc_v.html

Thought I would share with anyone else that wanted an easy way to traverse thru the sources to make use of your wonderful register list =D