> The VIAVidHWDiffInit error could be fixed by merging some commits from > master to the kms_branch. > James, this are the VX900 Xv support commits > (4406c4826f650e896548b369a73173c504434881 and > aa56f57da6e403060536f4215e3142f38e98d84d). What do you think about > cheery-picking them into kms_branch ? > John, this is harmless and has nothing to do with your problem.
I merged those patches. I haven't test them yet. > Both above errors will need to be fixed before you can use XvMC though, > but the XvMC code itself needs fweaking too anyway before it can be > useful for CX700 and later IGPs (this does include yours) I noticed for the XvMC case you need DRI working which currently is not the case or the VX900 yet for the kms_branch. You could enable it but the XvMC code uses a special blitter which is not ported yet to the drm-openchrome kernel. > Then you're hitting another bug in the kms_branch and X doesn't finish > starting up. James, I think this is the unresolved symbol I posted about > yesterday. > I think the attached patch should workaround that. > Once done, please send the log from the patched driver. That should be fixed now. _______________________________________________ openchrome-users mailing list openchrome-users@openchrome.org http://wiki.openchrome.org/mailman/listinfo/openchrome-users Main page: http://www.openchrome.org Wiki: http://wiki.openchrome.org User Forum: http://wiki.openchrome.org/tikiwiki/tiki-view_forum.php?forumId=1
