To implement Pepper in Native Client we need access to the implementation of the

Pepper APIs in Chrome.  Specifically, we need to be able to get the base::SharedMemory
or TransportDIB memory regions used to communicate with devices.  To enable doing this,
especially in 64-bit Chrome, I needed to change the GetStateContext and SetStateContext
functions to manipulate 64-bit values.  This CL does not include the Native Client
hookup to the new APIs, but is needed to do so.
BUG=none
TEST=none

Review URL: http://codereview.chromium.org/569004

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37975 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 4 insertions, 0 deletions

diff --git a/chrome/renderer/pepper_devices.h b/chrome/renderer/pepper_devices.h
index 50b3013..1abd554 100644
--- a/chrome/renderer/pepper_devices.h
+++ b/chrome/renderer/pepper_devices.h
@@ -31,6 +31,8 @@ class Graphics2DDeviceContext {
                 NPDeviceFlushContextCallbackPtr callback, NPP id,
                 void* user_data);
 
+  TransportDIB* transport_dib() { return transport_dib_.get(); }
+
  private:
   static int32 next_buffer_id_;
   scoped_ptr<TransportDIB> transport_dib_;
@@ -63,6 +65,8 @@ class AudioDeviceContext : public AudioMessageFilter::Delegate {
   virtual void OnVolume(double volume);
   // End of AudioMessageFilter::Delegate implementation
 
+  base::SharedMemory* shared_memory() { return shared_memory_.get(); }
+
  private:
   void OnDestroy();