second take, hopefully this time it doesn't break one of the builds: "SurfaceFlinger will now allocate buffers based on the usage specified by the clients. This allows to allocate the right kind of buffer automatically, without having the user to specify anything."

This commit is contained in:
Mathias Agopian
2009-08-11 22:34:02 -07:00
parent 064dbd076d
commit 5cec4742b3
16 changed files with 134 additions and 37 deletions

View File

@@ -132,6 +132,7 @@ FramebufferNativeWindow::FramebufferNativeWindow()
android_native_window_t::lockBuffer = lockBuffer;
android_native_window_t::queueBuffer = queueBuffer;
android_native_window_t::query = query;
android_native_window_t::perform = perform;
}
FramebufferNativeWindow::~FramebufferNativeWindow()
@@ -235,6 +236,18 @@ int FramebufferNativeWindow::query(android_native_window_t* window,
return BAD_VALUE;
}
int FramebufferNativeWindow::perform(android_native_window_t* window,
int operation, ...)
{
switch (operation) {
case NATIVE_WINDOW_SET_USAGE:
break;
default:
return NAME_NOT_FOUND;
}
return NO_ERROR;
}
// ----------------------------------------------------------------------------
}; // namespace android
// ----------------------------------------------------------------------------