Dave what is the best way to push this code? I am in no rush soI like to do it the right way. We have scattered history in the external tree but I would not lose sleep over its lost. I could just post pieces of the code to this list for review. One choice is after all the code is reviewed is to then merge the branch. Another choice is to create a new branch for later merge that will be composed of the patches posted to this list. We lose the history but that is not to be of deal for me. Just let me know what you would like and I will start the process.
Hi James,
I would probably say history loss is inevitable unless the tree is at a fairly high standard wrt bisection fail etc.
But it would probably be good to post the driver to dri-devel at least once so people can take a look, not sure what the best way to split it up is, the initial patches can be split different than what we merge if it makes reading it easier.
Can you post a link to what you consider the best place for me to be looking so I can see if splitting it makes sense.
Except for new pci ids in include/linux/pci_ids.h all the code is here
http://cgit.freedesktop.org/openchrome/drm-openchrome/tree/drivers/gpu/drm/v...
Thank you for taking a look.