| commit | 7ed2911c8f727077249fc5170a1ab842465aef21 | |
| author | Alan Cox <alan@linux.jf.intel.com> | |
| Fri, 13 May 2011 10:09:32 +0000 (13 11:09 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Tue, 17 May 2011 18:37:57 +0000 (17 11:37 -0700) | ||
| tree | 9fe63ae9ef9ffbf18f8dd9339d743ccecbf948fc | treesnapshot (tar.gz zip) |
| parent | 4f0c8f43ee5e9e12ed36a5950e19cfe513669ae7 | commitdiff |
gma500: finish off the fault handler
GEM wants to mmap the object through the GTT (which avoids aliasing) so we
need to put the object into the GTT before we provide the fault mapping for
it.
While we are at it update the pin interface so that it digs dev out of the
GEM object itself. This provides a rather cleaner API and call environment.
Fix th refcount/on-off confusion in the pin API.
At this point we get a bit further with modetest but if we write to the
new GEM mapping we hang solid and as yet I don't know why.
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
GEM wants to mmap the object through the GTT (which avoids aliasing) so we
need to put the object into the GTT before we provide the fault mapping for
it.
While we are at it update the pin interface so that it digs dev out of the
GEM object itself. This provides a rather cleaner API and call environment.
Fix th refcount/on-off confusion in the pin API.
At this point we get a bit further with modetest but if we write to the
new GEM mapping we hang solid and as yet I don't know why.
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>